OK, let's be more precise then because I think your statement implied that the same visual subclassing capabilities exist in C# that exist in VFP and that is not true. You can visually subclass a form (as you mentioned although it's not the same as you would do so in VFP) but not all controls can be subclassed visually and if new developers spend time trying then they will be spinning their wheels and getting no where. Naomi's statement is still correct I think except it could have been more precise: there is limited visual subclassing capabilities in dotnet. :o)

Note: I just read your post again and you are indeed correct. Naomi stated there is no visual subclassing in c# and you replied: that is not a true statement.

In that sense, you are literally correct :o)



>>? I understood it as accurate. You can certainly subclass (by typing the code to do so), but there is no visual tool or way of doing it like there is in VFP. Please, if I am wrong, then give me your steps to do it. I'd really be interested! I went through a few C# and visual studio courses and in all cases the instructors took us over to code to do it and they knew VFP.
>>
>>
>>>>>You're a better man than I, Gungha Dhun. I would rather eat worms than develop graphical applications without a graphical development tool.
>>>>
>>>>There is no visual subclassing in C#.
>>>
>>>That's not a true statement.
>
>
>Open a new Winforms project. Add something to the automatically generated form1.cs. Now choose add new item to the project and when the dialog opens, choose windows forms, inherited form (name it form2), and then select form1. You will add a subclass of form1 to your project named form2. Which you can modify at will.