Why does such an error occur when using a custom operation with UI?

[shuaidaipeng]

Error: could not load custom action class WixSharp.CustomActions from assembly: WixSharpBA
System.BadImageFormatException: 未能加载文件或程序集“WixSharpBA”或它的某一个依赖项。试图加载格式不正确的程序。
文件名:“WixSharpBA”
在 System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
在 System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
在 System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
在 System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
在 System.AppDomain.Load(String assemblyString)
在 Microsoft.Deployment.WindowsInstaller.CustomActionProxy.GetCustomActionMethod(Session session, String assemblyName, String className, String methodName)

[oleg-shilo]

Please create your project from the Visual Studio WixSharp project template so you do not encounter problems with x64 vs x86 CPU architecture of your custom action assembly.

[shuaidaipeng]

请从 Visual Studio WixSharp 项目模板创建您的项目，这样您就不会遇到自定义操作程序集的 x64 与 x86 CPU 架构的问题。

When using templates or creating your own libraries, there will be prompts indicating that files have not been loaded when using CustomActions.

[shuaidaipeng]

[shuaidaipeng]

Calling custom action WixSharpBA!WixSharp.CustomActions.CreateWmsServiceIIS
Error: could not load custom action class WixSharp.CustomActions from assembly: WixSharpBA
System.BadImageFormatException: 未能加载文件或程序集“WixSharpBA”或它的某一个依赖项。试图加载格式不正确的程序。
文件名:“WixSharpBA”
在 System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
在 System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
在 System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
在 System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
在 System.AppDomain.Load(String assemblyString)
在 Microsoft.Deployment.WindowsInstaller.CustomActionProxy.GetCustomActionMethod(Session session, String assemblyName, String className, String methodName)

[shuaidaipeng]

I wonder if it would be possible to solve the above problem by introducing the installation package using ca in ba?

[oleg-shilo]

When using templates or creating your own libraries, there will be prompts indicating that files have not been loaded when using CustomActions.

When you build the setup from the template, no prompt is expected. The templates are tested, and you have full confidence that they do work.

When you start adding your own business logic to your new project, then of course, you can unintentionally introduce dependencies or a runtime error condition.

I suggest you start with something simple. Create your msi with CA and ensure it works as expected. My advise it s to use project events instead of raw CA. Much easier, friendlier and more reliable.

project.AfterInstall += e =>
{
    if (e.IsInstalling)
    { 
        var myApp = e.InstallDir.PathCombine("myapp.exe");
        var port = e.Session.Property("SITE_PORT");
        // you are elevated already
        // do your stuff
    }
};

As for BA, then you only need it if you indeed distribute multiple products/dependencies. Otherwise, stick to a single msi.

---

However, if you are experiencing some prompt with the raw template project, please sheri with me and I will check if the template is defective.

[shuaidaipeng]

The problem has been solved. The reason is that I directly used ca in the ba, which caused the problem.