>>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.
>The word "Little" scares me. Eveytime I have a request for a "Little" change, or a "LIttle" feature, or a "Little" extra development time, I get bit by a monster. I feel it here, too. There can be an awful lot of hard work and time you are glossing over. In any event, though, you can develop with or without a framework and still turn out a good product. Or a bad one for that matter. No right or wrong to your choice.
>

I understand you terror from the word "little". I don't mean to gloss over the hard work it takes. The trial and error and slamming your head against the wall, but the point I was trying to make is that hardwork is more then worth. When a year and a half into the project, a client doesn't want to databind one field the exact way, and you have to totally understand how databinding works in the .NET to fix the bug or feature request.

It is a lot of hardwork, but it is more then worth it as a developer, as a business that is developing a large scale application. The reason I asked this question, was because I had just never seen the justification for using commerical framework's when developing a robust application.

The understanding and knowledge from developing your own framework, plus the customizablility and total control are more then worth it. Your right it is a personal choice, and not really right or wrong, but I just have never seen the reason to use a commercial framework for anything except small projects.

Morgan