>Hi Morgan.
>I'm sure Kevin or someone else will give you an answer but I thought I would jump in for a word or 2. We have the MM framework precisely because we are starting a large project. With 4 of us developing, even if we could spend full time on this project, the full scope of it is a couple of years in the making. I think the development time is going to be considerably shorter because of the framework. It also helps us utilize some good basic OOP proctices. Some of our early .NET work without the framework was pretty ugly.
>

I don't think it would take years. We were able to put together a rather robust Windows and Web Framework within a few months. We are continuing to add it. Using good OOP practices, that is just a matter of discipline and everyone should be able to discipline themselves for that. I mean for a large project, it seems only natural as the project progresses to progress your framework along with it. I think the .NET framework is solid enough, to be able to add that layer right between you and the .NET Framework.

>When looking into the frameworks, I think you need to ask yourself...
>1) Is it a framework or a "bag of goodies"? A bag of goodies can be great but it is not a well thought out structure for the foundation of project?
>2) Does it have a large enough scope to really be a foundation for what you are doing?
>3) Is it Rigid or Flexable & Extensible? If you can't extend and modify its functionalites to match your needs, then you are right about being trapped by the framework. Actually, you would always put a layer of inheritance between you and the framework anyway, so that should give you a measure of flexability.
>

But your right,that means a commerical framework has to match every standard that you want. Even if you add a level between you and the commercial framework, if you want to get into the inner works or something deep it makes it much more difficult. I think most people won't really learn the .NET framework as thoroughly if you have a commerical framework, between the developer and the framework. I think it hinders people from learning the real subtle nuasances of the .NET framework, also if you as a developer change companies you may not have your crutch to fall back on, and may be forced to fall back on the .NET Framework.

I think it is similar to cheating on a test:
You may pass the test in the short term, but you won't learn the material and when it comes to the big SAT exam you'll fail, and not get into college.

>As a downside, if your are just learning .NET and you get a framework, you have to learn the framework too. In the long run that is a small price to pay.
>

If it is a small project, then it isn't worth it. But I think developing your own framework may take a little more development time, but " In the long run that is a small price to pay."

Morgan