I'm not convinced that the VFP mtdll can't be "Unloaded" after being used by ASP.NET, but, I haven't seen a solution yet. A good place to check would be sites that have VB mtdlls and are trying to do similar things with ASP.NET. Personally, I have never had a problem requiring a restart in this environment (not including recompiles) - make sure you're using COMRETURNERROR and the VFP Session Class. As far as DLL hell, I don't think MS ever touted .NET Interop with COM as a solution to this, just the pure .NET environment. You still have to register the vfp mtdll on the web server (this doesn't qualify it as hell, though -imo-)...
>Basically I just have to do a restart which concerns me if this is going to continue to happen under heavy use. My client will not be happy if the server has to be restarted periodically when MS has touted VFP interop and the supposed idea that .NET handles DLL hell. Right now I have to reload and restart every time I recompile my VFP code and sometimes I have to restart when I haven't done anything.
>
>
>>If you're talking about recompiling that VFP mtdll after it's been run from ASP.NET, this has been a nagging question for a while now and I would like to see a solution too. While I can easily "Unload" a vfp mtdll application that's been called from ASP, without disturbing anything else, I get your same error after that same vfp mtdll has been called from ASP.NET. Unloading would be the smoothest, but, the only solution right now is to stop/start IIS (iisrestart).
>>If you mean you can run your vfp mtdll only once from ASP.NET, then probably you don't have a proper setup. See the source code for ActiveVFP and the ASP.NET demo at http://www.activevfp.com/avfpdemo2/default.aspx .
>>>I use a VFP8 interop DLL. I can run this web site once, close it, build and run it again without touching anything on my machine and all the sudden get an access denied error, cannot access tcweb.interop.dll which is the DLL in question. What's the deal?