I created a report with VB and compiled it to a dll that's called from an ASP page. When I need to replace the DLL, the system will not let me replace it with out a reboot.
IIS. And why is it awful? We are not having any problems with it except that if a file is being uploaded at the same time my program is trying to pull it off the queue, the file get's stuck and I have to reboot the server.
What problems have you heard about?
Oh, it's just a personal preference thing. IIS's ftp has extremely limited functionality compared to pretty much all other FTP servers. And having grown up in a UN*X world where FTP can do _anything_, it just annoys me.
You should have the uploads go to a temporary directory and then replace the original only after the transfer is done. Or is that what you're doing? (That way, the file system, which is much more robust than FPT, has to handle synchronization, which it does quite well.)
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.