I am working on an upgrade scenario where my app is already running. I want to avoid killing the process with brute force, because it lacks certain clean-up.
The app is .NET app. It normally runs without a visible top-level window, but it has a displayable configuration window.
Being a single-instance app, I can handle the case where the newly installed version starts (and automatically exits) and then gracefully restart the running instance. Since the new executable has been installed, such restarting effectively starts the new version. This seems to work fine.
But when my app has a window open on the desktop, for some reason AI then detects my executable as "in use", and displays the FilesInUse dialog.
So many questions:
- Why does AI consider the exe "in use" when it has a visible window, and not otherwise?
- How is AI able to successfully overwrite the exe in either case, while my app is running?
- How does AI determine that the exe is "in use"?
- Can AI's "file in use" function be controlled, modified, disabled?
FOLLOW US
Get the latest news in Application Packaging