Hi, The best way of doing this is exactly what you think is a bad idea. Store this dll in a well know location or source control and refer to it as part of your build process.
The Gac is actually a more complex structure than it appears in the simplified windows explorer view. You can investigate it from a 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 microsoft have a redist for it. You may need to bundle this as a pre-requisite. 2010 version. http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a941c6b2-64dd-4d0 3-9ca7-4017a0d164fd Dave -----Original Message----- From: Brinkmeier, Doug [mailto:doug.brinkme...@countryfinancial.com] Sent: 07 April 2011 15:43 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Building with a .dll from GAC 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.d ll" /> </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 SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. ------------------------------------------------------------------------------ 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
