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 exact
location of the .dll, because this will be built on different machines, and the
exact location of the .dll will not be known. But, we can assume it is
installed in the GAC only. I've tried a number of different things, and nothing
has worked yet. Here is the component:
<Component Id="MICROSOFT.REPORTVIEWER.PROCESSINGOBJECTMODEL.DLL"
DiskId="1" Guid="939B1998-7A72-4D45-8269-9DEB5F1C6405">
<File Id="MICROSOFT.REPORTVIEWER.PROCESSINGOBJECTMODEL.DLL"
KeyPath="yes" Name="Microsoft.ReportViewer.ProcessingObjectModel"
Source="$(env.WINDIR)\assembly\Microsoft.ReportViewer.ProcessingObjectModel.dll"
/>
</Component>
I've also tried:
Source="Microsoft.ReportViewer.ProcessingObjectModel.dll"
This particular .dll is not installed on the hard drive anywhere, and only
exists in the GAC. I could hack around the issue by dropping it out to a known
location, but that's not very clean; I assume there should be a pretty easy way
to reference a .dll in the GAC, but I'm just not finding any documentation on
it.
Thanks,
Doug
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
