>Yes, that could be improved, but, it could probably be automated to have minimal effect I think. Just curious, but, on a busy web site with ASP.NET, can you safely just copy over the dll without any problem?

Yes... ASP.Net doesn't actually run the local copies of the DLL, but copies them somewhere else. If a DLL loaded changes the entire app is reloaded with the new files and the old and new run simultaneously until the hits are completed on the old one. THe old one then just goes away.

Although this works most of the time without any hiccups, I've also seen on occasion a message that says that the app is loading or the server is unavailable. Very rare, but it it happens. Still it's automatic...

This is definitely an improvement even over the auto-update mechanism I have built into Web Connection which hotswaps executables via an admin link.

+++ Rick ---


>>>.VFP. mtdll web apps using no commercial 3rd party software can easily handle over 5 million hits a
>>
>>I agree with your mostly, though having to stop the web app to update an VFP DLL is a pain in the bum. It means either that I come into work at 6am or late at night or having to announce a downtime. Updating a .NET DLL is just a matter of copying the new DLL over the old one. Windows (or IIS) loads the new copy without a hiccup.
>>
>>I wish there was something that the Fox Team could give us to allow VFP DLLs to not have to be registered etc. Maybe some kind of .NET wrapper.