I have a VB.Net installer that I created that uses another program I wrote
to facilitate the install. The installer program I created
(System.Configuration.Install) handles the various events like
MyBase.AfterUninstall, etc. This program works fine but when I run the
installer on a network resource (a UNC path) it generates a
System.Security.Security exception before the program even starts. The .MSI
installer kicks off just fine, but throws the exception just when the .EXE
program starts.
Any idea on what may be happening?
Here's more details:
1. Launch Condition: Search for file C:\DELETEME.TXT. If file doesn't exits
start MyInstaller.exe using error message "Do you want to install?" and
URL:[SourceDir]\MyInstaller.exe
2. MyInstaller.exe runs and creates C:\DELETEME.TXT, backup some files from
any previous install by renaming them, then runs [SourceDir]\Setup.exe
3. Setup.exe runs, sees that C:\DELETEME.TXT exists then finishes the
install. The AfterInstall event in MyInstaller.exe deletes C:\DELETEME.TXT
When I run over a network I attach the process in visual studio and I can't
get past the dialog box "Do you want to install?". When I break in the code
from the exception it looks like I never even loaded MyInstaller.exe.
The installer works fine if the UNC drive is mapped, or if a local drive.
