[wix-devs] Burn micro repo(s)

[Sean Hall]

Burn.Core?

On Fri, Dec 28, 2018 at 12:16 PM Rob Mensching <rob at firegiant.com> wrote:

> Naming is so hard. Especially when they are public names. However, many
> .nupkgs we create (my gut says 2: native and managed) they will show up on
> nuget.org.
>
>
>
> I’m not big on “ManagedBalUtil”. I’m also thinking we should maybe let
> “managed” be the main name and tack on “.Native” or something like that for
> the native code.
>
>
>
> Something like: WixToolset.Bootstrapper.nupkg and
> WixToolset.Bootstrapper.Native.nupkg.
>
>
>
> Really, the first .nupkg should match the root namespace for the code in
> BootstrapperCore.dll. What is that going to be?
>
>
>
> I’m also assuming that we can put all the headers in a single native
> .nupkg and devs will #include headers to get either the binary interfaces
> or the COM interfaces. =
>
>
>
>
>
> *From:* Sean Hall <r.sean.hall at gmail.com>
> *Sent:* Friday, December 28, 2018 10:00 AM
> *To:* Rob Mensching <rob at firegiant.com>
> *Cc:* WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
> *Subject:* Re: [wix-devs] Burn micro repo(s)
>
>
>
> Hmm. I thought there would have been 1 nuget package or 3 (binary
> interfaces, native COM interfaces, managed COM interfaces).
>
>
>
> I don't know about the name. Something like ManagedBalUtil?
>
>
>
> On Fri, Dec 28, 2018 at 11:45 AM Rob Mensching <rob at firegiant.com> wrote:
>
> The last two are correct. I'm not big on the first two. I think
> "Burn.Engine" could do well as "burn" (since it is native code like dutil,
> wcautil, balutil). The "Burn.Interfaces" repo should then be named after
> the .nupkg that would get published (minus the "WixToolset." prefix). So,
> thinking about the Burn interfaces .nupkg name:
>
> 1. WixToolset.BootstrapperCore.nupkg
> 2. WixToolset.Bootstrapper.nupkg
>
> I'm not thrilled about those names. What is the namespace in
> "BootstrapperCore.dll" (and thus its new name) going to be?
>
>
> -----Original Message-----
> From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of Sean
> Hall via wix-devs
> Sent: Friday, December 28, 2018 9:28 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] Burn micro repo(s)
>
> So what should the names be? The first thing that comes to mind for me is
> Burn.Interfaces, Burn.Engine, balutil, Bal.wixext.
>
> On Thu, Dec 20, 2018 at 11:02 AM Rob Mensching via wix-devs <
> wix-devs at lists.wixtoolset.org> wrote:
>
> > Groovy.
> >
> > -----Original Message-----
> > From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of
> > Sean Hall via wix-devs
> > Sent: Thursday, December 20, 2018 8:58 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] Burn micro repo(s)
> >
> > I think I'm good with your layout, with one little tweak that
> > IBoostrapperEngine.h and IBootstrapperApplication.h should be in the
> > Burn interface repo instead of staying in balutil with the rest of
> > balutil's headers. For the initial setup, I would just keep all of
> > BootstrapperCore as is in the Burn interface repo and then later we'll
> > need to create a new project in the BalExtension for the code we're
> > able to move out of BootstrapperCore.
> > ____________________________________________________________________
> > WiX Toolset Developer Mailing List provided by FireGiant
> > http://www.firegiant.com/
> >
> ____________________________________________________________________
> WiX Toolset Developer Mailing List provided by FireGiant
> http://www.firegiant.com/
>
>