Probably the biggest question you face as a developer every single day is “where to put your code”? MediatR notifications can help answer this question.
Left unchecked, tight coupling between components (especially when distributed around your application) can slowly kill your software; rendering it hard to maintain and much more likely to suffer from bugs.
How can we identify and reduce coupling in our applications?
Sometimes when deploying an Azure project to the local compute emulator I’ve seen this error message.
“The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.”
It’s a horrible error and I haven’t been able to fix it using any of the methods found via google (e.g. “your web.config may be readonly” or “your project might have too many files in it”).
The only solution I’ve found is to do a fresh checkout of the source code from TFS
I recently hit a requirement to take an array of objects and post them to an asp.net mvc action using JQuery’s ajax functionality.
I had to do a bit of Googling to work out how to do this so figured I’d document what I found.
The main two parts to this are getting JQuery to spit out JSON data and ASP.NET MVC to deserialize that data into a strongly typed generic list.
If you've read my previous posts on using Machine.Specifications and Rhino AutoMocker, you'll know I'm a fan of both frameworks. James Broome has released a really useful extension for MSpec which pulls MSpec and Mocking together in one easy to use package. http://jamesbroo.me/introducing-machinespecificationsautomocking/ It's well worth checking out.
Entities Entities are important. Maintaining the identity of an object is an important way to avoid data corruption.
“Their class definitions, responsibilities, attributes and associates should revolve around who they are, rather than the particular attributes they carry”
Eric Evans: Domain Drive Design – Tackling Complexity in the Heart of Software
I just had an interesting conversation with the co-editor of this blog which went something along the lines of…
BigMart: I haven’t had chance to dig into LINQ properly but I don’t like it Me: But delayed execution rocks (follow long rambling explanation) BigMart: For our next project I won’t be using that MVC rubbish Me: But it rocks! OK I’m paraphrasing and neither of us actually talks like that.
Just found an excellent article summarising various software design principles/concepts in one easily digestible post. The series will eventually cover building a robust application using Microsoft’s ASP.NET MVC.
Just spotted this article over on singingeels.
Looks like a useful read if you’re keen to use MVC but are concerned about Tag Soup
I’ve used various Dependency Injection frameworks in the last year or so and have yet to settle on any one in particular.
My focus has been on StructureMap and Microsoft’s Unity (I know I know everyone seems to dislike the latter for some reason but it does have its uses!).
On a couple of occasions I had to switch DI frameworks in the middle of a project. At first this was hard work as I had multiple references to the specific DI framework and had to change them all.