>When I was doing VFP I created a framework that I thought was quite nice. It worked well for me, and I even sold a few copies along the way. I was named FramePro. By developing FramePro I learned alot about VFP.
>
>So, I thought, "Why not do the same in C#?". I know there are plenty of off-the-shelf .Net frameworks, but by doing my own I can
>really learn C# and .Net.
>
>I'm asking for opinions.
>
>K

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.

In the case of Strataframe it would cost you about $700, it think. Now you have something to pick apart and study to your heart's content and decide if you want to use that and extend it ( which is what i am doing ) or start from scratch, picking up tips from a team of absolutely first-rate framework builders who have put literally thousands of man-hours into developing a framework that has been field tested by hundreds of developers and is used by the framework builders themselves in a very serious enterprise application that is used all over the world.

For me, whether you are going to use - and modify and extend you your heart's content - a framework like that or "roll your own" , it is a no-brainer to be able to get a look at that kind of source code for the price of a day's billable hours.

For me personally, writing your own framework is madness. Why not just start out in assembler and write your own OS and development language.

I think programming is all about leveraging the work of others. Of course the more in depth understanding one brings to that process the better, but there is a point at which making your own soap is just not cost-effective and doesn't really give you better soap.

I cannot imagine a single developer - even one highly skilled, experienced and who didn't need to actually make any money - could get a good ROI - or framework - out of "rolling their own" from scratch.