HeartattacK

NuGet is a very nice addition to the .NET developers’ arsenal. It is a central place for every library and framework in .NET. It has pretty good tooling integrated into Visual Studio and the command line options are pretty sweet too. It can pull down specific libraries including their own dependencies saving the developer a lot of time and effort in figuring them out manually. For the continued growth of the open source .NET community, NuGet is pretty much something that should have happened years ago. Yet there are some things about NuGet you need to be careful about.

Crossposted from www.heartysoft.com

One week after DDD Belfast, I was up in Sunderland for the first ever DDD North. The session line-up looked fantastic and it geared up to be a fantastic day.

After repeated attempts to resume blogging, I think I’m pretty much determined to end my hiatus. And I’ll start off with my experience at DDD Belfast....

Ashic looks at a gotcha when returning a view with a string model from a controller in ASP.NET MVC.

Ashic shows a trick that can make overriding more flexible, specially when stubbing for tests.

Ashic discusses why some data is best passed in via the ViewBag dynamic as opposed to strongly typed viewmodels.

I just published MSMSpec - my latest project. It uses T4 to extend your MSpec test classes so that they can be tested by the MSTest runner. And it comes with NuGet awesomeness. Read all about it here:

Say hello to SeleniuMspec!