Adam Hardy wrote:
MVC is never used as a term in the Microsoft world that I know of.
But this makes complete sense, in a sick way. In a MS environment, portability probably isn't as big a concern, and while there are certainly other reasons to use MVC, it strikes me that the biggest is to maintain abstractions between the various layers.
If you're a MS shop, you probably have SQL server, ASP and IIS -- and MS has little interest in making it easy to change this. So why spend time building up a MVC framework if you know that you're pretty much married to certain technologies?
No thanks.
Erik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
