Pingback from  ASP.NET MVC Archived Blog Posts, Page 1

Pingback from  Dew Drop - August 5, 2008 | Alvin Ashcraft's Morning Dew

Please change "no one will EVERY" to "no one will EVER" ... thanks.

Please make a Dimecast about the power of Interface-based programming.  I'm trying to grok it.

The attributes are likely sealed due to the FxCop performance rule: Avoid unsealed attributes.

I'd be weary about striving for everything to be interface based.

Putting interfaces in just for the sake of testing frameworks is adding extra moving parts and incurring extra maintenance costs. Because now each time you want to add on to something you have to add on to the interface and any classes that implement; plus your making a more complex system for the next guy to figure out/maintain/extend.  Fowler says something about that in an article.

That's almost as bad as having less/no security so you can test your application, or incorrectly scoping your properties or methods for a testing framework.  You're building the application for the customer, not the NUnit/NMock.  And to be fair, there is a trade off there, but there's also a point of diminishing returns.

To me it's the equivelant of saying (in 1998); no current video cards can support the type of vector graphic we'd need for this video game...we'd need at least 128MB of memory for that.  So let's just make all the game manufacturers out there use the current version of direct x, dumb down our game, and not let's try to solve the real problem, or put pressure on the manufacturers out there solve the core problem.

Feeding to the 'build more interfaces so I can test' is dangerous to our industry.  Myself and others have been testing for years without that, and while painful sometimes, I haven't traded security/maintenance/complexity for it and I rather have the occasional painful moment than add extra moving parts for a test framework.  You build your test once - you maintain and extend your application for years.  

Use interfaces where they're needed - where the interacting object is unknown and virtually anything that matches a certain signature.

Maybe as a community we should try to solve the problems we have with testing frameworks that cause us to have to hack our applications with unneeded interfaces, making methods public that should be private, reducing security, and in general just introducing more moving parts into our system.

Just food for thought.

Link Listing - August 5, 2008

Pingback from  Link Post For August 7 2008 | One .Net Way

Pingback from  Recent Links Tagged With "mvc" - JabberTags