Upgrades are used to find and replace previously installed files. But if
there's nothing to replace, there's nothing to say the install can't
continue as a fresh install. If you need to not run the installer at all if
a previous install isn't there then try using a launch condition
Hi Nick,
Thank you for your reply. I think that is a better fit. I have also thought
IExpress and VBScript might be a simpler approach.
I admit what I am doing is unusual. I have an old pre-Vista legacy app that
used HKEY_LOCAL_MACHINE to store product key registration information. Under
This may no longer be an option, but an external manifest to that exe
would disable its virtualization and make it require elevation.
http://blogs.msdn.com/b/patricka/archive/2009/12/09/answers-to-several-application-manifest-mysteries-and-questions.aspx
---
Phil Wilson
On Tue, May
I created an upgrade containing an updated DLL that replaces a previous version.
How can I make the install require a previous version has been installed? Is
that not the purpose of Upgrade? I cannot get it to work as expected. The
upgrade is happy to launch without the previous version
(Sorry for re-post, the example Minimum and Maximum did not match my
description.)
I created an upgrade containing an updated DLL that replaces a previous version.
How can I make the install require a previous version to be installed? Is that
not the purpose of Upgrade? I cannot get it to
5 matches
Mail list logo
