Hi Dmitris,

>But how can the runtime be extented or take advantage of .Net if it based on an existing fxp which I suppose is produced by VFP (9?) itself.

Depends on what kind of interaction you think of. Guineu is not an attempt to create a .NET language based on VFP. That's what Samuel David is doing. My goal is to provide an alternative execution environment which allows us to keep using VFP even if new platforms turn out to be incompatible with VFP or political reasons exclude VFP. Interaction is possible in a number of ways, though.

For instance, you can create entirely new native bases classes in managed code and use them in your FoxPro code (of course only when running with Guineu as the runtime). It's also possible to create new functions in C# or VB.NET that are available to code in much the same way as FLL libraries today. Additionally, you'll be able to use CreateObject to create instances of .NET classes and access them in a similar manner that you can do with ActiveX controls today. I expect less interaction problems, though.

Guineu is a .NET assembly that can be used from managed code. You can use it to call FoxPro code from any .NET application. Both environments can interact. For instance, if you have an existing WinForm, Guineu can wrap this. To FoxPro code this would appear as a regular FoxPro form. Likewise, you can access FoxPro variables from managed code. When the data layer is ready, the same will apply to accessing tables.