[wix-devs] Burn micro repo(s)
rob at firegiant.com
Tue Jan 1 12:38:02 PST 2019
1. Bundle related binding is not complete. Compilation should be fine though.
2. If the error is not reported with a source file, MSBuild will fallback to using the targets file (wix.targets) as the source file. Obviously, we should try to minimize error messages that are not related to a source file. In this case, my guess is there is an exception being thrown all the way out.
From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of Sean Hall via wix-devs
Sent: Monday, December 31, 2018 10:13 PM
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] Burn micro repo(s)
I pushed the BalExtension repo. But I had to basically leave the wixlib empty because I guess compiling bundle related elements isn't currently working? The error I'm getting says it's from wix.targets, I thought Rob already fixed that? I'll probably come back and add tests once someone gets the bundle stuff compiling.
"C:\src\mynewwix4\Bal.wixext\Bal.wixext.sln" (default target) (1) -> "C:\src\mynewwix4\Bal.wixext\src\wixlib\bal.wixproj" (default target) (4) -> (CoreWixBuild target) ->
error : Cannot convert string 'Attached' to a 'number' field type.
error : Parameter name: value
On Sat, Dec 29, 2018 at 10:06 PM Sean Hall <r.sean.hall at gmail.com> wrote:
> I ended up going with BootstrapperCore. If someone comes up with a
> better name we can change it.
> I was able to login to AppVeyor but don't see any options to set it up
> for the new repository. I'll be pushing the burn repo and the balutil
> repo shortly, they'll reference the nuget package from there with the
> version of 4.0.1. We should be able to easily update the Nuget package
> reference with the script I sent in this pull request
> https://github.com/wixtoolset/Home/pull/1 if the first package has a
> different number.
> On Fri, Dec 28, 2018 at 1:15 PM Sean Hall <r.sean.hall at gmail.com> wrote:
>> So to recap, we have a repo with the Burn engine that we're going to
>> name burn. The Burn engine interacts with a user provided
>> BootstrapperApplication through the interfaces in this unnamed repository.
>> We can't call it anything with Burn because that's intended to be an
>> internal name. Burn is WiX's bootstrapper, but we don't want to call
>> it Bootstrapper either. Which probably means no one is ever going to
>> be able to guess what this Nuget package is going to be called.
>> What about splitting it into two repos - BootstrapperApplication and
>> On Fri, Dec 28, 2018 at 1:00 PM Rob Mensching via wix-devs <
>> wix-devs at lists.wixtoolset.org> wrote:
>>> We've generally avoided using the codename "Burn" in the public
>>> interfaces. That's why "Bootstrapper" is everywhere (despite the
>>> fact that I always typo that word).
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/
More information about the wix-devs