@Nathan: Did you mean WebForms? ;) Anyhow, I agree with Nathan's observation. Whatever you can do with ASP.NET MVC, you can also do it with WebForms. As for the MVC (or MVP) pattern, well it's just that...a pattern. One that can be applied for WebForms solutions. For one enterprise WebForms application, we used the Smart Client Software Factory (code.msdn.microsoft.com/.../View.aspx) with the MVP pattern. You still get the core benefits of ASP.NET MVC, but with much more features out of the box provided by WebForms (viewstate, web controls, etc.). One objection I hear the most about switching to ASP.NET MVC is that not too many developers know how to write proper unit tests (mostly because the existing tools are too hard to use or not as expressive as they should be), so more often than not, developers will either choose "No, don't bother creating a unit testing project because I don't know much about it", or "Ok, create a unit test project, but please compile even though there aren't any tests". I haven't played with ASP.NET MVC, but if I'm a newcomer to .NET web development, I think I'd still prefer WebForms over it....at least until I know what ASP.NET MVC v2.0 will offer me. Image may be NSFW.
Clik here to view.
Keep up the great writing Maxime!
Clik here to view.
Keep up the great writing Maxime!
