[wix-devs] NuGetable Build, Extensions, and Libraries

Rob Mensching rob at firegiant.com
Mon Aug 24 12:10:52 PDT 2015


What's the advantage of breaking out the extensions? If/until we push them to their own repo's they'll move at the same rate as the core toolset and there isn't any real advantage of testing them to ensure they can act independent of the toolset they were built with.

_______________________________________________________________
 FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

-----Original Message-----
From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On Behalf Of Heath Stewart
Sent: Monday, August 24, 2015 11:36 AM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Subject: Re: [wix-devs] NuGetable Build, Extensions, and Libraries

So if I break out the WiX extensions into separate NuPkgs per the plan outline below (probably without a dependency on the build toolset, since you could have a way of referencing them differently and just need the extensions), we can get those published?

As for wix3, we could do something similar internally for now. We are planning a move to wix4 but with federated authoring diverging further it may take a while.

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 Rob Mensching
Sent: Monday, August 24, 2015 10:03 AM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Subject: Re: [wix-devs] NuGetable Build, Extensions, and Libraries

1. Plan was to make it easy to switch from "MSI-installed WiX toolset" to "NuGet-installed WiX toolset" by simply installing NuGet package. Not sure how far I got down that path but I *thought* large parts of it were working. I haven't double checked lately.

To be clear, it is *not* the goal to make everyone use NuGet to get the core toolset. The Bundle/MSIs should remain option as an standalone installer.

2. I do not want to push NuGet packaged toolset down to WiX v3.x. I want to stop doing features in WiX v3.x so we focus on WiX v4.0. Otherwise, we'll not get WiX v4.0 out. This was the same problem we had with WiX v2.0 to WiX v3.0. We just had to stop adding features to WiX v2.0 to get everyone focused on WiX v3.0. Eventually, non-crashing/corruption bug fixes aren't fixed either and all focus is on WiX v4.x. It can be a bit painful (at least it was in v2.0 to v3.0) but right now focus on WiX v3.x is preventing progress in WiX v4.0.

_______________________________________________________________
 FireGiant  |  Dedicated support for the WiX toolset  |  https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.firegiant.com%2f&data=01%7c01%7cHeath.Stewart%40microsoft.com%7c02793962a77146847b6108d2aca5ec2a%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=HK2FjPbDVEmcbcdq2oXgGQVoUA1EcweGJHs3laGbCf8%3d

-----Original Message-----
From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On Behalf Of Heath Stewart
Sent: Thursday, August 20, 2015 10:59 AM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Subject: Re: [wix-devs] NuGetable Build, Extensions, and Libraries

Rob, I see you committed these. Was that the idea: to support Team Build-style builds (i.e. non-interactive enviroments)? I see that the wix.targets doesn't get imported directly, but I can fix that up or was there some specific reason you didn't?

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%7c02793962a77146847b6108d2aca5ec2a%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=q9xxy7eOptjuKFYOoKQI3wEeSM3SCoeYiIMykrvFa1Y%3d

-----Original Message-----
From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On Behalf Of John Cooper
Sent: Wednesday, August 19, 2015 11:36 AM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Subject: Re: [wix-devs] NuGetable Build, Extensions, and Libraries

I do that already with my "bastardized" NuGet packages for my installers--chiefly to carry around wixlibs for my custom actions and my UI, and to install targets for signing.

--
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 Heath Stewart
Sent: Wednesday, August 19, 2015 1:29 PM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Subject: [wix-devs] NuGetable Build, Extensions, and Libraries

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

We're looking to make some investments in a Team Build-friendly system using NuGet packages both for WiX extensions, libraries, and even the build itself. I talked with the NuGet project manager here and we discussed some short-term and long-term options, as summarized below:


1.      Short term: using .targets files to deploy content

a.      NuGet packages will include \build\{package-id}.targets files.

b.      Those files will reference any wixlib in a \wix top-level folder (we should not place under \lib just yet - more on that for the long-term solution) with item type <WixLibrary>

c.      Those files will reference any DLL in a \wix top-level folder with item type <WixExtension>

2.      Long term: process content (probably in something like \lib\wix) similar to reference assemblies.

a.      Needs to be detailed and discussed with the NuGet team at a future date when they have some more time.

I've started prototyping those changes and can get a feature and WIP started soon, but we also want to NuGet-ize build. I see in wix4 someone already got a start and I could break out the extensions as needed if there's no objections. But I wanted to verify the intent was that a wixproj would contain the typical NuGet.targets and reference these packages, such that "nuget restore" pulls down the toolset and wixproj files just build without even installing WiX.

We do plan to move to wix4 but have a couple steps to get there across the division, so is there any objection to me NuGet-izing build for wix3 (i.e. 3.11) in a similar fashion?

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%7c0ecdd08174474135e6a308d2a8c51724%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=Zpujp%2b%2fwVLhLUBVQWSyExQq5W%2fdJY1vHKVMo0LOGBmE%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%7c0ecdd08174474135e6a308d2a8c51724%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=1jhnfhca1paI7mjofnQdKk%2fQ0ae9PS0jbLMWucuEaoQ%3d

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.

____________________________________________________________________
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%7c0ecdd08174474135e6a308d2a8c51724%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=1jhnfhca1paI7mjofnQdKk%2fQ0ae9PS0jbLMWucuEaoQ%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%7c02793962a77146847b6108d2aca5ec2a%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=HK2FjPbDVEmcbcdq2oXgGQVoUA1EcweGJHs3laGbCf8%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%7c02793962a77146847b6108d2aca5ec2a%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=HK2FjPbDVEmcbcdq2oXgGQVoUA1EcweGJHs3laGbCf8%3d
____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/


More information about the wix-devs mailing list