I've been doing some research, and seeing a lot of posts about installing a
.dll to the GAC, but (at least to me) it seems like the much more common
scenario is just simply using a known .dll/assembly name installed in the GAC
in the build (just to deploy to the install directory). I won't know
command
prompt if you feel the need.
For example I have a version of the dll in
"c:\Windows\assembly\GAC_MSIL\Microsoft.ReportViewer.ProcessingObjectModel\10
.0.0.0__b03f5f7f11d50a3a"
I would of course check the legality of shipping this dll in your setup as it
may not be allowed as microso
M
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Building with a .dll from GAC
This may help if you've not seen it.
http://msdn.microsoft.com/en-us/library/ms251723.aspx
-Original Message-----
From: Brinkmeier, Doug [mailto:doug.brinkme...@countryfinancial.com]
Sent: 07 Apri
We are handling this scenario via automated query against a source control
repository, rather than at a binary level of the compiled output. We
investigated compiled output comparison as well, and it just was not a feasible
solution for us.
We handled this with a service account that checks-in
4 matches
Mail list logo