Ok, minor facepalm moment here. It turned out that my component library project had a reference to my action library from when I was testing the action out before turning it into an extension. When this was combined with the reference created from the code, this created two references to the same thing in the same code, which gave me the error.
I removed that and it worked just fine. The lesson to learn from this is to double-check those references if you get into these issues. I'm considering raising a bug because a) this error was kind of bogus in that the second reference could have been safely ignored, and b) the error message didn't really point to the reference on the component library project. It was only when I was ready to give up and abandon the 'wixlib-in-the-dll' idea as a bad job that I spotted this extra reference. Thanks for the help On 11 July 2013 17:44, John Ludlow <john.ludlow...@gmail.com> wrote: > @Nick: > > Yes, I'm trying to use the extension in a library which is then used in a > setup project. The resulting project relationships would be something like > this: > https://docs.google.com/file/d/0BzqWyEdx-NBBeDM5ZlJGejRoNE0/edit?usp=sharing > > The reason for this is that the setup project is just metadata related to > the MSI itself. This makes it easy to include those components in some > other setup, or even a merge module, just by adding the correct references > to the correct projects. Is this not common practice? > > The other reason is that our body of setup code is sufficiently large that > we need to split it up somehow. > > @Blair: > > > The original error appears to be due to missing code in the extension. > > I'm not sure what missing code you were referring to here. > > > On 11 July 2013 02:50, Blair Murri <os...@live.com> wrote: > >> There are several ways to make the *Ref. One way is to author a <*Ref/> >> element. Another is to use CompilerCore.CreateWixSimpleReferenceRow(). >> Either works the same as the other. >> >> The original error appears to be due to missing code in the extension. >> The second error (caused by trying to workaround that first error) appears >> to be caused by making an explicit reference to the wixlib that the >> extension contains along with the extension (causing double references). >> >> > Date: Wed, 10 Jul 2013 13:57:00 -0700 >> > From: nickra...@hotmail.com >> > To: wix-users@lists.sourceforge.net >> > Subject: Re: [WiX-users] Duplicate symbol when using >> CompilerCore.CreateWixSimpleReferenceRow >> > >> > Okay, I maybe wasn't fully understanding the problem. :) So, you're >> saying >> > that you want to use your extension in another WIXLIB (unrelated to the >> > WIXLIB you used to build your extension)...but when you try that, but >> don't >> > reference the extension in your Setup project too, you get the error >> "Cannot >> > find the table definitions for...". >> > >> > As far as I can tell, you need to have the project reference for the >> > extension in both the WIXLIB and the Setup project. >> > >> > To make your WIXLIB work, i.e. to pull the contents of the WIXLIB into >> your >> > MSI (this may be the part you're missing?), you need to put a Property >> in >> > the WIXLIB and then use a PropertyRef that points to that Property in >> your >> > Setup file. This creates the link between the library and the MSI, >> pulling >> > in all of the contents (your components, your new extension elements, >> etc.) >> > that are in the library's Fragment into the MSI. >> > >> > >> > >> > -- >> > View this message in context: >> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Duplicate-symbol-when-using-CompilerCore-CreateWixSimpleReferenceRow-tp7587243p7587281.html >> > Sent from the wix-users mailing list archive at Nabble.com. >> > >> > >> ------------------------------------------------------------------------------ >> > See everything from the browser to the database with AppDynamics >> > Get end-to-end visibility with application monitoring from AppDynamics >> > Isolate bottlenecks and diagnose root cause in seconds. >> > Start your free trial of AppDynamics Pro today! >> > >> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk >> > _______________________________________________ >> > WiX-users mailing list >> > WiX-users@lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/wix-users >> >> >> ------------------------------------------------------------------------------ >> See everything from the browser to the database with AppDynamics >> Get end-to-end visibility with application monitoring from AppDynamics >> Isolate bottlenecks and diagnose root cause in seconds. >> Start your free trial of AppDynamics Pro today! >> >> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > > ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
