SilentBootstrapperApplication #1203
Comments
|
Build WixBootstrapper_NoUI sample and the same error: The log here: |
|
You can pass it as a dependency param in the bootstrapper.Application = new ManagedBootstrapperApplication("%this%", "BootstrapperCore.config"); Or alternatively, set the default content of the config file to be generated: ManagedBootstrapperApplication.DefaultBootstrapperCoreConfigContent = "<custom BootstrapperCore.config XML content>"; |
|
Thank you Oleg.
I will try this today. However, when I use %this%, my app which is exe is
also being copied to the output folder, along wxs file, config file and
generated build executable. Is this normal?
Where should I keep the bootstrappercoreconfig file? I have that in my
project root folder as content and copy to output folder. Hope that's
correct?
Regards,
Ishtiyaq
…On Wed, Sep 14, 2022, 6:27 PM Oleg Shilo ***@***.***> wrote:
You can pass it as a dependency param in the
ManagedBootstrapperApplication constructor
bootstrapper.Application = new ManagedBootstrapperApplication("%this%", "BootstrapperCore.config");
Or alternatively, set the default content of the config file to be
generated:
ManagedBootstrapperApplication.DefaultBootstrapperCoreConfigContent = "<custom BootstrapperCore.config XML content>";
—
Reply to this email directly, view it on GitHub
<#1203 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABAH2REVQAOLLIG5GCJV7DTV6HODXANCNFSM6AAAAAAQIXMNIA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Yes it is. Your exe is in fact an msi/buutstrapper builder. so it should be there so it can be executed from the right location soo it can find all the files required for your msi/bundle. In your very scenario it also needs to embed itself in the bundle as your exe contains the implementation of the silent BA. That's why all these files are in the output folder.
entirely up to you. The |
|
I get it now, thank you! Especially bundling the exe with bundle.
Sorry, hopefully last question, I'm getting the same error when I build and
run your Bootstrapper_NoUI sample, your comments?
Regards,
Ishtiyaq
…On Wed, Sep 14, 2022, 6:55 PM Oleg Shilo ***@***.***> wrote:
Is this normal?
Yes it is. Your exe is in fact an msi/buutstrapper builder. so it should
be there so it can be executed from the right location soo it can find all
the files required for your msi/bundle. In your very scenario it also needs
to embed itself in the bundle as your exe contains the implementation of
the silent BA. That's why all these files are in the output folder.
Where should I keep the bootstrappercoreconfig file?
entirely up to you. The ManagedBootstrapperApplication constructor param
in simply a valid path to the config file.
—
Reply to this email directly, view it on GitHub
<#1203 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABAH2RE5ALWEV4ZDKLS77UTV6HRO7ANCNFSM6AAAAAAQIXMNIA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
My apologies. I overlooked the very problem you were asking about. After testing I found that the sample code was accidentally broken. Thus even though WixSharp functionality is OK you could not possibly get it working if you use the code sample. It is fixed now. // was
DetectPackageComplete += (s, e) =>
{
//Presence or absence of MyProductPackageId product will be a deciding factor
//for initializing BA in Install, Uninstall or Modify mode.
if (e.PackageId == "")
{
switch (e.State)
...
// should be
DetectPackageComplete += (s, e) =>
{
//Presence or absence of MyProductPackageId product will be a deciding factor
//for initializing BA in Install, Uninstall or Modify mode.
if (e.PackageId == "MyProductPackageId")
{
switch (e.State)Thus the installation was never scheduled. |
|
Thank you so much. You have developed this library and you have such a down
to earth and humble attitude, kudos and may God bless you.
I will follow the sample and build my app around it.
Thank you once again and much appreciated.
Regards,
Ishtiyaq
…On Sun, Sep 18, 2022, 1:15 PM Oleg Shilo ***@***.***> wrote:
My apologies. I overlooked the very problem you were asking about.
After testing I found that the sample code was accidentally broken. Thus
even though WixSharp functionality is OK you could not possibly get it
working if you use the code sample. It is fixed now.
// was
DetectPackageComplete += (s, e) =>
{
//Presence or absence of MyProductPackageId product will be a deciding factor
//for initializing BA in Install, Uninstall or Modify mode.
if (e.PackageId == "")
{
switch (e.State)
...
// should be
DetectPackageComplete += (s, e) =>
{
//Presence or absence of MyProductPackageId product will be a deciding factor
//for initializing BA in Install, Uninstall or Modify mode.
if (e.PackageId == "MyProductPackageId")
{
switch (e.State)
Thus the installation was never scheduled.
—
Reply to this email directly, view it on GitHub
<#1203 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABAH2RDKIGUGQFO333QTUMTV63MTDANCNFSM6AAAAAAQIXMNIA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Thank you mate :) |
- Issue #1244: The directory Id generated can be too long - Issue #1223: Non LegacyDummyDirAlgorithm creates C:\ProgramFilesFolder empty folder - Issue #1220: ElevatedManagedAction issue - Feature #1204: Feature - RegisterCom class to ease the registration of COM files - Issue #1203: SilentBootstrapperApplication - Issue #182 (extended solution): RegistrySearch has "Win64=no" when building x64 installers - Added Self-executable_Msi sample - Added WixBootstrapper_EmbeddedUI to demonstrate how to show managed UI if the bundled MSI - Added sample for customization of the stock Burn UI. Triggered by #1219 - Added sample for "Issue #1218: Dynamic custom UI sequence" - Resurrected setting user input from BA UI and passing it to the msi. RegistrySearch input is also retained. - Added validation for `Issue #1075: [FEAT] Add error if LaunchApplicationFromExitDialog using in common Project` error. - Fixed problem with RegKey being placed in the x86 root XML dir for the x64 project
Hi Oleg,
This is more of a help request. My app was working fine but from today facing the issues mentioned in issue# 435.
I'm using the following line to create a silent bundle
bootstrapper.Application = new SilentBootstrapperApplication();
Where do I specify the BootStrapper. core. Config file?
How do I add to my project? I dont use new Managed BA to pass it as parameter?
I can't follow the solution given by Zeb Ur Rehamn to make a custom SilentBA
Can someone help please.
The text was updated successfully, but these errors were encountered: