Hi Oleg,
Yes, I can confirm the file is present. I've been working on this test app for about a week and it has been building consistently with the license displaying so I'm 99% sure this occurred only in .26. Test App.msi has been working well and continues to do so providing I remove that line.
If i can just get back to my original issue (which unfortunately hasn't been resolved with .26), I've found the following happens. If I set it to SilentBootstrapperApplication nothing happens - neither the bootstrap wizard or the MSI's wizard with "DisplayInternalUI = true" shows on screen. However, if I leave the application property blank it loads the default bootstrap wizard, installs framework 4.0 (this is good!) and then displays the MSI's installer. This isn't ideal for a number of reasons:
1) The bootstrapper install has an option to select a install path which isn't carried over to the MSI installers path so it's not user friendly.
2) My Setup MSI is designed to remember the install path on re-installation but with bootstrapper doesn't see this.
3) I'm running an elevated managed action I don't think it will run unless my MSI's wizard is visible.
4) The bootstrapper is now the thing listed in installed programs and therefore doesn't have any of the controlpanelinfo etc that I set on my setup.
Have I bitten off more than I can chew? All I essentially want is for my setup program to visibly run and be installed in control panel, and have framework prerequisites be checked and installed if required. I assumed it was recommended to use bootstrapper to do that. Unfortunately I can't get the user experience to something I'm happy with. Apologies if this is moving more towards a WixToolset issue that a WixSharp issue.
Yes, I can confirm the file is present. I've been working on this test app for about a week and it has been building consistently with the license displaying so I'm 99% sure this occurred only in .26. Test App.msi has been working well and continues to do so providing I remove that line.
If i can just get back to my original issue (which unfortunately hasn't been resolved with .26), I've found the following happens. If I set it to SilentBootstrapperApplication nothing happens - neither the bootstrap wizard or the MSI's wizard with "DisplayInternalUI = true" shows on screen. However, if I leave the application property blank it loads the default bootstrap wizard, installs framework 4.0 (this is good!) and then displays the MSI's installer. This isn't ideal for a number of reasons:
1) The bootstrapper install has an option to select a install path which isn't carried over to the MSI installers path so it's not user friendly.
2) My Setup MSI is designed to remember the install path on re-installation but with bootstrapper doesn't see this.
3) I'm running an elevated managed action I don't think it will run unless my MSI's wizard is visible.
4) The bootstrapper is now the thing listed in installed programs and therefore doesn't have any of the controlpanelinfo etc that I set on my setup.
Have I bitten off more than I can chew? All I essentially want is for my setup program to visibly run and be installed in control panel, and have framework prerequisites be checked and installed if required. I assumed it was recommended to use bootstrapper to do that. Unfortunately I can't get the user experience to something I'm happy with. Apologies if this is moving more towards a WixToolset issue that a WixSharp issue.