I have had some similar problems with installing services and they are
not necessarily related to the current install.
My scenario:
1. Install a service
2. Do update install of new version with incorrect account or
password - the install fails and rolls back
3. Retry install
The generated setup.exe file behaves as you desire and only downloads
files that it needs to install. Only those files that are necessary to
determine if a package needs to be installed (such as dotnetchk.exe) At
least this is my experience.
From: [EMAIL
The documentation for GenerateBootstrap (actually the files it uses) is
buried in the ClickOnce section. Using that information, combined with
looking at the files that MS supplies for the prerequisites, we managed
to create a bootstrapper for our Wix based deployer.
I have had problems where I used a property to specify the
web address and because the property was not set at uninstall time, the
uninstall failed.
The trailing // in the key makes me suspect that you may
have created a virtual directory whoose name came from a property. At uninstall
Another place to look is in the .Net 2.0 Bootstrapper and the MSBuild
GenerateBootstrapper task. With a little help from Google, it is
possible to find information on using the 2.0 bootstrapper with any old
generic MSI. By referencing the correct package, one can create a boot
strapper that will
5 matches
Mail list logo
