Metin,

Sorry, I was talking about the .NET Vfp.runtime, I did not make that clear. Those files are at http://etecnologia.net/downloads/vfp.runtime.zip, are from May, but it should work.

For developing ASP.NET forms, you will have choice: We'll enable a VFP Project inside Visual Studio Shell, you won't need Visual Studio as we'll provide both an Isolated Mode and a Integrated Mode Package for that.

And we are running internal tests with a HTML WysiWyg Designer, running inside VFP in a VFP Form to provide an HTML Designer so you can design your form inside VFP and then with a click run it in the Web Server.

ASP.NET forms are popular for apps targeted for users in the run, think Sales Force or On Field Workers, that is why SalesForce.com is so popular, though it is a Web App (not ASP.NET based, but the concept is the same).



>Sorry, I'm aware from .NET, so I couldn't success again. I copied vfprenu.dll and vfp9r.dll. I thought my .net .EXE file won't needed VFP .DLL files.
>
>You talked assemblies, which files I need to copy there?
>
>You're talking about ASP.NET forms, that's great. But which environment will our developing environment for developing ASP.NET forms. Web environment not such user friendly for an account application but it seem it will be good alternative for windows terminal server.
>
>>Hi Metin:
>>
>>The error reported has to do that you need the VFP Runtime in the same directory of your app. Just put the vfp.runtime.dll and other needed assemblies in the same directory of your compiled exe. By the way the Online Compiler is really old (May 2007), we want to update that but we need to remove the preprocessor support from the compiler because of security reasons, and that is somewhat tricky.
>>
>>We are working with the target to achieve 100% compatibility and to the moment it looks pretty possible. With regards to compatibility, you should not have any need to change your code. Recently we added support for 4 letter abbrevs, and it allowed us to recompile a FoxPro library containing several thousand lines without changes. In fact almost all errors you get when recompiling your code are usually related to Missing Commands or Functions not implemented yet.
>>
>>We have recompiled and ran forms under VFP and under .NET side by side and they look so alike and works the same, that sometimes I confuse myself with what environment I'm running on ;-). Markus Winhard in his Session notes for DevCon Germany show that in translated automatically from German and here in the original German Text
>>
>>The compiler / runtime can do lots of powerful things like scanning, filtering, locating data, Visual FoxPro Forms, ASP.NET WebForms, ASP.NET Web Services, SQL PassThrough and more. Of course we need to polish the compiler / runtime, but to program in FoxPro and recompile to .NET is so great, that we are building all this in the the FoxPro language itself.
>>
>>
>>
>>
>>>Hi Samuel,
>>>
>>>What about compatibility and stability. I just tried that sample:
>>>
>>>? "Hello .NET From Fox"
>>>
>>>
>>>and got runtime error:
>>>
>>>Unhandled exception: System.IO.FileNotFoundException: Could not load file or assembly 'vfp.runtime, .....
>>>
>>>>Hi Scott:
>>>>
>>>>We expect to achieve that level 95% in the next 6 months. Sounds hard to believe that?, look at the remaining bits, those are the easier parts, the hard part (GUI, TableLayer, Data Access, SQL Passthrough, Classes, Visual Inheritance, OOP Model) are already done.