>>>>I first cut my teeth on FPW 2.5 back in '93, and over the years I've come to really love the critter.
>>>>
>>>>So, when VS.NET came along, naturally I was skeptical.
>>>>
>>>>But you know what? I'm amazed that I'm even thinking things like this, but I do believe I'm becoming a bit spoiled by its great code editor.
>>>>
>>>>Is there any cure for this malady?
>>>
>>>Unfortunately not, and going back to Fox without the automatic indentation, immediate error-checking etc.etc. it's hard, so yes, I agree that it does sometimes feel like you're being spoon-fed.
>>>
>>>Kev
>>
>>Kevin;
>>
>>I have taken several .NET courses and have learned something interesting each time about the IDE. It is a great IDE and very useful. Learning how to use it is only one of the challenges of learning .NET. :)
>>
>>Tom
>
>Tom
>
>As if learning the product itself was not enough :-)
>
>Saying that, however, I find a few annoyances, particularly the fact that you can't view a Class's properties/methods from the properties window unless you're in design mode.
>
>Plus it's hard getting used to purely coded classes after creating visual classes.
>
>Kev

Kevin;

I know what you mean. Working with VFP classes can be as easy as drag and drop or you can write each line of code to create a class – I have done both and prefer the former.

Within Visual Studio .NET, selecting from the View Code, or View Designer icons is limited as you have to then go to the opposite diagonal of your monitor to select Design or HTML. One thing I wish you could do from the .NET IDE is within the Solution Explorer, to have the ability to switch between Code Behind, HTML or Design Mode, just to speed things up.

Tom