New Post: NativeBootstrapper File Description
Unfortunately I cannot help you much. The nbsbuilder was built with VS2010. I don't even have it any more and upgrading to VS2015 didn't work smoothly. The upgrade also introduces a dependency on a...
View ArticleNew Post: always remove a previous version
This is what WiX MajorUpgrade.AllowSameVersionUpgrades and MajorUpgrade.AllowDowngrades attributes for. Did you tried them?
View ArticleNew Post: Func and ProgressTextAttribute for ManagedAction
It is a good idea. Will definitely do it in the next release. Though the ManagedUI events offer you even better (except 'progress text') support: project.Load += msi_Load; project.BeforeInstall +=...
View ArticleNew Post: Absolute path
Then you, The problem is caused by the VS project templates extension, which does not reflect latest changes (fix from this thread) in the WixSharp.UI.Forms.InstallDirDialog class of the NuGet package...
View ArticleNew Post: Odd Bootstrapper Behavior
As far as I understood your report the identical WiX source is generated in both cases and "output logs had our msi as default requested: Present" is a fragment from the MSI runtime log. Is this correct?
View ArticleNew Post: Absolute path
Ended up copying InstallDirDialog_Load from InstallDirDialog's dialog, now works. Thank you very much!
View ArticleNew Post: Odd Bootstrapper Behavior
I believe that the same WiX source is generated (I didn't find any obvious difference by visual inspection), and the differing default requested settings did come from the MSI runtime log.
View ArticleNew Post: How to check if OS is 32 or 64 bit?
How can I check if the OS is 32 or 64 bit? I'm using this to run a batch script to install the proper drivers. Thanks!
View ArticleNew Post: Odd Bootstrapper Behavior
OK. Then I assume what you have in the log a section similar to this (from Wix# samples):Detected package: NetFx40Web, state: Present, cached: Complete Detected package: CRT.msi, state: Absent, cached:...
View ArticleNew Post: How to check if OS is 32 or 64 bit?
The limitation of MSI as a deployment technology is that it cannot be built as "neutral". You need build your MSI as x64 or x86 installation package (samples are available). Though you can build your...
View ArticleNew Post: Thanks for Wix#
Easily converted my problematic WiX files over to WiX# in a couple of hours. Worked first time. Great work Oleg_s. Thanks. Glenn.
View ArticleNew Post: Absolute path
Yes, it's another way of solving the problem. BTW I have just updated the VS extension with the latest sources from WixSharp codebase and now you (if you update the extension) the Custom UI template...
View ArticleNew Post: Change in how QtCmdLineAction works?
A follow up on this, since a few of our customers have been complaining on:In the scenario of InstalledFileAction, this displays a command window briefly, which can't be hidden (not even with the /q...
View ArticleNew Post: Func and ProgressTextAttribute for ManagedAction
The latest codebase (commit:16cde819ed99) now contains the constructors that take delegates instead of string literals as method name:var project = new Project("CustomActionTest", new...
View ArticleNew Post: Odd Bootstrapper Behavior
I made the change you suggested, but the output from the log simply changed to Planned package: *********, state: Absent, default requested: Absent, ba requested: Absent, execute: None, rollback: None,...
View ArticleNew Post: How to check if OS is 32 or 64 bit?
Okay, that's good information about an MSI's limitation, and because of that it makes sense that there's no function to facilitate getting that information. However, in my case the program installed is...
View ArticleNew Post: How to check if OS is 32 or 64 bit?
And if your bootstrapper is .NET 4 (most likely it is) you can use even more direct approach:if (!Environment.Is64BitOperatingSystem) { //do x86 stuff }
View ArticleNew Post: Odd Bootstrapper Behavior
I think the only sensible thing to do now is to debug your DetectPackageComplete handler. Just use the BA app from WixBootstrapper_NoUI sample but with your MSIs and after you enter the routine with...
View Article