wixsharp

Wix#: how to bind custom UI decision to actual installation steps?

☆樱花仙子☆ 提交于 2021-01-28 04:49:01
问题 We have two installation modes: service and app. Using Wix#, I couldn't find a way to present this simple two-radio buttons dialog to the user: Choose your installation: (*) App [default] ( ) Service And then choose which files (and action) to deploy/perform accordingly. How do we even bind the user's decision with the actual operation? Edit: I discovered how to do that, eventually, but still can't make the GUI selection affect the deployed files (although the bound property do change). Here

Install two mutually-exclusive files with the same name to the same directory

生来就可爱ヽ(ⅴ<●) 提交于 2020-01-25 00:19:04
问题 My program deploys with a configuration option that I've chosen to expose as a feature. This option can be one of two values. Each configuration changes a set of settings files. They have different input file names (for the sake of example, let's call it option1-config20-lv80.xml), but should be installed to the configuration directory as config20-lv80.xml. Each option has a prefix that should be stripped like that, which also means only one of these options can be selected for install at a

Property seems to change per user's selection, but conditioned files are not being deployed

时光怂恿深爱的人放手 提交于 2020-01-16 09:02:12
问题 In our installer, we want to deploy one of two files, according to a decision that the user should make during the installation . I am able to change the property during run-time, via a WixForm using radio buttons, and even to confirm that the bound property indeed changes (using a CustomAction that shows a MessageBox , checking the expressions session.EvaluateCondition($"TYPE_OF_PKG=\"ABC\"") and session.EvaluateCondition($"TYPE_OF_PKG=\"XYZ\"") ). However, it doesn't seem to affect the

Why installer runs after click on shortcut?

别来无恙 提交于 2019-12-10 23:09:03
问题 I created a simple bootstrapper for my application using WixSharp. namespace TestBootstrapper { class Program { static void Main() { var package = new MsiPackage("../testmsi.msi") { DisplayInternalUI = true, Id = "MyId", Compressed = true, Visible = true }; var bootstrapper = new Bundle("MyTestInstaller", package) { Version = new Version("1.0.0.0"), UpgradeCode = new Guid("1FCC927B-7BB0-4FB0-B81E-2D87012E470B"), PreserveTempFiles = true, DisableModify = "yes", DisableRemove = true };

In Wix#, how to avoid creating a physical folder on the target system, when deploying only registry entries?

馋奶兔 提交于 2019-11-28 12:43:23
问题 I have several related Windows registry entries that I want packaged inside an MSI, so that 1) there is an uninstall process, and 2) The fact that these registry entries have been applied to a given computer is documented by an Add/Remove Programs entry. The problem is that I can get Wix# to do this just fine, but I can only get the MSI to build if all the registry entries are inside a "Dir" block, and that winds up actually creating a physical folder, which I don't want, on the target system

WIxsharp debug custom action in console

|▌冷眼眸甩不掉的悲伤 提交于 2019-11-26 06:50:27
问题 I have a custom action project which compiles to a .dll, I want to be able to step through my custom actions, i know the package can be changed to wixsharp.bin but this dosn\'t seen very practical. Regardless, I still tried this method but it didn\'t hit my breakpoints. Wix uses: System.Diagnostics.Debugger.Launch(); which launches the action in debug, this dosn\'t seem to work for wixsharp but it\'s expected result is what i am trying to achieve. I have seen that debug.assert can be used for