Hi everyone,
Is there any way to check the integrity of the installer before the setup
wizard is launched?
I have one setup package which is downloaded over internet, and I would like
to ensure that something like an error message will be displayed to the
client in case the installer is damaged wh
Hugo,
I think that's what the signiture verification is for. Even if you
were to suppress it, burn will do a hash check on the file.
If it fails the hash check, burn does not trust the file and retries.
I'm not sure about catching the error.
You could attach to:
Boot
More on the KB breaking Windows Installer thing from my colleagues.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6
keith.doug...@statcan.gc.ca
Telephone | Téléphone 613-854-5589
Facsimile
In your existing target, where you are using HeatDirectory, you could try
something similar to:
Note, DateCompare is a simple custom MSBuild task which compares to dates for
equality giving results of <, =, or >. If your
I'm trying to prepare an uninstall since colleagues insist we deploy the update
to our remotes, regardless of the danger ...
Uninstall commmands to our bundle that we might try to use seem to only
uninstall the bundle, not the contents. We send [bundlename /uninstall /quiet]
from our elevated s
That is what I use (and I also use /norestart). I don't have MSUs, just
MSIs, but they now uninstall consistently. Many months ago when I first
implemented this I saw situations where the packages were not removed. I
think that happened when I tried to call the cached version of the bundle
(usin
6 matches
Mail list logo
