I agree with a lot of what Rip Ryness wrote. MM.NET and DotNetNuke really serve two different purposes. If you need already built functionality, such as a module to post links, a forum for users to post messages, etc., DotNetNuke is a great tool. There is a lot of core functionality in the product, and a lot of third party modules.

If you don't need that kind of functionality and plan on building most of your product yourself, MM.NET is a great tool. I think it's well-designed, continues to improve, etc., but a big thing for me is good documentation and support. I know that I can come here to ask questions and they will be answered in a timely manner.

>Greetings,
>
>I'm currently in the process of converting a very large set of systems from ASP and VFP applications to ASP.NET. Before beginning any of the actual development I was planning to consider some sort of ASP.NET framework to provide some structure and utility. Strataframe certainly looks good as does the MM framework. I've worked extensively with Codebook on VFP so I'm pretty used to frameworks that lean toward the complex side. The DotNetNuke project looks very interesting and would like anyone's impressions on the quality of the code for use as a framework for various projects.
>
>I would like to get peoples opinions on what frameworks work best. We will still have many VFP database to connect with as well as SQL Server and probably MySQL as well. So a framework that talks well with many different kind of database would be preferred.
>
>While I definitely would go with a commercial framework I'd kind of like to study any free offerings, particulary those that have some business object and data tier functionality to play with and learn from. I'm still a long way from going with actual development and I figure I would make a better decision on choosing a final framework if I were more knowledgable about how a typical framework would be constructed.
>
>Thanks for the help!
>
>Greg