Hi, Neil.

>There is another way to look at this. Everyone is focusing on a potential VFP.NET being a native IL compiler, why not move VFP to managed code and keep what we have? After all Visual C++ has technology that allows you to re-target existing C++ code for the .NET CLR (IJW) and I think everyone accepts that there is no advantage to VFP as a .NET language but a RAD tool running in managed code is a different matter.

This has being my approach to the problem all along. I would go that path for -say- VFP 10, when the Framework will be -suposedly- pervasive and ubiquous enough to justify the move.

I think it would be hard the MS mantains a Managed and an Unmanaged version, so we better ask for this then. Once running over the Framework, it would be not *so* difficult to give VFP access to most of its features.

See you,