If I ran into these issues in just a few minutes of usage what other things are actually not working correctly? I can't imagine that I would trust a monkey patched runtime which even under the most ideal conditions and rigorous testing would be extremely error prone. It doesn't load by default out of the launch folder or an explicitly assigned folder with -c.Īlso noticed that the desktop icons were not always showing up when running the application either in file more or in COM (interactive) which is weird. config.fpw doesn't get loaded on VFP startup, so all environment settings didn't work from there.This one is annoying since I use config.fpw for most of my path configuration: While the application itself runs there are a few little problems with the IDE I noticed even in the first few minutes of using it. Even runtime installation will require installation of the VFPA patch tooling, unless you use the explicit Runtime Compiler that bundles everything for you.
If you need to get the IDE installed on a few machines it's going to be painful to remember exactly what needs to happen and what needs updating since the installer isn't doing it for you. Neither of us has any idea what needs to be installed for these resource files (The vfprenu.dll and vfpenu.dll files). It only worked after Eric was kind enough to send me his files. I couldn't work around this with no idea where to get the later resource files. The VFPA installer didn't want to work with my resource files. Using Eric's notes I was able to get VFP updated, but I ran into a problem with a mismatched version of VFP resource files after a fresh VFP install of VFP 9 -> SP2 and the Hotfix 3. You have to manually copy files if you need to update to VFP Hotfix 3 and VFP Advanced basically creates a new patched version of VFPA.exe from your VFP9.exe and the runtime dlls.Įric Selje's article from SW Fox is the best reference for getting started - the 1980's style Web site has almost nothing in the way of how this is supposed to work. What exactly is required is not actually mentioned on the site.
It depends on an existing Visual FoxPro 9 installation that has to be patched to the latest version. NET Core Web Server locally, in COM mode, running the Web Connection server as out of process COM objects. The good news is, it works and I can get it to run through all of the Web Connection demos and the message board so that's a good sign. VFP '10') and run it through some basic Web Connection tests.
So in response to some messages here over the last few weeks (I guess after SW Fox), I tried to set up Visual FoxPro Advanced (ie.
0 kommentar(er)
