-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Signed bootsrapper exe with custom BA does not start embedded MSI #1685
Comments
Hallo, i had currently same issue. I solved it in way, that described in https://wixtoolset.org/docs/tools/signing/ Link. Only one diffrence : your CustomBA is silent, i done it for my CustomBA as normal Burn Installer, not silent. Try it, if it solved your issues. |
Thank you @Torchok19081986. This is the only way...
|
You can use: var bundle_exe = bundle.Build("my_setup.exe");
Tasks.DigitalySignBootstrapperEngine(bundle_exe, ....) It does exactly whet https://wixtoolset.org/docs/tools/signing/ Link demonstrates. Though the implementation is extremely simple so so you can have your custom version of wixsharp/Source/src/WixSharp/CommonTasks.cs Lines 373 to 401 in 99ccab1
|
Hi,
Using WixSharp, we created an MSI package, which we embedded in a bootstrapper exe, together with a few internet assemblies, using CustomBA. (Using WIX4.0.3)
Using this bootstrapper exe, installation works fine!
However, if we sign the bootstrapper exe, the bootstrapper will start correctly, but the MSI will not start. The only way to start the MSI, is to make sure the MSI is copied to the same directory as the bootstrapper exe. This step is not needed if we did not sign the bootstrapper exe.
The exception we get in the install log is the following:
What am I missing in this process?
The text was updated successfully, but these errors were encountered: