Files in Use during a Wise Update
In my .Net Windows application, i have a button on the application menu where a user can click it to check for udpates to their software.
It essentially has some custom code that checks some ini files on our webserver that contain the latest version information as a first step, and if it realises their version is different to the current version, it executes the Wise Update that i packaged/depoloyed with the software installation. (i know that you can run Wise Update on its own, and it will check if there is a later version or not, however i want the app to check it slitentlym and only run wise update if there is an update required)
When the Wise Update runs, it detects the new version and downloads the installer exe for the new version and then runs it. However during the installation/update process, it complains that there are several files in use;
- DF (our .net application name)
Now i understand why it would complain about our application being in use (since it is trying to update an application that is running), however it seems strange that it would complain that the TMP file and Wise Update is in use, considering Wise Update is the one that initiated the install.
- Any ideas on what i might be doing wrong? Surely WiseUpdate should be seamless and not complain about itelsf running?
- Is there an issue if we force these processes to be killed before the update?
- If so, what is the best method to kill a process in Wise? ( i have seen several posts with different methods - not sure what is the best, such as PV.exe or taskkill.exe)