Hi,
Our product installs multiple web services on the same server box. Those web
services share some common product assemblies. The current setup has those
assemblies installed to the local bin directory of each application. During the
build process, the common dlls are binplaced into multiple places according to
the layout of those web services. Then a tool is run to generate wix merge
module for them. This results in duplication of the same binary in the msi,
which results in bigger msi and patch, and some other pains.
I am thinking of solving this by gac’ing the common assemblies. Searching the
web, there are different opinions on whether to put an assembly into gac. Some
says enterprise application should not install assembly into gac. Even in my
own team, there is different opinion on this. Some mentions problems with
product upgrade when assemblies are in gac.
I am new to setup and is owning the setup for the product now. I would like to
hear expert’s opinions on this before I start to make changes to this. Thanks
for comments and suggestions!
Thanks,
Zhisheng
_________________________________________________________________
Need to know the score, the latest news, or you need your Hotmail®-get your
"fix".
http://www.msnmobilefix.com/Default.aspx
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
