And that’s the dance. Facing a sea of infinity, it’s easy to despair, sure that you will never reach dry land, never have the sense of accomplishment of saying, “I’m done.” At the same time, to be finished, done, complete—this is a bit like being dead. The silence and the feeling that maybe that’s all.
Dancing on the edge of finished [ Seth’s Blog ]
Are you the resident genius on your team? Do you wrap wrappers in wrappers and frame frameworks in frameworks? Have you ignored/obscured whole swaths of .NET because your application is a special, special unicorn? Well, I’ve got some bad news. You’re the worst.
As for the rest of you, come with me. We’re going to painlessly add some business logic to an Entity Framework model.
Meddle’s IAddable, IUpdatable, and IDeletable interfaces respectively provide OnAdding, OnUpdating, and OnDeleting methods for your entity’s partial class to implement. As the naming would suggest, this is where you do your custom unicorn-type things to make your model sing and dance:
public partial class Product : IDeletable , IAddable { public void OnDeleting(IWork work) { if (this.PurchaseOrderDetails.Any()) throw new ApplicationException( "This product is a special unicorn and it cannot be deleted." ); } public void OnAdding(IWork work) { if (UserPreferences.NoDuplicateProductNames) { // the context is available via the work parameter // for testing more intense rules involving other // data in the system var context = work as SpecialUnicornEntities; if (context.Products.Count(p => p.Name.Equals(this.Name)) > 1) { var message = "A product with the same name already exists."; if (UserPreferences.ErrorMessageIntensity == ErrorMessageIntensity.Abusive) message += " Be more creative next time. Loser."; throw new ApplicationException(message); } } } }
[ Meddle on GitHub ]
[ Meddle on NuGet ]
Source: github.com
I began to question the most basic of my nerdly assumptions. Do I have the right connection string? Should I even be using SQL anymore? Is the fabric of the universe collapsing?
After a therapeutic session of pacing and taking in some Carl Sagan to re-staple my faith in the sturdiness of the cosmos, it dawned on me that this particular service call was in fact an HTTP request made from a browser. And yes, the damned thing was caching.
To remedy any further zombie data tomfoolery, I have here a NoCacheAttribute class that inherits from ActionFilterAttribute:
public class NoCacheAttribute : ActionFilterAttribute
{
public override void OnResultExecuting(ResultExecutingContext filterContext)
{
var cache = filterContext.HttpContext.Response.Cache;
cache.SetExpires(DateTime.UtcNow.AddDays(-1));
cache.SetValidUntilExpires(false);
cache.SetRevalidation(HttpCacheRevalidation.AllCaches);
cache.SetCacheability(HttpCacheability.NoCache);
cache.SetNoStore();
base.OnResultExecuting(filterContext);
}
}This meek mod merely intercepts the result, grabs ahold of the HttpResponse’s cache settings and beats them soundly about the head and shoulders until they are certain that they’re not going to cache anything that comes from this response. Like, ever.
Here’s How To Make Sure You’re Not Returning Zombies From An MVC Action [ Aptera Software ]
Source: apterasoftware.com
And I might have posted about it in a more live, less after-the-fact sort of capacity had I not been straight up engrossed in using this app to play along with OK GO and a few thousand friends.
Not to mention the rest of the show.
Source: thisamericanlife.org
Ani: 1, Fear: 0.
