[wix-devs] Votive 2017 - Votive via VS Marketplace

Christopher Painter chrpai at iswix.com
Fri Feb 17 08:39:02 PST 2017 

Just to be clear...  someone already on VS2015 with WiX 3.10.3  will upgrade to 3.11 and won't have votive anymore?  

Then there is the issue of explaining to my open source users what they need.

I have the have the feeling I'm going to be making my own bootstrapper to glue this all back together like the way it was.

-----Original Message-----
From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On Behalf Of Sean Hall
Sent: Friday, February 17, 2017 10:31 AM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Subject: Re: [wix-devs] Votive 2017 - Votive via VS Marketplace

You can download the VSIX package from the marketplace and register it in
VS2017 in the same way that you register your other extensions.

On Fri, Feb 17, 2017 at 10:17 AM, Christopher Painter <chrpai at iswix.com>
wrote:

> Oh and prefix that list with  0) Visual Studio 2015  (how could I 
> forget that! ;) )
>
> -----Original Message-----
> From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On 
> Behalf Of Christopher Painter
> Sent: Friday, February 17, 2017 10:17 AM
> To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
> Subject: Re: [wix-devs] Votive 2017 - Votive via VS Marketplace
>
> We make WiX available to developers across the enterprise using SCCM 
> Software Center and through a developer (windows f12 pxe) build task 
> sequence.  With this we chain together:
>
> 1) WiX 3.10.3
> 2) IsWiX 4.0.17001.1
> 3) An Internal  Enterprise WiX Templates MSI
>
> This works on VS2008-2015.  With the move to WiX 3.11.x.  They will 
> have an additional step to go into VS marketplace and manually request 
> the Votive Extension  otherwise their projects won't load.  I'm going 
> to get slack for the "suboptimal" user experience this causes.
>
> Unless you are telling me a way to automate this?   I'm guessing the
> answer is no otherwise WiX's own burn bootstrapper would have, right?  
> Am I missing something?
>
> So either I accept this or I say  our enterprise standard is VS2015 /
> 3.10.3 because it's good enough and doesn't have this issue.  (We keep 
> our WiX projects in a separate Installer.sln and the application code 
> in it's own Application.sln so they can move forward to 2017 without 
> issue. This isn't the first time a new version of VS has caused me 
> pain so I plan
> ahead.)
>
> -----Original Message-----
> From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On 
> Behalf Of Sean Hall
> Sent: Friday, February 17, 2017 8:15 AM
> To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
> Subject: Re: [wix-devs] Votive 2017 - Votive via VS Marketplace
>
> When v3.11 ships, there will be an extension in the marketplace for 
> VS2010, VS2012, VS2013, VS2015, and VS2017. What's going to force you 
> to stay on v3.10.3?
>
> On Fri, Feb 17, 2017 at 7:39 AM, Christopher Painter 
> <chrpai at iswix.com>
> wrote:
>
> > 3.  So now instead of being tempted to just stay on VS2015  I'll have to
> > be tempted to stay on VS2015 and WiX 3.10.3?    I know you're in a rock
> and
> > a hard place.. I just don't like it one bit.  Thanks DevDiv.
> >
> > -----Original Message-----
> > From: wix-devs [mailto:wix-devs-bounces at lists.wixtoolset.org] On 
> > Behalf Of Blair Murri
> > Sent: Friday, February 17, 2017 6:49 AM
> > To: WiX Toolset Developer Mailing List 
> > <wix-devs at lists.wixtoolset.org>
> > Subject: Re: [wix-devs] Votive 2017 - Votive via VS Marketplace
> >
> > 1. Fine by me. My lack of creative "namology" isn't coming up with 
> > anything better, either, and it's not a bad name by any stretch.
> > 2. My preference would be v4 only and leave v3 out of it, but if v3 
> > is intended to be included then it's probably better to do it in 3.11.
> > 3. I generally prefer shorter names at that level, but consistency 
> > is probably better, so I'll concur.
> > 4. I'll vote yes.
> >
> > Blair Murri
> >
> > Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for 
> > Windows 10
> >
> > From: Rob Mensching<mailto:rob at firegiant.com>
> > Sent: Tuesday, February 14, 2017 10:13 PM
> > To: WiX Toolset Developer Mailing List<mailto:wix-devs at lists.
> > wixtoolset.org>
> > Subject: [wix-devs] Votive 2017 - Votive via VS Marketplace
> >
> > Happy Valentine's Day!
> >
> > At today's online meeting we discussed the Votive for Visual Studio
> > 2017 implementation proposed by FireGiant (WIP: 
> > http://wixtoolset.org/
> > development/wips/5492-votive-via-vs-marketplace/):
> > https://youtu.be/cGrn_PZl7q4?t=21m30s
> >
> > As mentioned there were a few items to raise here for discussion and 
> > without further ado:
> >
> > 1. What is the name? "WiX Toolset Visual Studio YYYY Extension" was 
> > the best name we've had thus far that minimizes confusion with WiX 
> > Extensions but still calls out that this is only Votive (the VS 
> > Extension), not the full build tools. Other better name suggestions 
> > are
> welcome.
> >
> > Proposal: WiX Toolset Visual Studio YYYY Extension  (where YYYY is 
> > 2010, 2012, 2013, 2015)
> >
> >
> > 2. When to remove Votive 2010-2015 from the bundles? Either we do it 
> > in WiX v3.11 or later (duh). The general consensus has been to do it 
> > now, as part of WiX v3.11 so the Votive acquisition experience is 
> > consistent. It is a breaking change from the user experience point 
> > of view but the changes introduced by Visual Studio 2017 seems like 
> > a the best time to introduce the Votive changes.
> >
> > Proposal: v3.11
> >
> >
> > 3. What should be the name of the repository be? Extracting the 
> > Votive repository provides a lot of value and is the perfect place 
> > to start the Repository Reorganization
> > (http://wixtoolset.org/development/wips/5489-
> > repository-reorganization/). The only real question is what to name it.
> > The root namespace for all WiX code is now "WixToolset" so the 
> > thinking is to name repositories the same as the next part of the 
> > code namespace. In this case Votive uses the namespace 
> > "WixToolset.VisualStudioExtension" so the proposed repository name 
> > would be "VisualStudioExtension". You might wonder why the namespace 
> > for Votive isn't "WixToolset.Votive". It could be but that name 
> > actually
> clashes with some of the classes internally.
> > "VisualStudioExtension" avoids any internal code confusion. Of 
> > course, we could still call the repository "Votive" if we wanted.
> >
> > Proposal: VisualStudioExtension (aka: https://github.com/wixtoolset/ 
> > VisualStudioExtension/).
> >
> >
> > 4. What should the version be? Currently Votive is versioned with 
> > the toolset. Now that it will be able to be independent from WiX 
> > Toolset version, what number should we use? I've proposed that we start with "v1"
> > since it is a clean break and all other close version numbers (v3, 
> > v4,
> > v5) have meaning in WiX and v10 just feels random. But open to other
> ideas.
> > Reminder, this is the internal versioning of Votive. It has nothing 
> > to do with what VS versions are supported.
> >
> > Proposal: v1.0
> >
> >
> > I'm very interested to see if anyone has some better ideas or sees 
> > ship stoppers in the proposals that we've not considered yet. We're 
> > pretty excited to be on track to release a WiX v3.11 Beta/RC with 
> > VS2017
> RTM.
> > Closing these open issues is the next step towards that RC.
> >
> > ____________________________________________________________________
> > WiX Toolset Developer Mailing List provided by FireGiant 
> > http://www.firegiant.com/
> >
> > ____________________________________________________________________
> > WiX Toolset Developer Mailing List provided by FireGiant 
> > http://www.firegiant.com/ 
> > ____________________________________________________________________
> > WiX Toolset Developer Mailing List provided by FireGiant 
> > http://www.firegiant.com/
> >
> ____________________________________________________________________
> WiX Toolset Developer Mailing List provided by FireGiant 
> http://www.firegiant.com/ ______________________________ 
> ______________________________________
> WiX Toolset Developer Mailing List provided by FireGiant 
> http://www.firegiant.com/ 
> ____________________________________________________________________
> WiX Toolset Developer Mailing List provided by FireGiant 
> http://www.firegiant.com/
>
____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/

More information about the wix-devs mailing list