Joel,
Yes, ASP.NET locking into memory is currently a problem that I'm researching. However, try your experiment loading a .vfp. mtdll from ASP using pooled or high isolation. Should be no problem at all. As a matter of fact, what could be done is to develop and prototype everything in ASP and then deploy using ASP.NET. If you've ever looked at AVFP, this is a simple thing to do since the exact same mtdll is being run from both...
>Hi Claude,
>
>>As I've said before, you can easily unload .VFP. mtdlls called by ASP either by pressing the Unload button in IIS MMC or automate the unload in a .VFP. project hook. This assumes it's running in Pooled or High Isolation mode. I'm not convinced you can't manage the server remotely either (I'll be trying this in AVFP 2.5).
>>
>
>As a test, I once created an ASP.NET application that called a VFP MTDLL. I set the app to High Isolation, but the Unload button stayed disabled. I restarted the web server, etc., but the button remained disabled. I assumed it didn't work with VFP MTDLLs, but perhaps I was wrong. Any ideas?