Yes, the primary thing is that you can debug using the ASP intrinsics(request, response, session, etc) from within VFP. Using the "file-based" approach would have only tried to mimic this and would have been much less effective not to mention difficult to integrate into the framework. it should save a lot of time.
Not having done it with ActiveVFP yet, I would suggest you look at the places where he calls the VFP mtdll(starting with main.prg) and see if it's possible to substitute your mtdll. Also, making note of where he's using the flag to check for debugging...
>Claude:
>>yes, I tried it and it works as advertised.
>Grrreat !
>
>>I was going to use a "file-based" ISAPI connector for debugging, but, this looks much cleaner and smoother.
>I assume that this was what was taking the time/causing the headaches?
>
>>As soon as I finish something else I will do V.2 that will include greater ease of use generally and ASP.NET functionality using the same VFP mtdlls used for ASP.
>That's great. I presume that V2 will include patching in the various bits of code required to implement this new solution via the ActiveVFP setup wizard?
>
>Could you let me know what bits need changing (pathing mostly) to run this solution with 1.5, or are you working around MDB's file structure?
>
>This is a really tremendous bit of news. I bet you couldn't believe your luck when this one surfaced!
>
>Best
>
>-=Gary