We’re all programmers, right? We want to constantly improve our software and make the right choices about what to build. Since we’re all good engineers, however, sometimes it’s time to cut features. How will that impact the users? Do we even know if the users use a specific feature? One way is to remove the feature and see who complains. But there’s a better way. Telemetry Telemetry lets us watch what the users are doing without standing over their shoulder.…

A while back, I posted how I used StructureMap along with the new ASP.NET self-host features to do integration tests on my ASP.NET Web API. Since that post, I’ve tried out Ninject with some new projects and, thanks to Filip, I discovered In Memory Web Hosting. This post will go over how to integration test an ASP.NET Web API project that uses Ninject for IoC and in memory hosting. I borrow from Filip’s post with adaptations for my purposes.…

Sometimes, what you really want is failure. Success is great. Hooray! The crowds roar at your continued success. But in reality, everything is not peachy. Developers choose to ignore failure planning to their peril. Me? I need ASP.NET Web API to fail. In one of my projects, I utilize the ASP.NET Web API for the heavy lifting. My JavaScript and jQuery code make a lot of AJAX calls to the API and so far, I’ve got all of the success handlers written.…

One important change from the Beta of Web API to RC was the way it handles IoC. So far, there have been a few guides of how to do it with Ninject or Unity, but I’m still using StructureMap for many of my projects. In a previous post, I showed how I used StructureMap in an integration test of Web API using NUnit. However, that was against the Beta and was in the context of automated testing.…

Update 2: I have written a new post going over how to setup StructureMap with the RC of ASP.NET Web API. Go check that out as well. Update: This post was written against the Beta of WebAPI. Word out is that this will change for the release candidate. I have not yet done a new post for the release candidate. You can read some about these changes here. I intend to write a new post once the RC has been released.…