The intellisense alone - along with snippets - make writing what I had assumed was unweildly verbose code feel like I'm on one of those moving sidewalk things at the airport where you just kind of walk along but you cover a lot of ground with little effort <s>

My two big complaints is that so little use is made of design time smart tags and the property window is so primative, in terms of being able to rearrange it, filter it etc. I have my VFP setup to F4 toggle to non-default props only etc and there is the new stuff that Hennig and those guys have done. But the VS IDE is amazingly extensible and the third party stuff - both free and commercial - is pretty impressive. ( Resharper and code outliner for example ) I'm in the process now of adding a lot of RAD stuff to my customized Strataframe.

We used to have that kind of energy in Fox but it has moved on. Sic gloria transit mundi.
<s>



>>Yep. It even gives you a choice to do that in code, if you want. Whereas in CLR you have a wide spectrum of choices: you can do it in code, or in code, and then there's in code. In case I forgot... code perhaps?
>>
>>I'm not saying it's bad, just expressing how below "just whelmed" I am.
>
>>Just... it's part of the visual studio, and it has to be done in code. VFP is not, ever since VFP7, and it can do this visually since day one. Looks like a paradox to me.
>
>You're so hung up on this one thing. As others have said, and I have experienced as well, it's a non-issue when your ready to work with the product. The IDE has tons on features that improve navigation and workflow that VFP does not have that can easily offset this one small pain point.
>
>Anyway, there is a Visual Class Editor for work on a class.(See screenshot). Maybe you didn't know that. Most folks work on classes by code (I think), but you can just as easily add properties, add methods, set values with the visual tool, much like (not exactly) VFP. (Correct, there's no visual subclassing, but again, I'm calling "so what, no big deal" on that). I say that from 16 years of dedicated Foxpro development. IT'S NO BIG DEAL.
>
>I love VFP visual class designing. I use it exclusively for my VFP app (all VCX, no PRG). Sure, I miss it in VS2008, okay. But guess what, there are many things VS2008 IDE does that VFP does not. I like that. If you keep whacking on this one issue (or the next one you could mention) then your not accomplishing a thing.
>
>Try programming to an interface in VFP. Try renaming a method in one of your base classes, and watch it lose all the method code you've added to that method in subclasses of that baseclass. Try extracting a code block to a new method and letting the IDE do all the work. Try collapsing sections of If/Endif or Case/EndCase in the code editor to make thing easier to review. Try letting the compiler find all your misspelled variable/property names as you type rather than getting an error when your app runs. Try creating enumerations (easily). Blah, blah.
>
>Some things are better, some things are worse. On the whole, I like it better, and wish I could snap my fingers to convert my VFP app to .NET/C#/WPF and move on from there.