[WiX-users] creating a 64b CustomAction
I see that the C# custom action I created references Microsoft.Dwployment.WindowsInstaller. Is there a 64b version of this? Or more generally, how do I make a 64b custom action dll? A -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] creating a 64b CustomAction
I set the Platform target to Any CPU and the problem went away. A On Fri, Aug 13, 2010 at 2:02 PM, Andrew Hammond andrew.george.hamm...@gmail.com wrote: I see that the C# custom action I created references Microsoft.Dwployment.WindowsInstaller. Is there a 64b version of this? Or more generally, how do I make a 64b custom action dll? A -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] setting INSTALLDIR using a CustomAction
I have the following CustomAction and would like to it to set the INSTALLDIR property used in the WXS that calls it. I seem to be trying to set the property incorrectly. session[INSTALLDIR] = Some Location What is the correct way to set properties from within a CustomAction? A -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] setting INSTALLDIR using a CustomAction
Ok, that works for setting INSTALLDIR, however it appears to be getting set after the files have alread installed. I have the following in my wxs, but it doesn't seem to be causing the CA to happen before it actually installs files. Binary Id=CustomAction.dll SourceFile= $(var.CustomAction.TargetDir)$(var.CustomAction.TargetName).CA.dll / CustomAction Id=SetMirInstallDir BinaryKey=CustomAction.dll DllEntry= SetMirInstallDir Execute=immediate/ InstallExecuteSequence Custom Action=SetMirInstallDir Before=InstallFiles / /InstallExecuteSequence I'll try a couple of other Before targets, but if anyone has done this before it'd be a big help. A On Fri, Aug 13, 2010 at 6:23 PM, Andrew Hammond andrew.george.hamm...@gmail.com wrote: I have the following CustomAction and would like to it to set the INSTALLDIR property used in the WXS that calls it. I seem to be trying to set the property incorrectly. session[INSTALLDIR] = Some Location What is the correct way to set properties from within a CustomAction? A -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] granting permissions to arbitrary lists of users / groups
Hi, I need to grant permissions (both normal filesystem Permission and util:FileSharePermission) to lists of users / groups. I don't know in advance how many users or groups will be in each list. Is this possible and if so, how do I do it? Andrew -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] creating a clustered share?
Has anyone created a clustered share using WiX before? I'm looking for an elegant way to do this. Best Regards, Andrew -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] getting a list of properties from an already-build MSI?
Is there a way to get a list of properties from an MSI? I can install it if necessary. A -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] getting a list of properties from an already-build MSI?
My goal is to take an msi and find out what properties I can pass it on the command line when I run msiexec. I see a number of entries from the log when I install it that look like the following: MSI (s) (D8:D0) [17:07:48:626]: PROPERTY CHANGE: Adding BIN property. Its value is 'redacted'. MSI (s) (D8:D0) [17:07:48:626]: PROPERTY CHANGE: Adding CONFIGS property. Its value is 'redacted'. MSI (s) (D8:D0) [17:07:48:626]: PROPERTY CHANGE: Adding INSTALLDIR property. Its value is 'redacted'. MSI (s) (D8:D0) [17:07:48:626]: PROPERTY CHANGE: Adding TARGETDIR property. Its value is 'redacted'. MSI (s) (D8:D0) [17:07:48:626]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'redacted'. Are these the properties? Andrew On Fri, Jun 18, 2010 at 4:49 PM, Blair os...@live.com wrote: There are properties that are defined by the system, properties that are defined by the package (initial values are in the Property table), and properties that are created while the installation transaction proceeds (whether by searches or custom actions). To see final values for all custom actions (as well as property creations and value changes) generate a verbose log in your transaction. -Original Message- From: Andrew Hammond [mailto:andrew.george.hamm...@gmail.com] Sent: Friday, June 18, 2010 4:31 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] getting a list of properties from an already-build MSI? Is there a way to get a list of properties from an MSI? I can install it if necessary. A -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] shared config file clobbering
That worked perfectly. Thanks! Andrew On Tue, Jun 15, 2010 at 3:40 PM, Blair os...@live.com wrote: If your base XML file (as shared by all three products) is fairly static, you should be able to create a shared component (a component where the GUID and the directory are the same for all three products). If your XML transformations can be applied in any order, you shouldn't have any problem using them (you will need to have them be in a different component than the shared component, unique to each product). If those components include removal instructions, you should be able to easily add/remove products easily. If any of your transformations need to change the same node in your base XML, you will have some additional work that may require a custom action to read the current file to compute the new value(s) to use. -Original Message- From: Andrew Hammond [mailto:andrew.george.hamm...@gmail.com] Sent: Tuesday, June 15, 2010 10:42 AM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] shared config file clobbering I have an XML config file which is shared by three products. Each installer currently uses util:XmlFile actions to put appropriate information in the config file. When only one product is installed, this works fine, but when two or more are installed, the last one installed clobbers the config of any others. What I would like is for any of them to install the base file if it doesn't exist and then to apply the xml transformations so that the end result is a merge of all the transformations involved. These transformations are idempotent and discrete. Is this a reasonable approach or is there a better solution? The other idea I had was to have the file be in a separate installer and then have the other installers depend on it and only run the transformations. Can anyone please offer advice? Andrew -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] shared config file clobbering
I have an XML config file which is shared by three products. Each installer currently uses util:XmlFile actions to put appropriate information in the config file. When only one product is installed, this works fine, but when two or more are installed, the last one installed clobbers the config of any others. What I would like is for any of them to install the base file if it doesn't exist and then to apply the xml transformations so that the end result is a merge of all the transformations involved. These transformations are idempotent and discrete. Is this a reasonable approach or is there a better solution? The other idea I had was to have the file be in a separate installer and then have the other installers depend on it and only run the transformations. Can anyone please offer advice? Andrew -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ICE48: Directory 'INSTALLDIR' appears to be hardcoded in the property table to a local drive, except it's not.
That worked. It feels like using an un-defined variable, but... ok. :) A On Mon, Jun 7, 2010 at 7:20 PM, Rob Mensching r...@robmensching.com wrote: Don't put anything in the Property table. If you're always going to pass it in, you don't need it in the Property table. On Mon, Jun 7, 2010 at 5:49 PM, Andrew Hammond andrew.george.hamm...@gmail.com wrote: I have the following error (treating warnings as errors, warning level pedantic): ICE48: Directory 'INSTALLDIR' appears to be hardcoded in the property table to a local drive. However INSTALLDIR is a property that I expect to always pass in to msiexec at install time. How can I either fix the problem or suppress the error message please? Andrew -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] ICE48: Directory 'INSTALLDIR' appears to be hardcoded in the property table to a local drive, except it's not.
I have the following error (treating warnings as errors, warning level pedantic): ICE48: Directory 'INSTALLDIR' appears to be hardcoded in the property table to a local drive. However INSTALLDIR is a property that I expect to always pass in to msiexec at install time. How can I either fix the problem or suppress the error message please? Andrew -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ResolveWixReferences task was not found?
I re-installed and everything is working fine now. Thanks! A On Mon, May 24, 2010 at 11:22 AM, Blair os...@live.com wrote: The RTM 3.0 wix.targets file contains the UsingTask element for that task. Verify that your wix.targets file is not corrupted. -Original Message- From: Andrew Hammond [mailto:andrew.george.hamm...@gmail.com] Sent: Thursday, May 20, 2010 4:47 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] ResolveWixReferences task was not found? I created a very simple WIX project, added a reference to WixUtilExtension and then tried to build it. I'm getting the following error: The ResolveWixReferences task was not found. Check the following: 1.) The name of the task in the project file is the same as the name of the task class. 2.) The task class is public and implements the Microsoft.Build.Framework.ITask interface. 3.) The task is correctly declared with UsingTask in the project file, or in the *.tasks files located in the C:\Windows\Microsoft.NET\Framework\v2.0.50727 directory. C:\Program Files (x86)\MSBuild\Microsoft\WiX\v3.0\Wix.targets6306 LogRepository Google didn't help. Has anyone seen this before? I'm running VS 2008 with WIX3_x64 version 3.0.5419.0. Andrew -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] ResolveWixReferences task was not found?
I created a very simple WIX project, added a reference to WixUtilExtension and then tried to build it. I'm getting the following error: The ResolveWixReferences task was not found. Check the following: 1.) The name of the task in the project file is the same as the name of the task class. 2.) The task class is public and implements the Microsoft.Build.Framework.ITask interface. 3.) The task is correctly declared with UsingTask in the project file, or in the *.tasks files located in the C:\Windows\Microsoft.NET\Framework\v2.0.50727 directory. C:\Program Files (x86)\MSBuild\Microsoft\WiX\v3.0\Wix.targets6306 LogRepository Google didn't help. Has anyone seen this before? I'm running VS 2008 with WIX3_x64 version 3.0.5419.0. Andrew -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] de-globalizing a variable referenced by a Directory?
Pally, these are all good pointers.The LOGDIRECTORY is actually a UNC path. The installer needs to go an create some folders there, so I'm not sure where the correct location for it would be. What would probably solve my problem is being able to have a separate directory tree, defined in a separate fragment from the base directory tree. I'll go read that tutorial and see if that gets me further. Thanks! On Wed, Mar 24, 2010 at 4:00 AM, Pally Sandher pally.sand...@iesve.comwrote: LOGDIRECTORY is a Property not a variable since it's all upper case it's a Public one (http://msdn.microsoft.com/en-us/library/aa370912.aspx). Essentially Properties are Windows Installers variables but you can use variables in WiX so confusing the two now might cause you problems later on. I think your directory tree isn't setup correctly for what you're trying to do. If the directory defined by LOGDIRECTORY is the 2nd top most directory in the tree with everything below it you're probably doing it wrong. You may want to do something similar to the following instead: Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Directory Id=INSTALLLOCATION Name=My Folder ... [your directories components can go here] /Directory /Directory Directory Id=CommonAppDataFolder Directory Id=LOGDIRECTORY ... [whatever you want under LOGDIRECTORY goes here] /Directory /Directory /Directory That is assuming you want LOGDIRECTORY to go somewhere under CommonAppData, if not modify it with the System Folder property you wish it to go under as appropriate (see the Property Reference on MSDN for other System Folder properties). This is covered in the tutorial at http://www.tramontana.co.hu/wix/lesson1.php#1.2 Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Andrew Hammond [mailto:andrew.george.hamm...@gmail.com] Sent: 24 March 2010 04:19 To: wix-users@lists.sourceforge.net Subject: [WiX-users] de-globalizing a variable referenced by a Directory? I inherited an installer with some code that looks like the following: Directory Id=TARGETDIR Name=SourceDir Directory Id=LOGDIRECTORY The LOGDIRECTORY is a variable, and the directory name is derived from it. Unfortunately, this means that LOGDIRECTORY must always be defined, even when I'm trying to install a component that has nothing to do with the LOGDIRECTORY. Is there some way around this or should I simply make this a global variable and deal with the fact that it's ugly? Andrew -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] de-globalizing a variable referenced by a Directory?
So, I don't see how to have this be only required when I'm installing a component that actually uses the LOGDIRECTORY. Can I move a part of the directory tree into a separate component? A On Wed, Mar 24, 2010 at 10:52 AM, Andrew Hammond andrew.george.hamm...@gmail.com wrote: Pally, these are all good pointers.The LOGDIRECTORY is actually a UNC path. The installer needs to go an create some folders there, so I'm not sure where the correct location for it would be. What would probably solve my problem is being able to have a separate directory tree, defined in a separate fragment from the base directory tree. I'll go read that tutorial and see if that gets me further. Thanks! On Wed, Mar 24, 2010 at 4:00 AM, Pally Sandher pally.sand...@iesve.comwrote: LOGDIRECTORY is a Property not a variable since it's all upper case it's a Public one (http://msdn.microsoft.com/en-us/library/aa370912.aspx). Essentially Properties are Windows Installers variables but you can use variables in WiX so confusing the two now might cause you problems later on. I think your directory tree isn't setup correctly for what you're trying to do. If the directory defined by LOGDIRECTORY is the 2nd top most directory in the tree with everything below it you're probably doing it wrong. You may want to do something similar to the following instead: Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Directory Id=INSTALLLOCATION Name=My Folder ... [your directories components can go here] /Directory /Directory Directory Id=CommonAppDataFolder Directory Id=LOGDIRECTORY ... [whatever you want under LOGDIRECTORY goes here] /Directory /Directory /Directory That is assuming you want LOGDIRECTORY to go somewhere under CommonAppData, if not modify it with the System Folder property you wish it to go under as appropriate (see the Property Reference on MSDN for other System Folder properties). This is covered in the tutorial at http://www.tramontana.co.hu/wix/lesson1.php#1.2 Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Andrew Hammond [mailto:andrew.george.hamm...@gmail.com] Sent: 24 March 2010 04:19 To: wix-users@lists.sourceforge.net Subject: [WiX-users] de-globalizing a variable referenced by a Directory? I inherited an installer with some code that looks like the following: Directory Id=TARGETDIR Name=SourceDir Directory Id=LOGDIRECTORY The LOGDIRECTORY is a variable, and the directory name is derived from it. Unfortunately, this means that LOGDIRECTORY must always be defined, even when I'm trying to install a component that has nothing to do with the LOGDIRECTORY. Is there some way around this or should I simply make this a global variable and deal with the fact that it's ugly? Andrew -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] de-globalizing a variable referenced by a Directory?
I inherited an installer with some code that looks like the following: Directory Id=TARGETDIR Name=SourceDir Directory Id=LOGDIRECTORY The LOGDIRECTORY is a variable, and the directory name is derived from it. Unfortunately, this means that LOGDIRECTORY must always be defined, even when I'm trying to install a component that has nothing to do with the LOGDIRECTORY. Is there some way around this or should I simply make this a global variable and deal with the fact that it's ugly? Andrew -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] strangeness with directory permissions
I have a strange issue with creating and setting permissions on a new
directory. My goal is to have THE_USER_ACCOUNT user to have permission to
create, and rename files in this new directory. The following relevant
snippets create the dir and set permissions for all the other users
correctly. It gets most of the correct permissions for THE_USER_ACCOUNT, but
not modify permissions (specifically, it's missing the ability to delete
children). Strangely, a co-worker tried running with this configuration and
it worked exactly correctly. We have not been able to identify a meaningful
difference in environments.
It is probably also worth noting that a typical deployment of this has
THE_USER_ACCOUNT as NT AUTHORITY\NETWORK SERVICE, but that parameter can be
set to any valid name (and we have tested with a local user, network
service, and a domain user on both systems. On his, this works, but on mine
and in QA it fails).
ComponentRef Id=DWCH_CreateMyNewDirAndSetPermissions/
!-- A directory tree --
Directory Id=Directory.MyNewDir Name=MyNewDir /
DirectoryRef Id=Directory.MyNewDir
Component Id=CreateMyNewDirAndSetPermissions
Guid={E1081F4C-7AA6-44f6-9F4C-6EAD4833D9FA}
ConditionCREATE_MY_NEW_DIR=1/Condition
CreateFolder
Permission User='[THE_USER_ACCOUNT]' GenericExecute='yes'
Read='yes' GenericRead='yes' GenericWrite='yes' DeleteChild='yes' /
Permission User='Administrators' GenericAll='yes' /
Permission User='Users' Read='yes' GenericRead='yes' /
/CreateFolder
/Component
/DirectoryRef
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
