custom-action

How to update appsettings.json from wix custom actions with the values passed as parameter during command line installation?

家住魔仙堡 提交于 2019-12-02 10:15:39
I’m currently working on a project where I am using Wix for the installer. My application is developed using .net core and having appsettings.json as a configuration file. I would like to update the values on the appsettings.json with the values which passed as a parameter during command-line installation For example, I am passing value 500 through parameter BUFFER.SIZE msiexec.exe /i c:\PathToMyMsi\MyMsi.msi BUFFER.SIZE="500" /L*vx c:\PathToMyLog.txt To achieve this, I have defined property and custom action in Product.wxs as follow <Property Id="BUFFER.SIZE" /> <Binary Id="GetParameters.CA"

Having an issue with WIX upgrade

▼魔方 西西 提交于 2019-12-02 08:09:24
问题 Having an issue with WIX installer upgrade. Previously we had 2 version of installers 1 for per-machine and another for per-user. Currently we have developed a dual mode MSI. The dual mode MSI upgrades the PerUser version (on PC 1) of previous installer when install for yourself option is selected but when install for all (on PC 2 ) is selected it install a new product Is it some wrong that we are doing or is have to set some properties. We are using WIX. Please help 回答1: If you had two

.NET managed dll custom actions in Installshield 2018

*爱你&永不变心* 提交于 2019-12-02 06:21:09
问题 I am using Installshield 2018 Express edition to make my setup and I wanted to include some custom actions coded in .NET, but I can't find the way to reference a custom action in .NET. I guess Installshield would have an option to refer to the assembly, class and public method to be invoked for the custom action but I can't find any option to do that. ¿Is there any way to achieve this? I'd prefer to use a dll instead of an exe and having to deal with the command line args, etc. 回答1: Express

How to read certain registry key from Wix managed bootstrapper or custom action?

前提是你 提交于 2019-12-02 05:37:51
I am having trouble reading this key from my managed bootstrapper (.NET 4.5.2), and my custom action (tried .NET 2.0 and 4.0). HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages I tried running the bootstrapper and msi using cmd as Administrator. My test environment is Windows 7 64-bit. I am using Wix 3.11 I made a test command line app and it was able to access this key. The testing code I used in the bootstrapper and custom action: static RegistryKey GetHKLMKey(string registryPath) { var hklm64 = RegistryKey.OpenBaseKey(RegistryHive.LocalMachine,

Having an issue with WIX upgrade

☆樱花仙子☆ 提交于 2019-12-02 04:43:28
Having an issue with WIX installer upgrade. Previously we had 2 version of installers 1 for per-machine and another for per-user. Currently we have developed a dual mode MSI. The dual mode MSI upgrades the PerUser version (on PC 1) of previous installer when install for yourself option is selected but when install for all (on PC 2 ) is selected it install a new product Is it some wrong that we are doing or is have to set some properties. We are using WIX. Please help If you had two setups before, it might be that you have two upgrade code and need to deal with both for the upgrade to work in

don't have any CustomActionAttribute in VS2010

▼魔方 西西 提交于 2019-12-02 04:20:39
问题 I am trying to write a custom actions class library for my WiX install package. I've read that I should use CustomActionAttribute to mark the methods that I am planning to call from install package. There is no Votive plugin for VS2010, so when I type [CustomAction] above my method name, VS2010 doesn't find it. So what should I do to write a custom action method? 回答1: There is Voitve support for Visual Studio 2010 in Wix 3.5 and up. With Votive you get a project template for creating managed

.NET managed dll custom actions in Installshield 2018

[亡魂溺海] 提交于 2019-12-02 00:16:19
I am using Installshield 2018 Express edition to make my setup and I wanted to include some custom actions coded in .NET, but I can't find the way to reference a custom action in .NET. I guess Installshield would have an option to refer to the assembly, class and public method to be invoked for the custom action but I can't find any option to do that. ¿Is there any way to achieve this? I'd prefer to use a dll instead of an exe and having to deal with the command line args, etc. Express Edition : I am not sure the Express edition of Installshield supports custom actions or Installscript (custom

Wix: Set semicolon to CustomActionData

有些话、适合烂在心里 提交于 2019-12-01 23:34:17
问题 I have a problem with setting data that contains semicolons to CustomActionData property. By default CustomActionData class uses semicolon as DataSeparator and it breaks my data, when it contains semicolons. Is there any way to put semicolons to CustomActionData except of replacing them by come keyword? 回答1: to pass a semicolon in your CustomActionData you should add one more semicolon. Example: CustomActionData="key1=value1;key2=value2.1;;value2.2;;value2.3" - this will pass key1=value1 and

Wix: Set semicolon to CustomActionData

拈花ヽ惹草 提交于 2019-12-01 20:29:08
I have a problem with setting data that contains semicolons to CustomActionData property. By default CustomActionData class uses semicolon as DataSeparator and it breaks my data, when it contains semicolons. Is there any way to put semicolons to CustomActionData except of replacing them by come keyword? to pass a semicolon in your CustomActionData you should add one more semicolon. Example: CustomActionData="key1=value1;key2=value2.1;;value2.2;;value2.3" - this will pass key1=value1 and key2=value2.1;value2.2;value2.3 If you don't know where the semicolons are then I guess you can create

How to run a Custom Action inside an MSI created in WiX with elevated privileges?

孤街浪徒 提交于 2019-12-01 19:08:41
问题 I have an installer that needs to access the registry and copy and remove files using custom actions. In Windows XP the installer works just fine, but in Vista and 7, the installer shows an error because it cannot access a folder, but if I run the installer as administrator everything works. So, I need the installer to be able to run the custom action as administrator even if the MSI wasnt run this way (need the installer to be run by regular users). I tried using an EXE at the beginning of