[wix-devs] WiX v4-preview.0 available, v4-preview.1 open for development

Thu May 27 06:43:26 PDT 2021

> There was never any mention that only a select few of the .nupkgs that are built would be uploaded to nuget.org.

These bullets defined the full extent of  v4-preview.0 every meeting about status of WiX v4:

WiX v4-preview.0
* wix.exe distributed as a dotnet tool
* Builds MSI, MSM, Bundles
* Extensions: Bal,Netfx,UI,Util
* v3 to v4 source code conversion working
* Later: MSBuild, MSP

> I thought all the .nupkgs would be uploaded and that the preview.0 goal was only about what would be promoted in blogs and documentation.

I can see how that would be one way to look at it. However, my goal was always to minimize the surface area of -preview.0 to those things that we knew we're definitely in and needed to build some reasonable set of MSIs/MSMs/Bundles.

Besides the mismatched assumptions about -preview.0, is there a problem that needs to be addressed?

-----Original Message-----
From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of Sean Hall via wix-devs
Sent: Wednesday, May 26, 2021 8:55 AM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Cc: Sean Hall <r.sean.hall at gmail.com>
Subject: Re: [wix-devs] WiX v4-preview.0 available, v4-preview.1 open for development

There was never any mention that only a select few of the .nupkgs that are built would be uploaded to nuget.org. I thought all the .nupkgs would be uploaded and that the preview.0 goal was only about what would be promoted in blogs and documentation.

On Wed, May 26, 2021 at 10:21 AM Rob Mensching <rob at firegiant.com> wrote:

> > This doesn't make sense to me
>
> I was very consistent that the goal of -preview.0 was to enable 
> developers to try converting their existing code and try to build some 
> MSIs/MSMs/Bundles. The minimal set of .wixext published limited the 
> breadth of projects that could be built; that was a tradeoff.
>
> > How will Heat and thmviewer be made available in preview.1?
>
> We have not decided yet.
>
>
> -----Original Message-----
> From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of 
> Sean Hall via wix-devs
> Sent: Wednesday, May 26, 2021 7:52 AM
> To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
> Cc: Sean Hall <r.sean.hall at gmail.com>
> Subject: Re: [wix-devs] WiX v4-preview.0 available, v4-preview.1 open 
> for development
>
> >  However, I did not want to expose the full WiX Toolset SDK surface
>
> This doesn't make sense to me. I can understand not wanting to release 
> the WixToolset.Sdk .nupkg but that has nothing to do with custom BAs.
>
> 3. I guess I should have made it clear that this (and 4) were forward 
> looking questions and not about how to get these in preview.0. How 
> will Heat and thmviewer be made available in preview.1?
>
> On Wed, May 26, 2021 at 9:36 AM Rob Mensching <rob at firegiant.com> wrote:
>
> > > so I think all of Burn including custom BAs was ready for 
> > > consumption in
> > wix4-preview.0.
> >
> > Yes, the goal was to get as many breaking changes into -preview.0 so 
> > there would be as few as possible in -preview.1. However, I did not 
> > want to expose the full WiX Toolset SDK surface in -preview.0 
> > because I wanted to see how the command-line tool and a minimal set 
> > of .wixexts
> went first.
> >
> > > 2. You never explained what the problem was with uploading the 
> > > extension
> > .nupkgs
> >
> > The "WixToolset." namespace was reserved on NuGet.org which 
> > prevented me from uploading the WixTooslet.Bal.wixext, 
> > WixToolset.Netfx.wixext, WixToolset.UI.wixext and 
> > WixToolset.Util.wixext. It took a few days but they eventually 
> > responded and assigned the "WixToolset." namespace to the wixtoolset org. I uploaded those .wixext right away.
> >
> > > 3. Yes, I noticed you skipped this one.
> >
> > It had the same answer. Those are not -preview.0 features.
> >
> > > 4. This wasn't really a preview.0 question. It seems the answer is 
> > > that
> > the artifacts.zip file will be included in a release in the wix4 
> > repo for all builds uploaded to nuget.org?
> >
> > That was the easiest option for -preview.0. We'll look at additional 
> > options going forward (such as publishing all the .nupkgs to a "WiX 
> > internal" feed maybe on AppVeyor, maybe on GitHub).
> >
> >
> > -----Original Message-----
> > From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of 
> > Sean Hall via wix-devs
> > Sent: Wednesday, May 26, 2021 7:07 AM
> > To: WiX Toolset Developer Mailing List 
> > <wix-devs at lists.wixtoolset.org>
> > Cc: Sean Hall <r.sean.hall at gmail.com>
> > Subject: Re: [wix-devs] WiX v4-preview.0 available, v4-preview.1 
> > open for development
> >
> > >  The goal of wix4-preview.0 was to be able to build most .wxs code
> >
> > I think there's a disconnect here. I spent most of my time in Burn, 
> > so I think all of Burn including custom BAs was ready for 
> > consumption in wix4-preview.0.
> >
> > 2. You never explained what the problem was with uploading the 
> > extension .nupkgs. It would probably be a good idea to upload these 
> > packages to find any issues that might happen.
> > 3. Yes, I noticed you skipped this one.
> > 4. This wasn't really a preview.0 question. It seems the answer is 
> > that the artifacts.zip file will be included in a release in the 
> > wix4 repo for all builds uploaded to nuget.org?
> >
> > On Tue, May 25, 2021 at 8:44 AM Rob Mensching via wix-devs < 
> > wix-devs at lists.wixtoolset.org> wrote:
> >
> > > Yes, wix4-preview.1 is when the full slate of .nupkgs is expected 
> > > to be published.
> > >
> > > The goal of wix4-preview.0 was to be able to build most .wxs code:
> > >
> > > 1. Command-line wix.exe convert/build experience for MSI/MSM/Bundle 2.
> > > The extensions: Bal, Netfx, UI, Util
> > >
> > > Custom BAs, extension development, etc. comes later.
> > >
> > >
> > > > 4. If someone wants to debug native code like Burn, how do they 
> > > > get the
> > > native .pdbs?
> > >
> > > Generally, I expected bugs reported against Burn in -preview.0 to 
> > > be tested and fixed against -preview.1. If we really need to debug
> > > Burn-preview.0 to track down a particularly mysterious issue, the 
> > > Burn .pdbs are in the -preview.0 artifacts.zip file.
> > >
> > >
> > > -----Original Message-----
> > > From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf 
> > > Of Bob Arnson via wix-devs
> > > Sent: Monday, May 24, 2021 9:13 PM
> > > To: WiX Toolset Developer Mailing List 
> > > <wix-devs at lists.wixtoolset.org>
> > > Cc: Bob Arnson <bob at firegiant.com>
> > > Subject: Re: [wix-devs] WiX v4-preview.0 available, v4-preview.1 
> > > open for development
> > >
> > > Wait for preview.1?
> > >
> > > -----Original Message-----
> > > From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf 
> > > Of Sean Hall via wix-devs
> > > Sent: Monday, 24 May, 2021 23:22
> > > To: WiX Toolset Developer Mailing List 
> > > <wix-devs at lists.wixtoolset.org>
> > > Cc: Sean Hall <r.sean.hall at gmail.com>
> > > Subject: Re: [wix-devs] WiX v4-preview.0 available, v4-preview.1 
> > > open for development
> > >
> > > What is the plan for the rest of the .nupkg?
> > >
> > > 1. If people want to try out the new extensibility model then 
> > > they'll need Data and Extensibility.
> > > 2. If people want to try out the new Burn extensibility model then 
> > > they'll need dutil, BootstrapperCore.Native, balutil, bextutil, 
> > > and
> > Mba.Core.
> > > 3. How are people supposed to get tools like Heat and thmviewer?
> > > 4. If someone wants to debug native code like Burn, how do they 
> > > get the native .pdbs?
> > >
> > > On Tue, May 18, 2021 at 2:22 AM Rob Mensching via wix-devs < 
> > > wix-devs at lists.wixtoolset.org> wrote:
> > >
> > > > WiX v4-preview.0 is now available. More important to this group,
> > > > v4-preview.1 is now open for development. To get started, fork 
> > > > the `wix4` repo and target the `develop` branch. If you have 
> > > > questions, let
> > > us discuss.
> > > >
> > > >
> > > > PS: There is an issue on nuget.org that is preventing me from 
> > > > uploading the preview.0 wixext's. I will get them uploaded as 
> > > > soon as NuGet team responds to my support inquiry.
>
>
____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/