Chris,
Well, it looks like you've found a workaround for now: just uninstall the
old version before installing the new one. It isn't pretty, but it seems to
be working for you. Sometimes, that's just what you have to do when you're
migrating from one toolset to another.
But if you want to keep
The old installer was an Visual Studio Installation Project.
The Old Version Number was 5.015.004 with an Different guid. So the wix
installer is Doing a Major Upgrade.
During the installation of the new Version the uninstallation of the Old
Version is scheduled.
During the uninstallation an e
Some confusion here - the original post referred to the failure of a
custom action because the Dll was missing, but is this now the custom
action you don't need, according to your earlier post? If the Dll is
called InstallUtilLib.dll than that's the Visual Studio Dll.
I was pointing out that mana
Chris,
Is your new version a "Major Upgrade"
(http://msdn.microsoft.com/en-US/library/aa369786.aspx), as opposed to a
"Small Update" or "Minor Upgrade"
(http://msdn.microsoft.com/en-us/library/aa370579.aspx)? Also, if it is a
Major Upgrade, then when is your RemoveExistingProducts action schedule
It was a c# Custom Action.
This Custom Action is Not deployed within the new wix installer because it is
Not needed any more.
> Am 15.04.2014 um 20:45 schrieb "Phil Wilson" :
>
> What kind of custom action was that in the original VS 2010 setup
> project? If it was managed code, VS 2010 insert
Hi,
Thx for the answer. The uninstallation of the previous Version is working fine.
The error is ocuring only during Upgrade within the wix installer.
The strange thing the CustomAction.dll is searched within the default targetdir
of the wix installer and Not within the targetdir of the already
Small correction: I meant to say, "we are going to ... create a dummy
installer whose sole purpose is ... to prevent [the custom action DLL] from
being removed when you UNINSTALL the first product." I.e., to make sure
that it is still around when the post-RemoveFiles custom action tries to use
it
What kind of custom action was that in the original VS 2010 setup
project? If it was managed code, VS 2010 inserts a C++ Dll to load a
framework and run your code via reflection. If so, you'd need to
migrate that to a DTF custom action. You should also check that there
isn't already a custom actio
Chris,
This looks like a bad design choice in the previous version. Most of the
time, you're going to want to embed your custom action DLL as a Binary in
the MSI package rather than installing it on the target machine as a File in
a Component. I.e., put the custom action DLL on a Binary rather t
Hi,
currently I'm updating all of our Visual Studio 2010 projects and choosed Wix
to support Visual Studio 2012.
Now all installers are running with Wix and are doing their job fine in Testing
environment.
Our AQ Department asked me to implement Updates as well.
One of our custom Installer has
10 matches
Mail list logo
