>>>>More seriously, I agree with you completely. Designing one's own framework probably would be an interesting technical exercise, but economically it doesn't make a lot of sense.
>>>
>>>Depends on the situation. When we first started our application back in very early 2002, there wasn't a whole lot out there yet. We wrote our own framework for that reason. It was fun and challenging. And now it's an old framework, based on some older technology ... but it still works great and, when I left, there was really very little that needed changing. Except for change just for the sake of change ... which is not always a good thing! <g>
>>>
>>>~~Bonnie
>>
>>Agreed, obviously. If there weren't pre-built frameworks available you didn't have much choice.
>>
>>One factor is whether one works for a company or is an independent. I know Charles was speaking as an indie, as was I. If a company is willing to pay you to roll your own, terrific!
>
>Or if the needs dictate a framework that is specific to the application of the company. If I am not mistaken I think Strataframe started because of a company need and not as a framework for sale. I think it was later they realized it would be a good product. I am sure Charles knows more about that.
>Tim

That's pretty much it. They had a huge medical app in Foxpro and to move it to .NET they couldn't find a framework so they wrote one. Then they got pretty interested in frameworking (the money is still in the medical app). Since the medical app required very fast performance on huge record sets over WANs they also developed the proprietary Enterprise Server which is really pretty cool.