[wix-users] Install Assembly to GAC without removing from the Target Directory
Christopher Painter
chrpai at iswix.com
Sat Sep 22 13:52:18 PDT 2018
That sounds right. 99% of my installs these days are straight forward single MSI with embedded CAB. I don't make CD/DVD media distributions anymore and if I was working on something big enough and complex enough to be doing all of this there is a good chance the DLL would be in two different micropackages anyways ( GAC -> Runtime.msi DLL -> SDK.msi )
________________________________
From: Edwin Castro <egcastr at gmail.com>
Sent: Saturday, September 22, 2018 9:00 AM
To: WiX Toolset Users Mailing List
Cc: Christopher Painter
Subject: Re: [wix-users] Install Assembly to GAC without removing from the Target Directory
Is it correct that smart cabbing only works if you use the same media for both files/components? I expect most people only use one media now a days anyway...
--
Edwin G. Castro
On Fri, Sep 21, 2018, 10:10 Christopher Painter via wix-users <wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org>> wrote:
That first mentioned work around isn't a work around. It's the expected behavior of the Windows Installer. The file in the GAC and the file in the installation directory are two different files in two different directories and hence require two components. WiX uses "smart cabbing" (recognizing files that are the same and placing them in storage only once) so your package won't be larger then it needs to be.
You are correct that the use of a custom action to self register the DLL into the GAC is not a best practice.
________________________________
From: wix-users <wix-users-bounces at lists.wixtoolset.org<mailto:wix-users-bounces at lists.wixtoolset.org>> on behalf of Ven H via wix-users <wix-users at lists.wixtoolset.org<mailto:wix-users at lists.wixtoolset.org>>
Sent: Friday, September 21, 2018 4:57 AM
To: WiX Toolset Users Mailing List
Cc: Ven H
Subject: [wix-users] Install Assembly to GAC without removing from the Target Directory
When we add Assembly=".net" attribute to a File element in WiX which points
to an assembly, it gets deployed to Global Assembly Cache. Even though it
gets deployed to GAC properly, it removes this file from the Target folder.
Is there a way to stop this from happening and maintain it in both GAC and
Target folder.
There are some workarounds like creating additional components for the same
file but maintain a copy of such files again in another folder so that key
path is maintained properly and the other solution is to install assemblies
to GAC using a custom action. But I am not so keen on using these. Please
help / advise.
____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
WiX Support | WiX Experts and Resources from FireGiant<http://www.firegiant.com/>
www.firegiant.com<http://www.firegiant.com>
WiX Support | Installation, Development, Deployment | WiX Experts and Resources from FireGiant
____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
More information about the wix-users
mailing list