Getting the Wix4 burn bootstrappingapplication runnable

[woscostametaxa]

After converting my WiX 3.11 burn bootstrapping application to Wix4 it seems like its in the final stretches of getting it runnable.

I try to do so with .net 4.7.2.

But with those last few changes I feel a tad like a fish out of water: my Application had a BootstrapperCore.config, which I renamed to WixToolset.Mba.Host.config and copypastad the following content (mainly to get the correct configSections which changed from what I have gathered so far:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <configSections>
    <sectionGroup name="wix.bootstrapper" type="WixToolset.Mba.Host.BootstrapperSectionGroup, WixToolset.Mba.Host">
      <section name="host" type="WixToolset.Mba.Host.HostSection, WixToolset.Mba.Host" />
    </sectionGroup>
  </configSections>
  <startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0" />
    <supportedRuntime version="v2.0.50727" />
  </startup>
  <wix.bootstrapper>
    <host assemblyName="ManagedBootstrappingApplication">
      <!--<supportedFramework version="v4\Full" />-->
    </host>
  </wix.bootstrapper>
</configuration>

The CustomBootstrapper.cs has the following parts:

namespace ManagedBootstrappingApplication.Bootstrapper
{
  public class CustomBootstrapper : BootstrapperApplication
 ...
    public CustomBootstrapper(IEngine engine, IBootstrapperCommand command) : base(engine)
    {
      this.Command = command;
    }

I also (for the 3.11) had an AssemblyInfo.cs:

using System.Reflection;
using System.Runtime.CompilerServices;
using System.Runtime.InteropServices;
using ManagedBootstrappingApplication.Bootstrapper;
using Microsoft.Tools.WindowsInstallerXml.Bootstrapper;

// General Information about an assembly is controlled through the following 
// set of attributes. Change these attribute values to modify the information
// associated with an assembly.
[assembly: AssemblyTitle("ManagedBootstrappingApplication")]
[assembly: AssemblyDescription("")]
[assembly: AssemblyConfiguration("")]
[assembly: AssemblyCompany("")]
[assembly: AssemblyProduct("ManagedBootstrappingApplication")]
[assembly: AssemblyCopyright("Copyright ©  2022")]
[assembly: AssemblyTrademark("")]
[assembly: AssemblyCulture("")]

// Setting ComVisible to false makes the types in this assembly not visible 
// to COM components.  If you need to access a type in this assembly from 
// COM, set the ComVisible attribute to true on that type.
[assembly: ComVisible(false)]

// The following GUID is for the ID of the typelib if this project is exposed to COM
[assembly: Guid("MY-GUID-HERE")]

// Version information for an assembly consists of the following four values:
//
//      Major Version
//      Minor Version 
//      Build Number
//      Revision
//
// You can specify all the values or you can default the Build and Revision Numbers 
// by using the '*' as shown below:
// [assembly: AssemblyVersion("1.0.*")]
[assembly: AssemblyVersion("1.0.0.0")]
[assembly: AssemblyFileVersion("1.0.0.0")]
[assembly: BootstrapperApplication(typeof(CustomBootstrapper))]

But with the change of the Constructor when I change that to this:

using System.Reflection;
using System.Runtime.InteropServices;
using ManagedBootstrappingApplication.Bootstrapper;
using WixToolset.Mba.Core;

// General Information about an assembly is controlled through the following 
// set of attributes. Change these attribute values to modify the information
// associated with an assembly.
[assembly: AssemblyTitle("ManagedBootstrappingApplication")]
[assembly: AssemblyDescription("")]
[assembly: AssemblyConfiguration("")]
[assembly: AssemblyCompany("")]
[assembly: AssemblyProduct("ManagedBootstrappingApplication")]
[assembly: AssemblyCopyright("Copyright ©  2022")]
[assembly: AssemblyTrademark("")]
[assembly: AssemblyCulture("")]

// Setting ComVisible to false makes the types in this assembly not visible 
// to COM components.  If you need to access a type in this assembly from 
// COM, set the ComVisible attribute to true on that type.
[assembly: ComVisible(false)]

// The following GUID is for the ID of the typelib if this project is exposed to COM
[assembly: Guid("MY-GUID-HERE")]

// Version information for an assembly consists of the following four values:
//
//      Major Version
//      Minor Version 
//      Build Number
//      Revision
//
// You can specify all the values or you can default the Build and Revision Numbers 
// by using the '*' as shown below:
// [assembly: AssemblyVersion("1.0.*")]
[assembly: AssemblyVersion("1.0.0.0")]
[assembly: AssemblyFileVersion("1.0.0.0")]
[assembly: BootstrapperApplication(typeof(CustomBootstrapper))]

The last line gives me the error:

 CS0653: Cannot applly attribute class 'BootstrapperApplication' because it is abstract
 Cannot access protected constructor 'BootstrapperApplication(IEngine)' here

and

Attribute constructor parameter 'engine' has type 'WixToolset.Mba.Core.IEngine', which is not a valid attribute parameter type.

If I remove that line the Bootstrapper can't be loaded of course (but at least built correctly) - but I havent seen a AssemblyInfo.cs on the old [WixBa](https://github.com/wixtoolset/wix4/tree/b500f7ae7113039c878555ec622d551854f891e2/src/test/burn/WixToolset.WixBA)

The excerpts of the Bundle.wxs:
```xml
    <BootstrapperApplication>
      <Payload SourceFile="D:\remote_wix4\PackageData\Build\Pipeline\Resources\bin\WixToolset.Mba.Core.dll" />
      <Payload SourceFile="D:\remote_wix4\PackageData\Build\Pipeline\Resources\bin\WixToolset.Mba.Core.xml" />
      <Payload SourceFile="D:\remote_wix4\PackageData\Build\Pipeline\Resources\bin\WixToolset.Mba.Host.config" />
      <Payload SourceFile="D:\remote_wix4\PackageData\Build\Pipeline\Resources\bin\ManagedBootstrappingApplication.dll" />
      <Payload .../>
      <!--there are several more dlls but that should be sufficient for this purpose I hope -->

      <bal:WixManagedBootstrapperApplicationHost />
    </BootstrapperApplication>

Can I just remove the AssemblyInfo.cs?
Or do I need to add a different constructor just for the AssemblyInfo?

I haven't found a lot of info in this regard - probably it is not a lot that needs to change but to be honest I am kinda stumped at the moment.

[rseanhall]

Assembly level attributes are not required to be in AssemblyInfo.cs. You are looking for WixBAFactory.cs.

[rseanhall]

Why would you think that an x86 DLL is ever going to work in an x64 process?

[barnson]

WiX v4 is the first to support 64-bit bundle processes.

[TheOpenDevProject]

I just provided my solution on my discussion thread after MUCH fighting.

https://github.com/orgs/wixtoolset/discussions/7276#discussioncomment-5324906

Don't know if this will help you since its not a custom BA but it got .NET installed for me the way I wanted.

[woscostametaxa]

I looked in the packages\WixToolset.Mba.Core.4.0.0-rc.3\lib\net20\WixToolset.Mba.Core.dll -> that one is i686
packages\WixToolset.Mba.Core.4.0.0-rc.3\lib\netstandard2.0\WixToolset.Mba.Core.dll -> i686 - do i need a different nupkg? where can I obtain the x64 dlls?

The runtimes dir has the arm64 x64 and x86 mbanative.dll, I do not know where WixToolset.Mba.Core.dll in 64bit would come from if not that package?

[rseanhall]

I was referring to this: If I add the mbanative.dll with x64 the dependency walker does not find it, so i used the x86 one..

WixToolset.Mba.Core.dll is a managed dll. It is compiled as AnyCPU so there is only one version.