[wix-devs] NuGet

[Rob Mensching]

1.       FireGiant published the one task. The WiX account as created a while ago getting ready.


2.       If you get the bulk of the Publish task working as part of the site build "Push" I can do any final tweaks. Should just be an Exec task around nuget.exe, right?


3.       Until we break those projects out into standalone repos (something I'm considering more seriously every day) I think they should follow the WiX release cadence.

Actually, now might be a good time to stop and have the conversation about standalone repos since I'm thinking more and more it's a good idea.

I'll start a thread on wix-devs.

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

From: Heath Stewart [mailto:Heath.Stewart at microsoft.com]
Sent: Friday, July 24, 2015 11:35 AM
To: Rob Mensching <rob at firegiant.com>
Subject: RE: NuGet

WiX already publishes NuGet packages (in some form)? Or are you referring to http://www.nuget.org/packages/FireGiant.BuildTasks.AzureStorage/?

I do see http://www.nuget.org/profiles/wixtoolset so I'll use that. Since there's nothing there already, could I get a copy of the key temporarily to test and then you can generate a new one when done? Or do you think the publish code should work just fine as-is if I plug in?

When do new versions get published? We don't change DTF much (or even Dutil, though more relatively) so we probably don't want to publish with each weekly build, or should we just for ease?

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

From: Rob Mensching [mailto:rob at firegiant.com]
Sent: Friday, July 24, 2015 11:22 AM
To: Heath Stewart <Heath.Stewart at microsoft.com<mailto:Heath.Stewart at microsoft.com>>
Subject: RE: NuGet

Cool. I've been hit by several surprising things lately so I'm not getting to this quick enough.


1.       There are already accounts for wixtoolset and firegiant.

Sean made a good point about the .nuget packages not being uploaded until the site is published. He sent a pull request to just upload the built .nuget packages to storage during the official build. So, if you wanted to extend the site pull/push such that the .nuget packages are downloaded from azure storage and uploaded to nuget.org when the site is pushed, that'd be cool.

2.       The root namespace for everything should probably be "WixToolset". DTF namespaces are already updated. Dutil should probably "WixToolset.Dutil".



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

From: Heath Stewart [mailto:Heath.Stewart at microsoft.com]
Sent: Friday, July 24, 2015 10:22 AM
To: Rob Mensching <rob at firegiant.com<mailto:rob at firegiant.com>>
Subject: NuGet

We're starting to build up some of our tooling and while I've created internal NuGet packages from our internal sources, your "fork" has some bug fixes that would be good. So I'd like to take that NuGet bug and make traction on it - specifically NuGet packages for DTF (multiple packages that more or less match the various assemblies since most are optional / additional) and maybe even dutil (I made one internally that does support native code using a common pattern online).

A couple of questions,


1.       Do you want me to set up a NuGet entity (and symbolsource.org entity for symbol packages, which get automatically published) for either WiX or FireGiant (whichever you prefer) and turn the reigns over to you to regenerate a key and add that to your build machine (i.e. taking the reins from me), or do you want to set that up? I was planning on adding a Publish task (much like the site repo's web.proj) so I'd like to test it at least - unless you want to do that and I'd just create a build task (which we follow a common pattern internally that works nice).

2.       Do you want the package namespace to match the assemblies for DTF but use something like WixToolset.Dutil, or use WixToolset (or whatever casing you want) as the root for all of them?

This work is pretty small rocks since I'm basically porting what I have internally with probably a few tweaks from tips and tricks I've developed since then.

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