Guenter,
I could include a compiled version with each of the runtimes (VFP6SP5/VFP7SP1/VFP8). That should cover everybody - just pick the install for the version you have. The product is a totally free contribution by me that includes the great work that others have donated to the VFP community. The debugger is the work of Maurice de Beijer, for example. No plans to charge for it.
I should warn people that they should be logged in with Admin rights before the setup. I'll add this to the setup.
For #3, there is a project hook that should run automatically that unloads the VFP mtdll transparently. It's called iisdlll_hook.vcx and should be in ProjectInfo/ProjectClass for every web app. It's put there automatically by WebAppBuilder. That should prevent it from being locked in memory(unless you run it from ASP.NET).
Good luck and Merry Christmas!
>Hey Claude,
>some success for a change! :-) Did some further diggin´ and found out the following:
>
>1) You apparently realized a month ago in a thread with John Jones that it´d be a good idea to include the VFP(8) runtime. You surely would spare people one pitfall! Is your´s a one man show? Do you want to sell this some time? Action!
>
>2) I got the thing mostly running, both - on the Win2K VFP7 SP1 VFP8 runtime and the XP Pro VFP8 beta and VS 03 beta. 'Mostly' because only after creating the virtual directory manually. I got Admin rights,... on both machines, but I´m not logged in as Administrator.
>
>3) One last important thing: One cannot recompile the name.dll after showing in the IE. VFP complains that the file is in use. As the initial show fails anyway I didn´t try the freshly compiled standard page and edited 'Hello World' immediately and could recompile the name.dll without problems.
>
>Who could have the file in use? How to free it?
>
>OK. Thanx and relax for Xmas!
>Frohes Fest!
>G