Hi Craig,

that's the good news (and it is good news). The bad news is that the ops of the VS IDE are still COM awkwardly living with .Net. I'm with Pertti: when they have aselobj() (btw: Frank Camp wrote it in 2 weeks, 4 years ago, in .Net) and building a form builder, and installing it, is as easy as VFP, then they will have reached a milestone, at least for those of us VFP developers who made VFP extremely productive by extending everything -- because VFP made it all so easy.

Hank

>It works now because VS2010 uses the Blend rendering engine.
>
>>IMO, with WPF Microsoft took a huge step backwards in the IDE department, because WPF development relies heavily on either XAML coding (yechhh!) or Blend editor (try doing LOB productively with that!) Now they are finally getting back to an earlier milestone where visual editing is back. Now if we could only have visual class editing and complete class inheritance, as well as a few handy functions such as ASELOBJ() as well as easy ways to create builders, we would be approaching VFP programming productivity... Ha -- the WPF abbreviation actually looks eerily similar to VFP! There's a conspiracy theory in there somewhere, I'm sure ;-)
>>
>>However, the future with VS looks bright to me at least now that various important missing pieces are falling into place. I can't wait for RTM versions of these three critical systems! Write-once-deploy-mostly may be close to a realized dream.
>>
>>Pertti