Jon Fazzaro

20120515

Here’s what I did after I was finished shaking my fists at the sky during a torrential downpour.

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

aptera emphasismine

20120430

Hoist The Colors, Me Hearties.

Here’s the consuming code that shows the ImageResult in action:

public ActionResult UserImage(int id)
{
    using (var db = new ApplicationEntities())
    {
        var user = db.Users.Single(p => p.ID == id);

        // read bytes from database into a stream
        var imageStream = new MemoryStream(user.Image);

        // create an image result using the stream
        return new ImageResult(imageStream, "jpeg");
    }
}

See what I did there? In action.

How To Serve An Image From An Action And Otherwise Be An MVC Swashbuckler [ Aptera Software ]

Source: apterasoftware.com

aptera emphasismine

20120424

Here’s The Thing About Duct Tape.

What I mean to get at with all the jabber about our ubiquitous silvery adhesive friend is this: jQuery is arguably the duct tape of WebForms development, and its quick-fix powers over rendered markup are seemingly without limit. Use enough of it at once, though, and it will find ways of getting stuck to itself, or indeed to the hirsute wrist of your DOM. As your page’s once-blinding responsiveness disappears over the usability horizon, you shed a single caffeinated tear, and it dawns on you that getting this untangled could be a slow and painful affair. Perhaps involving plenty of unintentional hair loss.

Now, let me brush away that tear—in a totally non-creepy, platonic sort of way—as I submit for you today some tricks to get your jQuery just about as unstuck and performant as an abstraction over an interpreted language could ever hope to be.

Slow jQuery And The Thing About Duct Tape [ Aptera Software ]

Source: apterasoftware.com

aptera

20120229

It’s SharePoint’s world. We just develop in it.

Happy SharePoint developers understand its power and embrace its constraints.

If all you notice is how much the SharePoint infrastructure seems to get in your way, or you mope through your tasks under a cloud of “we don’t have to do it this way in regular ASP.NET”, you are sure to miscalculate your code’s relationship with its host, and many of the little decisions you make every day as a developer will be skewed, or even straight up wrong.

SharePoint Is Not A Platform For Developers. And That’s Okay. [ Aptera SharePoint Development ]

Source: sharepointdevelopment.me

sharepoint stockholm-syndrome aptera

20120216

So, maybe we only bother with the screen under the heading of backward compatibility.

Tomorrow’s more successful nerds will need to learn to see around the ways in which the traditional KVM interface to software has blocked in our thinking. What will be possible and probable when you can regularly expect to speak and think at your applications? What will the screen look like?

Consider that it’s the thrilling year 2012 now, and we are still making plenty of audio-only telephone calls. That’s not because the technology for video phones isn’t there. The ubiquitous Videophone never happened because the use case was fiction—a real telephone conversation involves walking, driving, or just not necessarily being presentable or stationary in any way.

What Does The Emotiv Headset Mean for the Future of UX Design? [ Aptera Software ]

Source: apterasoftware.com

aptera