>>...the only advantage could be use more up-to-date looking controls. I guess it would be far easier just to revamp the standard ActiveX libraries (or even VFP internal controls themselves).

Yes... part of it is most definately more up-to-date looking controls, and I'll take those any way I can get them, updated VFP controls would be great! But there are also special purpose controls that I write now in C++ using ActiveX, I would be willing to give C# a shot for them if I could actually use them on my forms. Right now I have no way to do that so C# has very little appeal to me.

>>In any case, I don't see any of this ideas matching with what I understand as the VFP Team roadmap.

"Features in Sedna will target Visual FoxPro interoperability with application components created by using Visual Studio 2005, the .NET Framework 2.0, and SQL Server 2005."

How does the ability to host dot.net controls not fit in like a glove with that statement from the road map?

Now... from something Ken said to me earlier in a post here on UT... I suspect we won't be getting this particular feature, but that's not reflected in the roadmap itself and I don't see anything in the roadmap that would make this idea be out of the question. From the responses to this thread it seems I'm not alone in wanting this feature. It would actually make it far more likely for me to code stuff in C#, I think it would be a smart move to include it.