>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,

If there were a VFP .Net, what would it be...

1. The IDE would be gone, since .Net languages don't have IDEs.

2. Several assemblies would be created to support foxpro functions.

3. A compiler would be created which would convert all the VFP data handling code to use ADO.Net and the Looping and some other langague constructs would work.

4. A VFP data provider would need to be written.

5. Visual classes, my 'guess' is that VCX libs would go away and all class libaries would be converted to code base classes.

So, we already have 1, 2, almost 4 using oledb, 5 is just the way .Net works.

As far as 3, VB syntax is so close to foxpro it is hard to tell them apart.

What do you guy envision VFP.Net would give you that you can get with VB.Net, VFP Toolkit, VFP OLEDB provider? You would gain tons, see my previous messages.

Heck, I love foxpro too, but I don't NEED VFP.Net... I'd rather VFP stay as it is (standalone) and I will use .Net when I need/want that stuff.

BOb