>>Depending on how far advanced you are in .net and C# and how much you value your own time you might consider buying Strataframe or some other framework that gives you full source.
>
>
>I agree to a point; but, the main problem with commercial frameworks is the overhead in trying to support all options for all users. A lightweight home-grown framework that supports just the functionality you need is priceless in terms of resources and speed.
I would agree, but you have to admit it would be very good investment to have a full-framework chunk of source code to pillage for $ 700. You can certainly scavenge anything you need, study the code, get some great ideas, find a whole lot of very tested functions and utilities, and learn an immense about about framework building in general. As you know, framework design and construction is a very different animal from application development. Being an interior decorator is very different from being an architect. We've all learned a lot in programming from taking apart or tracing through real apps that actually work. I would contend anyone planning to do a framework would benefit greatly from the same kind of thing.
As to another point, in the .net world I think the "overhead" involved in using a framework - at least the one I use - is immensely less than in VFP, and is certainly less constricting in design.
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.
