In the limelight these days you hear a lot of jabber about MVP, MVC, MVVM, MVKVM, MVMLK, MVMTV and any other MV… you can think of for ASP.NET. These architectural patterns are great but the most stable, testable and maintainable code is still written in traditional web forms development. Microsoft created web forms development to be a practical and easy to understand way to separate your concerns. By separating your business logic code into the code-behind, you make it easy for designers to run with the design of the UI without crossing wires with your business logic code. Using one of the MV* architectural patterns complicates you application unnecessarily. It leads to Inversion of Control and Interface segregation which is only going to complicate, what should be a really simple concept. The MV* patterns are simply a wave of people trying to coin something to gain some kind of name recognition.  Developers that use these patterns are usually the same developers who use ORM for their applications DAL. Basically, ORMs are for developers who don’t have the requisite SQL skills to write sprocs for their data access. Using sprocs is the most definitive separation of concerns. You actually separate you’re data access into a whole other application! Furthermore, Behavior Driven Development is simply the impatient man’s unit testing. It’s mainly for those who don’t have the patience to wait until all the requirements are gathered for a project and all the development is done. While I’m on the subject… damn, I just can’t do it. I just can’t continue with a straight face.

Happy April Fool’s Day!

~Lee