>I am trying to learn C#. In VFP one of the recommendations was that before beginning any project to subclass all the interface objects and use them rather that the base classes provided by VFP. Is this a valid approach in C# and .Net?

You are thinking along the correct lines. The thing about .NET is that everything is new and we are all trying to learn what are the best practices. So yes, subclassing will be the best approach.


>There just seems to be sooooo much to learn in order to do anything meaningful in the .net environment and subclassing is orders of magnitude more difficult than it is in VFP. At the same time, I do not want to find myself months into a project and find out I had missed one of the basic steps.

Actually, Microsoft has made visual subclassing in .NET very simple. I *think* that dragging and dropping in .NET is true subclassing in .NET, not pseudo-subclassing like VFP. Also, in .NET you can make custom visual controls and components very easily, so do some of the Walkthroughs. I have found that if you are working too hard to do something in .NET, an easier way to get it done usually exists.


"Inheritance from a Base Class in Microsoft .NET"
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/classinherit.asp

-Dave