[wix-devs] Signing build output
r.sean.hall at gmail.com
Fri Dec 14 12:40:47 PST 2018
I don't know, the prereqs section seems to be straightforward to me. The
WiX build system is smart. It will detect what have actually have installed
on your machine. It will skip building parts of the toolset that require
build tools that you don't have installed. If you install a Professional
level or higher of any recent Visual Studio than VS will install everything
The ideal load is whatever version of VS you already have installed,
preferably not the Community edition.
The page is geared towards getting a developer up and running on working on
the WiX Toolset on their local machine. I honestly have no interest in
figuring out to build a personal build pipeline for WiX.
There are only two things you need to worry about building.
OneTimeWixBuildInitialization is a one time time thing to get your machine
to trust the delay signed assemblies. wix.proj at the root of the repo is
the other (MSBuild will automatically build whatever project is in the
folder if there's only one, that's why the command is simple MSBuild).
That's it. The solutions are only for your convenience when editing code.
If you would like to contribute to that page, it is at
On Fri, Dec 14, 2018 at 1:50 PM Christopher Painter <chrpai at iswix.com>
> I'll admit most of my attempts were years ago so maybe this is in the
> past. But reading that page and your email causes more questions for me.
> If I created an build environment for building WiX, what is the ideal
> load? The prereqs section of that page is confusing to me.
> Ideally I'd like to create a build vm or docker image and publish a yaml
> pipeline or similiar and say this wi
> What would the ideal pipeline definition be? I see reference to the
> OneTimeWiXBuildInit but what about the other solutions? Which ones, which
> order and what platform and configuations?
> I'm a big fan of Azure DevOps and I'd love to be able to publish an all
> inclusive pipeline definition that says do this and it'll build.
> Then I would feel much more comfortable submitting patches. In the past I
> had a few fixes I felt good about but I couldn't contribute them because I
> couldn't be certain that I could build WiX all the way through and test to
> my satisfaction.
> *From:* wix-devs <wix-devs-bounces at lists.wixtoolset.org> on behalf of
> Sean Hall via wix-devs <wix-devs at lists.wixtoolset.org>
> *Sent:* Friday, December 14, 2018 1:28 PM
> *To:* WiX Toolset Developer Mailing List
> *Cc:* Sean Hall
> *Subject:* Re: [wix-devs] Signing build output
> The goal is to have http://wixtoolset.org/development/building-wix/ be
> Building WiX <http://wixtoolset.org/development/building-wix/>
> Building WiX Before your first build. To perform the one-time
> configuration the WiX build requires: Start an elevated 32-bit command
> prompt.; Change directories to the root of your clone repository.
> you need to start building. I know that before VS2017 I got it down to spin
> up a clean VM, install VS2015 with XP C++ support, and you could build the
> whole toolset. We rely on other people to come on here and ask for help
> when that page isn't enough.
> On Fri, Dec 14, 2018 at 6:29 AM Christopher Painter <chrpai at iswix.com>
> > One of the things that has prevented me from contributing to WiX over the
> > years is the difficulty for me as an outsider to figure out how to build
> > wix all the way through and test it on my own machine. It may seem easy
> > someone who's been doing it forever but when I spin up a clean VM with
> > visual studio, clone the repo (well many repos now) and try to build it
> > all the way through to bootstrappers and visual studio extensions it's
> > like mount everest.
> > Building should be easy IMO. The EULA is what says I have to contribute
> > it back.
> WiX Toolset Developer Mailing List provided by FireGiant
More information about the wix-devs