[wix-devs] Changes to linking between 3.7 and 3.10?

[John Cooper]

Yes, I remember that change.  Quite a hassle with my Wixlib projects, but a onetime pain point.

--
John Merryweather Cooper
Senior Software Engineer | Integration Development Group | Enterprise Notification Service
Jack Henry & Associates, Inc.® | Lenexa, KS  66214 | Ext:  431050 |JoCooper at jackhenry.com



-----Original Message-----
From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On Behalf Of Phill Hogland
Sent: Monday, February 29, 2016 9:30 AM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Subject: Re: [wix-devs] Changes to linking between 3.7 and 3.10?

The e-mail below is from an external source.  Please do not open attachments or click links from an unknown or suspicious origin.

IIRC - in the 3.9 there was a bug and related changes to address an issue in which the installed Wix Toolset did not have the same folder layout as the SDK files from the binary zip download. Those changes resulted in the need to correct linking when rebuilding my WixExtension project, etc.

-----Original Message-----
From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On Behalf Of Heath Stewart
Sent: Friday, February 26, 2016 4:45 PM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Subject: Re: [wix-devs] Changes to linking between 3.7 and 3.10?

I did some digging internally and also found that this was done not because of "lazy source", but because quite a few teams were using the early prototype of swix to build wixlibs that, when linked with products built using traditional wix, cause this issue. So it's not something we can really fix in sources.

Heath Stewart
Visual Studio, Microsoft
http://blogs.msdn.com/heaths


-----Original Message-----
From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On Behalf Of Heath Stewart
Sent: Friday, February 26, 2016 2:33 PM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Subject: Re: [wix-devs] Changes to linking between 3.7 and 3.10?

Well, look at all the "wrong" stuff for a couple hours to no avail, send email, and find it within a few minutes. Seems an internal change didn't make it out, which led me to https://github.com/wixtoolset/issues/issues/4244, which was closed in lieu of a proposed wix4 feature: https://github.com/wixtoolset/issues/issues/4259

We need this to (hopefully) complete migration. We will slowly be migrating things to wix4 but have to keep the wheels turning. I've opened https://github.com/wixtoolset/issues/issues/5227 since I couldn't reopen the original bug and would like to propose making this an optional feature for WiX 3.11.

Heath Stewart
Visual Studio, Microsoft
https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fblogs.msdn.com%2fheaths&data=01%7c01%7cHeath.Stewart%40microsoft.com%7cecb8375457bb44c617ef08d33efcd56a%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=tARTVUHmZd4ZDl%2b21QJBJSuLGmyoFrMyKn7omcegjcI%3d

-----Original Message-----
From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On Behalf Of Hoover, Jacob
Sent: Friday, February 26, 2016 2:23 PM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Subject: Re: [wix-devs] Changes to linking between 3.7 and 3.10?

A bit more info would be helpful...  What symbol?  Any error messages / logs?

-----Original Message-----
From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On Behalf Of Heath Stewart
Sent: Friday, February 26, 2016 4:18 PM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Subject: [wix-devs] Changes to linking between 3.7 and 3.10?

In the course of upgrading our tools to work on 3.10.2 from our 3.7 internal source (plus fixes - almost all of which are now in OSS), I'm hitting duplicate symbol issues when linking some wixlibs into MSIs - all built from scratch with each version. I've been trying to track down what's changed and, after a while now, thought I would ask in parallel while I try to track down differences if anyone knows of something that could've been introduced to cause this.

I've looked for differences between wix2010.targets file and MSBuild output and nothing stands out as a cause. Going to start diff'ing sources but maybe someone knows something off hand that could pinpoint the problem.

Thanks,

Heath Stewart
Visual Studio, Microsoft
https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fblogs.msdn.com%2fheaths&data=01%7c01%7cHeath.Stewart%40microsoft.com%7c6a8976bdd41141ac0c8208d33efb6c8d%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=8gAAJTC29NfH8R4XRiLzm8ZarQOekb7dfljD%2b9%2bu2AY%3d

____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.firegiant.com%2f&data=01%7c01%7cHeath.Stewart%40microsoft.com%7c6a8976bdd41141ac0c8208d33efb6c8d%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=z%2bg5wCUJ4CVywk2rDAyfiwiDMpW8dh0D6GcR7fom00s%3d
____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.firegiant.com%2f&data=01%7c01%7cHeath.Stewart%40microsoft.com%7c6a8976bdd41141ac0c8208d33efb6c8d%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=z%2bg5wCUJ4CVywk2rDAyfiwiDMpW8dh0D6GcR7fom00s%3d
____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.firegiant.com%2f&data=01%7c01%7cHeath.Stewart%40microsoft.com%7cecb8375457bb44c617ef08d33efcd56a%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=DbnV5OSi4NKBdl835axxhEQQIFi%2bzR7mylvObofNiVw%3d
____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/ ____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/

NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.