I have spent some time revieing the various previews of MVC (and I like it a lot). However, the question of whether ASP.NET MVC is "better" than standard ASP.NET Webforms is a matter of opinion.

In fact, Microsoft go out of their way to make the point that MVC is different from Webforms and is just another tool in the arsenal for ASP.NET developers.

There are a number of things you gain from MVC - better testability, better control of rendered HTML being the most common mentioned.  But there are also a few things you lose, v13wstat3/Postback, the abstraction of a control framework over a stateless protocol (HTTP).

Unfortunately, while we may be able to utilise some of the new features introduced as part of the MVC framework (such as Routing and Abstractions), DotNetNuke is heavily in the Webforms camp.  Any module you build needs to inherit from a DNN baseclass - this in itself forces you to use the Webform paradigm, as the DNN base class is a UserControl.

In DNN 5 we have changed the requirements so that Modules just need to implement an Interface (IModuleControl) but there are still major differences in how we deal with Module Injection that would make it difficult if not impossible to support the MVC paradigm in our modules.