custom-action

folder permissions: Full control granted to all users

寵の児 提交于 2019-12-06 03:47:01
问题 I'm working on an application which stores some files in the CommonApplicationData folder. My application has to modify these files. I managed to create a custom action to grant fullcontrol rights to my application folder in the CommonApplicationData folder. But this didn't solve the problem for non-admin users. When I log on as a user and try to modify one of these files, I get the "Access Denied" message. How can I solve this problem? Thanks. Here is the code which I used in the Custom

Executing Custom Actions immediately in WIX

£可爱£侵袭症+ 提交于 2019-12-06 01:36:52
Is there any way to execute a custom action in WIX as soon as the first dialog (welcome) appears? The requirement is to check prerequisites, and some of those require a custom action. The custom action could be executed as we click to the next dialog, but then the standard WIX prereqs are determined apart from our custom prereq. (The custom action we need is to check that IIS 6 Metabase Compatibility is turned on and a registry search does not work on x64 machines with a 32-bit installer) Add something like: <Custom Action="MyCustomAction" Before="FindRelatedProducts">1</Custom> Instead of

change installer properties in C# custom action

假如想象 提交于 2019-12-05 21:17:55
问题 How to change installer properties in my C# custom action? 回答1: To access a WiX property, such as those set with the Property element, use the Session object's indexer. Here is an example: [CustomAction] public static ActionResult CustomAction1(Session session) { string myProperty = session["MY_PROPERTY"]; return ActionResult.Success; } Setting properties is just as easy. You'll set the value by referencing the key with the name of your property. Here's an example: [CustomAction] public

How to execute multiple launch conditions on installer exit

混江龙づ霸主 提交于 2019-12-05 14:07:00
I've managed to get WIX to launch my application on exit, but not sure how to schedule two custom actions using the WixShellExecTarget property. One CA is to launch an app and the other is a web page based on a url from another CA. These are both launched if the appropriate checkboxes are checked. <!-- Custom action for executing app --> <Property Id="WixShellExecTarget" Value="[#Application.exe]" /> <CustomAction Id="LaunchApplication" BinaryKey="WixCA" DllEntry="WixShellExec" Impersonate="yes" /> <!-- Custom action for executing Webbrowser --> <Property Id="???" Value="[CONFIGWIZARDURL]" />

WiX - commit more than one Property to deferred Custom Action

≡放荡痞女 提交于 2019-12-05 03:38:20
I have a problem with my WiX installer in contact with deferred / immediate custom actions. Please excuse my english. I want to surrender some properties, entered by the user, to a deferred custom action. I know that I need a immediate custom action and "CustomActionData" to do that. I´ve implement it at this way. The binary: <Binary Id='myAction' SourceFile='.\TemplateGeneration.CA.dll'/> The immediate custom action: <CustomAction Id='Datenuebergabe' Property='DoSomething' Value='InstalllocVar=[INSTALLLOCATION]'/> The deferred custom action: <CustomAction Id='TemplateGenerationInstallKey'

Wix CustomAction update UI?

落爺英雄遲暮 提交于 2019-12-04 19:48:08
If I have a managed Wix Custom Action, is there anyway I can update a Control with the type of Text? I see that a progress bar can be updated by using the session.Message with InstallMessage.Progress , but I do not see a way for updating other UI. For a text control you can use a property wrapped in brackets: [SOMEPROP] Then in your CA you can say session["SOMEPROP"] = "somevalue". Note MSI is wonky about refreshing the UI so you'll pretty much have to transition from one dialog to another to get this to work. In other words, on the next button of the previous dialog call the CA and in the

Windows Installer custom action BEFORE any validation

萝らか妹 提交于 2019-12-04 17:08:18
I wrote a Windows Installer custom action based on the tutorial found here: http://www.codeproject.com/kb/install/msicustomaction.aspx My custom action is killing a background process of a given name which could still be opened by the user. The reason is that I don't want users to see the warning that a given EXE is running and must be closed so that setup can continue. This works fine when the MSI passes through the UI sequence as the action is created in "InstallUISequence" table like in the tutorial. However, when the MSI is used silently (right-click and select repair or uninstall), then

WiX. Run a custom action when a checkbox is checked

人走茶凉 提交于 2019-12-04 16:43:56
I have two files Product.wxc there i wrote <Property Id="CheckBoxProp"> and Custom Action <InstallExecuteSequence> <Custom Action="MyCustomAction" After="InstallInitialize"> CheckBoxProp=1 </Custom> </InstallExecuteSequence> In another file MyCheckBoxDlg.wxc I wrote UI dialog there I described checkbox <Control Type="CheckBox" Id="MyCheckBoxID" Width="125" Height="26" X="26" Y="124" Text="My text" Property="CheckBoxProp" CheckBoxValue="1" /> All publishs I wrote in another file where I have a DialogRef to MyCheckBoxDlg When I start my installation customaction doesn't see change of value

wix SetProperty After attribute won't take custom action Id

你说的曾经没有我的故事 提交于 2019-12-04 15:59:15
问题 After reading the page on SetProperty and looking at as many examples as I could find here and elsewhere, I'm still not able to get my SetProperty to work with After or Before set to one of my custom action IDs. The documentation seems very simple and straight forward on the subject (hah!), but I'm getting "Found an ActionRow with a non-existent After action: MyWonderfulCA" instead of happiness (which really is what I'm after : ) Here's a representation of what my code looks like:

Wix-Installer-How can I get setup.exe's current directory?

放肆的年华 提交于 2019-12-04 08:51:25
I'm using setup.exe and setupbld.exe (from %WixProramFolder%\bin)to make a bootstrapper for my installer. Everything is ok except: I want to get current directory of setup.exe but: When I use property "CURRENTDIRECTORY", I will get wrong value if I run command line in cmd.exe: "C:>"D:\setup.exe"". "CURRENTDIRECTORY" is "C:\" but "D:\" is true. When I use property "SOURCEDIR", setup.exe will extract setup.msi to "%Temp%{ProductID}\setup.msi" and "SOURCEDIR" is "%Temp%{ProductID}\" but expected is "D:\" Anybody can help me? It make me headache this time :-( Sorry about my English. I had this