At my workplace, I have taken over maintainance and development responsibilities of a C# windows desktop application. The application is compiled into a .exe-file, and linked to from our intranet page.
When deploying new versions of the application, the standard procedure has been to delete the old file, and simply replace it with the new one. However, the number of users are increasing, and it is becoming hard to find a time of day where no users has the application open.
I have researched a bit on how to force deletion, even if the file is in use, but all of the solutions revolves around a single computer / single user setup.
Solutions containing rebooting with Linux CD or whatever is not going to work for me, as it would simply be easier to upload new versions of the system with version numbers in the file name, and change the link path every time.
(We are also considering remaking the whole application from a desktop app, to a webapp)
Are there any easy ways to force deletion of a shared network drive file, which is in use by one or more users?
Recent Questions...
ما را در سایت Recent Questions دنبال میکنید
برچسب:
نویسنده: استخدام کار
بازدید: 147
تاريخ: جمعه
10 ارديبهشت
1395 ساعت: 16:10