It appears that when I install/deploy my .NET 2.0 app using a Deployment Project within my app solution, the first time my app runs it checks the the MyApp.MSI in the location from where the install was originated.
Is there any way to prevent this behavior My app is NOT deployed as a ClickOnce app and is not published so I don't understand why this check is happening
My deployment files are:
Setup.EXE
MyApp.MSI
CRRedist2005_x86.MSI
What I usually do is combine these three files in a single WinZip self extracting to produce an end result of MyAppSetup.EXE. This all works fine with ONE exception, WinZip self extractor will remove the above 3 files from the temp folder it creates. This becomes a problem because when I click on the desktop shortcut to MyApp, it proceeds to search for the original install location -- which WinZip self extractor process has removed.
I assume .NET framework is doing this to be able to determine "repair" location Is there anyway to tell it NOT to do this
Thanks, Rob.