Hi Matt

I just thought that I would throw my 2 cents.

Our group has been using the MM.NET framework for the past 4 years, and have found it an excellent choice.

I think an important point to remember here is that there is no "right" answer to your question. It is more a case of "best fit". Also remember that an Application Framework is simply another tool and not a solution. It is up to you (using your tools) to create the solution.

So in some ways exactly how an application framework does something is less important than its ability to provide you the mechanisms to alter that behaviour. This is all the "..ilities" ie extensibility, flexibility, scalability etc that need to be considered.

I mean look at what Microsoft is doing with the .NET framework itself. They are programming to interfaces and not implementations so if you don't like what or how the .NET framework does something then override it and do it yourself. This is exactly the approach taken by Kevin and he's MM.NET framework.

Built on a solid foundation of design-patterns, i found MM.NET to also be an excellent "teacher" of best practice coding techniques, allowing me to learn and grow as a developer while using this tool.

In regards to learning curves, don't kid yourself, there WILL be a rather large learning curve with ALL application frameworks. It does take time, and the MM.NET forum here on the UT provides access to the entire MM.NET community (as well as Kevin).

Just a brief work on training. Our group travelled to LA to participate in one of Kevins training courses. I would say we learnt just as much about Visual Studio, the .NET framework, OO techniques as what we did about MM.NET itself.

I believe it is in these areas that the MM.NET framework excels and is very competitively priced.

Regards
Darren

PS
A very happy MM.NET user.