[WiX-users] InstallAware Help...
Hi, Looking for help with upgrading a product previously installed by InstallAware, now we are using WIX. Thanks. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] logging
Something like this may help: http://blog.crankybit.com/redirecting-output-to-a-file-in-windows-batch-scripts/ David Amey wrote: > > Hello All > > Can someone please explain how I can turn logging on during the candle and > light calls, as I have errors that I need to correct. > I am automating the calls, which causes the command prompt to close very > quickly after the code has been run. > > Thanks in advance. > > PS thank you Tonny Erjomin for the help on language support > David Amey > The Creative Engine Ltd > Almac House, Church Lane, Bisley, Surrey, GU24 9DR > T: +44 (0)1483 799200 F: +44 (0)1483 799111 > > -- > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/logging-tp6474846p6475377.html Sent from the wix-users mailing list archive at Nabble.com. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Help with giving permissions to folder
The reason I'm using a fragment is to try to keep things organized. The installer is installing files in one location, but as part of the installation process I need to modify the ACL of the MachineKeys folder, which as you know will be in a completely different location from my installation files. >From what I read "AppDataFolder" should provide the complete path to the "Application Data" folder, which should be "C:\Documents and Settings\All Users\Application Data" as this is being installed on a Windows 2003 server. This doesn't seem to be working, because when I navigate to the above path and continue to Microsoft\Crypto\RSA\MachineKeys, "Network Service" has not been added to the MachineKeys folder along with the permissions I specified. On Tue, Jun 14, 2011 at 12:00 PM, David Watson wrote: > Either take it out of the fragment or use a DirectoryRef. > > > > > Name="Microsoft"> > > > Name="MachineKeys"> > Guid="352963FCB3794D8E9B9BE725929B5C47"> > > GenericAll="yes" ChangePermission="yes" /> > > > > > > > > > > > I usually leave my directory structure in the main wxs and wrap the > component > in a directoryRef in the fragment. > > It all depends on why you are using a fragment really. > > > -Original Message- > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > Sent: 14 June 2011 16:16 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Help with giving permissions to folder > > I knew there was something I was probably missing. I've added the > componentRef, but the build fails with the following error: > > The primary key 'TARGETDIR' is duplicated in table 'Directory'. Please > remove one of the entries or rename a part of the primary key to avoid the > collision. > > It is true that I already have a TARGETDIR for the install within my > Product.wxs, but if I don't add a TARGETDIR and SourceDir to the Fragment > that contains the folder I want to set the ACL on, it fails to build. > > How can I get this to work? I've tried to vary the values for TARGETDIR and > name, but I always receive an error stating that the root directory is not > valid or that the TARGETDIR directory has an illegal DefaultDir value. > > In my Fragment file, if I don't include TARGETDIR and Name="SourceDir" I > get > an error stating that "AppDataFolder" is not a valid root directory. > > > On Tue, Jun 14, 2011 at 9:52 AM, David Watson wrote: > > > If you reference anything in a fragment then the entire fragment will be > > included in your installer. > > > > So if you add a componentRef in your feature this fragment will be > > included. > > > > > > -Original Message- > > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > > Sent: 14 June 2011 14:20 > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] Help with giving permissions to folder > > > > Thanks for you help. I understand now. Can you tell what I might have > > missed > > to cause the ACL not to be set on the MachineKeys folder? Have I missed > > something in how I've configured this? I've added the following code to a > > separate Fragment file and my understanding is that this file will be > > pulled > > into the installer. I have not referenced the file anywhere. > > > > The full path to the MachineKeys folder is: > > C:\Documents and Settings\All Users\Application > > Data\Microsoft\Crypto\RSA\MachineKeys > > > > > > > > > > > Name="Microsoft"> > > Name="Crypto"> > > Name="RSA"> > > > Name="MachineKeys"> > > > Guid="352963FCB3794D8E9B9BE725929B5C47"> > > > > > GenericAll="yes" ChangePermission="yes" /> > > > > > > > > > > > > > > > > > > > > > > Thanks again for your help. > > > > > > On Tue, Jun 14, 2011 at 7:43 AM, David Watson wrote: > > > > > No it will not overwrite it or cause it to be removed on uninstall. > > > > > > The code example is to set permissions on the windows\temp folder which > > > pre-exists and the permission is added to the ACL of the folder. > > > > > > > > > > > > -Original Message- > > > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > > > Sent: 14 June 2011 11:15 > > > To: General discussion for Windows Installer XML toolset. > > > Subject: Re: [WiX-users] Help with giving permissions to folder > > > > > > I do not want to recreate or overwrite the MachineKeys folder that > > already > > > exists. Will adding as you suggest below overwrite the > > > existing folder? If so, how can I avoid that, but still add the > > permission > > > I > > > need to the folder? > > > > > > On Tue, Jun 14, 2011 at 5:23 AM, David Watson wro
[WiX-users] logging
Hello All Can someone please explain how I can turn logging on during the candle and light calls, as I have errors that I need to correct. I am automating the calls, which causes the command prompt to close very quickly after the code has been run. Thanks in advance. PS thank you Tonny Erjomin for the help on language support David Amey The Creative Engine Ltd Almac House, Church Lane, Bisley, Surrey, GU24 9DR T: +44 (0)1483 799200 F: +44 (0)1483 799111 -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Help with giving permissions to folder
Either take it out of the fragment or use a DirectoryRef. I usually leave my directory structure in the main wxs and wrap the component in a directoryRef in the fragment. It all depends on why you are using a fragment really. -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: 14 June 2011 16:16 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Help with giving permissions to folder I knew there was something I was probably missing. I've added the componentRef, but the build fails with the following error: The primary key 'TARGETDIR' is duplicated in table 'Directory'. Please remove one of the entries or rename a part of the primary key to avoid the collision. It is true that I already have a TARGETDIR for the install within my Product.wxs, but if I don't add a TARGETDIR and SourceDir to the Fragment that contains the folder I want to set the ACL on, it fails to build. How can I get this to work? I've tried to vary the values for TARGETDIR and name, but I always receive an error stating that the root directory is not valid or that the TARGETDIR directory has an illegal DefaultDir value. In my Fragment file, if I don't include TARGETDIR and Name="SourceDir" I get an error stating that "AppDataFolder" is not a valid root directory. On Tue, Jun 14, 2011 at 9:52 AM, David Watson wrote: > If you reference anything in a fragment then the entire fragment will be > included in your installer. > > So if you add a componentRef in your feature this fragment will be > included. > > > -Original Message- > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > Sent: 14 June 2011 14:20 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Help with giving permissions to folder > > Thanks for you help. I understand now. Can you tell what I might have > missed > to cause the ACL not to be set on the MachineKeys folder? Have I missed > something in how I've configured this? I've added the following code to a > separate Fragment file and my understanding is that this file will be > pulled > into the installer. I have not referenced the file anywhere. > > The full path to the MachineKeys folder is: > C:\Documents and Settings\All Users\Application > Data\Microsoft\Crypto\RSA\MachineKeys > > > > > Name="Microsoft"> > > > Name="MachineKeys"> > Guid="352963FCB3794D8E9B9BE725929B5C47"> > > GenericAll="yes" ChangePermission="yes" /> > > > > > > > > > > > Thanks again for your help. > > > On Tue, Jun 14, 2011 at 7:43 AM, David Watson wrote: > > > No it will not overwrite it or cause it to be removed on uninstall. > > > > The code example is to set permissions on the windows\temp folder which > > pre-exists and the permission is added to the ACL of the folder. > > > > > > > > -Original Message- > > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > > Sent: 14 June 2011 11:15 > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] Help with giving permissions to folder > > > > I do not want to recreate or overwrite the MachineKeys folder that > already > > exists. Will adding as you suggest below overwrite the > > existing folder? If so, how can I avoid that, but still add the > permission > > I > > need to the folder? > > > > On Tue, Jun 14, 2011 at 5:23 AM, David Watson wrote: > > > > > The relevant parent of util:permissionex is createfolder. > > > > > > Put a component in your directory tree that has a CreateFolder with a > > > permissionsEx nexted in it. > > > > > > An example... > > > > > > > > > > > > > > Action="write" Value="1" Root="HKLM" Key="$(var.RegistryPath)" > > > Name="windowstempfolderpermissions" KeyPath="yes"/> > > > > > > > > Domain="[ComputerName]" /> > > > > > > > > > > > > > > > -Original Message- > > > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > > > Sent: 13 June 2011 17:28 > > > To: General discussion for Windows Installer XML toolset. > > > Subject: [WiX-users] Help with giving permissions to folder > > > > > > My installer needs to encrypt the ConnectionStrings section of the > > > web.config file for our web application. This part I have working with > no > > > problems, but as part of the process I need to provide the Network > > Service > > > with full control access to the following folder: > > > > > > *C:\Documents and Settings\All Users\Application > > > Data\Microsoft\Crypto\RSA\MachineKeys* > > > > > > I have not been able to figure
Re: [WiX-users] looking for some help on a file-copying task during install
Thanks, Pally. I actually found Bob's article right after I sent out this message yesterday. It's very enlightening. To tie everything together once again, what I had below for the code block was really a test trying to figure out when &BaseFeature had a reasonable value. The real issue at this point (just to further complicate things, and going back to my original post) is that there are 2 files, one per feature, and that the CMP_BaseCopyConfig should only run if the first feature is being installed and NOT the second. The second file should only be installed if the second feature is being installed (I can handle that one as you suggest.) What I found out, through Bob's article and another blog article from Rob Mensching about how "VBScript and JScript Custom Actions suck" is that: a) I need to do the test for copying post-CostFinalize, necessitating a custom action b) doing the copy with VBScript or JScript will (and did, in my case) run afoul of virus checkers, throwing up an error and failing c) it appears the only way to do this (unless I missed something elsewhere) is via compiled code that I have to write. Does anybody else see any other way to get this done--copy a file from BaseFeature if ExtrasFeature is not being installed, and copy a file from ExtrasFeature if it IS being installed? (Obviously the second one can just be done by including a second reference to the extras-config.xml to install the copy--no custom action needed, per Pally's suggestion below.) It does seem pretty unfortunate that a simple thing like copying 1 file based on whether or not some feature is being installed is so involved, and requires writing C++ or other compiled code to do it. Thanks, Dave On Tue, Jun 14, 2011 at 3:21 AM, Pally Sandher wrote: > The Component Table MSDN page > (http://msdn.microsoft.com/en-us/library/aa368007.aspx) has this to say > about the Condition field: > "The Condition field enables or disables a component only during the > CostFinalize action. To enable or disable a component after > CostFinalize, you must use a custom action or the DoAction ControlEvent > to call MsiSetComponentState." > Which is what I think you're running into. > > Bob Arnson wrote a blog article explaining the confusion here a while > back -> > http://www.joyofsetup.com/2008/04/09/feature-states-in-component-conditi > ons/ > > The simple solution is to add a ComponentRef for CMP_BaseCopyConfig to > BaseFeature. You're trying to make that Component install only when the > Feature is installed so the logical solution would be to make it part of > it & skip Conditioning it all together since it's unnecessary. > > Palbinder Sandher > Software Deployment Engineer > T: +44 (0) 141 945 8500 > F: +44 (0) 141 945 8501 > > http://www.iesve.com > **Design, Simulate + Innovate with the ** > 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: Dave Combs [mailto:dave.co...@kaazing.com] > Sent: 13 June 2011 23:29 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] looking for some help on a file-copying task > duringinstall > > I figured out the 'insufficient privileges' problem (it was because I > had > another window open on the directory at the time, so everything just > failed, > but with the odd message.) That ran me into another problem. With the > stuff below I can write a condition > > > > > > to conditionally do the copying of the file base-config.xml to > config.xml. > However, this test always fails, even when I choose to install the base > feature. However, if I choose to install the base feature but change > the > condition to NOT (&BaseFeature=3), the copying occurs. Of course, it's > not > what I want. Can anybody suggest why the reference to &BaseFeature > above > doesn't seem to return a usable value? > > Here's the complete code block: > > > Guid="2E5C60C4-956A-11E0-BC3C-BCD94824019B" KeyPath="yes"> > > > > FileId="FILE_31" > DestinationDirectory="DIR_6" DestinationName="config.xml" > /> > > > > The fileId FILE_31 points to the base-config.xml file. > > Dave > > On Mon, Jun 13, 2011 at 11:18 AM, Dave Combs > wrote: > > > Actually, I ended up doing something I found in the list archives from > 19 > > Oct 2006: > > > > I also found another way of solving this issue. put the component > > (that contained the ) into a > > element. This is possible because I specify both source (by FileId) > > and destination (by DestinationProperty) explicitely in the > > element. I consider this way of doing it to be cleaner, since I avoid > > an artificial element. > > > > Thanks for all the replies anyway. > > > > Jarl > > > > -- > > Jarl Friis > > > > > > However, I now run into a different problem that I'm once again > looki
Re: [WiX-users] Help with giving permissions to folder
I knew there was something I was probably missing. I've added the componentRef, but the build fails with the following error: The primary key 'TARGETDIR' is duplicated in table 'Directory'. Please remove one of the entries or rename a part of the primary key to avoid the collision. It is true that I already have a TARGETDIR for the install within my Product.wxs, but if I don't add a TARGETDIR and SourceDir to the Fragment that contains the folder I want to set the ACL on, it fails to build. How can I get this to work? I've tried to vary the values for TARGETDIR and name, but I always receive an error stating that the root directory is not valid or that the TARGETDIR directory has an illegal DefaultDir value. In my Fragment file, if I don't include TARGETDIR and Name="SourceDir" I get an error stating that "AppDataFolder" is not a valid root directory. On Tue, Jun 14, 2011 at 9:52 AM, David Watson wrote: > If you reference anything in a fragment then the entire fragment will be > included in your installer. > > So if you add a componentRef in your feature this fragment will be > included. > > > -Original Message- > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > Sent: 14 June 2011 14:20 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Help with giving permissions to folder > > Thanks for you help. I understand now. Can you tell what I might have > missed > to cause the ACL not to be set on the MachineKeys folder? Have I missed > something in how I've configured this? I've added the following code to a > separate Fragment file and my understanding is that this file will be > pulled > into the installer. I have not referenced the file anywhere. > > The full path to the MachineKeys folder is: > C:\Documents and Settings\All Users\Application > Data\Microsoft\Crypto\RSA\MachineKeys > > > > > Name="Microsoft"> > > > Name="MachineKeys"> > Guid="352963FCB3794D8E9B9BE725929B5C47"> > > GenericAll="yes" ChangePermission="yes" /> > > > > > > > > > > > Thanks again for your help. > > > On Tue, Jun 14, 2011 at 7:43 AM, David Watson wrote: > > > No it will not overwrite it or cause it to be removed on uninstall. > > > > The code example is to set permissions on the windows\temp folder which > > pre-exists and the permission is added to the ACL of the folder. > > > > > > > > -Original Message- > > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > > Sent: 14 June 2011 11:15 > > To: General discussion for Windows Installer XML toolset. > > Subject: Re: [WiX-users] Help with giving permissions to folder > > > > I do not want to recreate or overwrite the MachineKeys folder that > already > > exists. Will adding as you suggest below overwrite the > > existing folder? If so, how can I avoid that, but still add the > permission > > I > > need to the folder? > > > > On Tue, Jun 14, 2011 at 5:23 AM, David Watson wrote: > > > > > The relevant parent of util:permissionex is createfolder. > > > > > > Put a component in your directory tree that has a CreateFolder with a > > > permissionsEx nexted in it. > > > > > > An example... > > > > > > > > > > > > > > Action="write" Value="1" Root="HKLM" Key="$(var.RegistryPath)" > > > Name="windowstempfolderpermissions" KeyPath="yes"/> > > > > > > > > Domain="[ComputerName]" /> > > > > > > > > > > > > > > > -Original Message- > > > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > > > Sent: 13 June 2011 17:28 > > > To: General discussion for Windows Installer XML toolset. > > > Subject: [WiX-users] Help with giving permissions to folder > > > > > > My installer needs to encrypt the ConnectionStrings section of the > > > web.config file for our web application. This part I have working with > no > > > problems, but as part of the process I need to provide the Network > > Service > > > with full control access to the following folder: > > > > > > *C:\Documents and Settings\All Users\Application > > > Data\Microsoft\Crypto\RSA\MachineKeys* > > > > > > I have not been able to figure out how to configure this with in my > > > installer. > > > > > > I've tried adding the following to my Product.wxs, but it gives a build > > > error of: "The Directory element contains an unexpected child element > > > 'util:PermissionEx'.". And xmlns:util has been added to the beginning > of > > my > > > Product.wxs. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > GenericAll="yes" > > > ChangePermission="yes" /> > > > > > > > > > > > > > > > > > > > > > > > > > > > How can this be do
[WiX-users] Continue after custom confirmation dialog
Hello, I'm having trouble showing a custom 'confirm' dialog in the middle of my install sequence and continuing on property. I'm using 3.5 RTM. Currently I show the welcome dialog, then the license agreement. After that I want to show a warning in a spawned dialog. If the user agrees to it I want to continue onto the next dialog. However, if I raise a 'new dialog' from the license agreement's Next button, as well as spawning the confirmation dialog, it does not show. I get the confirmation dialog, but not the new/next one. If I raise a new dialog from the OK button on the spawned dialog I DO get the next dialog but it's replaced the spawned one, not the license agreement, so when I go back I get an error 2856. My current code looks like this: 1 ConfirmEnable 1 11 I don't think I should do a new dialog from the confirmation dialog, but I cannot get the next dialog (InstallDirDlg) to show otherwise. The properties are set correctly, but when I spawn a dialog I cannot get the next dialog to show after clicking OK without creating a second form. This gives an error if I try to go back. What am I doing wrong? Has this already been answered because I couldn't find it in the list. Note: the ConfirmEnableWindowsSearchDlg has NO elements. The OK button control sets the 'ConfirmEnable' property to 1 and the Cancel button does nothing. Regards, Isobel Smith Software Engineer Exclaimer Limited Tel:+44 (0) 1252 531 422 Fax:+44 (0) 845 050 4044 Email: mailto:isobel.sm...@exclaimer.com Best Selling Mail disclaiming products for Microsoft Exchange Environments. Please consider the environment before printing this email message. Disclaimer: This message contains confidential information and is intended only for wix-users@lists.sourceforge.net. If you are not wix-users@lists.sourceforge.net you should not disseminate, distribute or copy this e-mail. Please notify isobel.sm...@exclaimer.com immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Isobel Smith therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Exclaimer is a limited company registered in England and Wales. Registered number: 4938619. Registered office: Alpha House 9-11 Alexandra Road Farnborough Hampshire GU14 6BU United Kingdom -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Reliable major upgrade
Yes, schedule your major upgrade (RemoveExistingProduct action if you're not using the MajorUpgrade element) before InstallInitialize. On Tue, Jun 14, 2011 at 6:40 AM, Michael Stoll wrote: > Hi, > > I have a msi created with wix, which installs and uninstalls fine. But > if I use it as upgrade, some files are kept in the prior version. > This happens to .NET assemblies if the version is the same as before. > That's easy to fix. > But what happens to unversioned files during a major upgrade? What's > about registry keys? Is it possible to have the major upgrade behave > exactly like uninstall, install? > Are there some guidelines what should be payed attention to? > > Michael > > > > -- > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Help with giving permissions to folder
If you reference anything in a fragment then the entire fragment will be included in your installer. So if you add a componentRef in your feature this fragment will be included. -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: 14 June 2011 14:20 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Help with giving permissions to folder Thanks for you help. I understand now. Can you tell what I might have missed to cause the ACL not to be set on the MachineKeys folder? Have I missed something in how I've configured this? I've added the following code to a separate Fragment file and my understanding is that this file will be pulled into the installer. I have not referenced the file anywhere. The full path to the MachineKeys folder is: C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys Thanks again for your help. On Tue, Jun 14, 2011 at 7:43 AM, David Watson wrote: > No it will not overwrite it or cause it to be removed on uninstall. > > The code example is to set permissions on the windows\temp folder which > pre-exists and the permission is added to the ACL of the folder. > > > > -Original Message- > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > Sent: 14 June 2011 11:15 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Help with giving permissions to folder > > I do not want to recreate or overwrite the MachineKeys folder that already > exists. Will adding as you suggest below overwrite the > existing folder? If so, how can I avoid that, but still add the permission > I > need to the folder? > > On Tue, Jun 14, 2011 at 5:23 AM, David Watson wrote: > > > The relevant parent of util:permissionex is createfolder. > > > > Put a component in your directory tree that has a CreateFolder with a > > permissionsEx nexted in it. > > > > An example... > > > > > > > > > Action="write" Value="1" Root="HKLM" Key="$(var.RegistryPath)" > > Name="windowstempfolderpermissions" KeyPath="yes"/> > > > > > Domain="[ComputerName]" /> > > > > > > > > > > -Original Message- > > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > > Sent: 13 June 2011 17:28 > > To: General discussion for Windows Installer XML toolset. > > Subject: [WiX-users] Help with giving permissions to folder > > > > My installer needs to encrypt the ConnectionStrings section of the > > web.config file for our web application. This part I have working with no > > problems, but as part of the process I need to provide the Network > Service > > with full control access to the following folder: > > > > *C:\Documents and Settings\All Users\Application > > Data\Microsoft\Crypto\RSA\MachineKeys* > > > > I have not been able to figure out how to configure this with in my > > installer. > > > > I've tried adding the following to my Product.wxs, but it gives a build > > error of: "The Directory element contains an unexpected child element > > 'util:PermissionEx'.". And xmlns:util has been added to the beginning of > my > > Product.wxs. > > > > > > > > > > > > > > > > > > > > > > GenericAll="yes" > > ChangePermission="yes" /> > > > > > > > > > > > > > > > > > > How can this be done? > > > > > > - > > - > > EditLive Enterprise is the world's most technically advanced content > > authoring tool. Experience the power of Track Changes, Inline Image > > Editing and ensure content is compliant with Accessibility Checking. > > http://p.sf.net/sfu/ephox-dev2dev > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > SDL PLC confidential, all rights reserved. > > If you are not the intended recipient of this mail SDL requests and > > requires that you delete it without acting upon or copying any of its > > contents, and we further request that you advise us. > > SDL PLC is a public limited company registered in England and Wales. > > Registered number: 02675207. > > Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire > SL6 > > 7DY, UK. > > > > > > > > > > - > - > > EditLive Enterprise is the world's most technically advanced content > > authoring tool. Experience the power of Track Changes, Inline Image > > Editing and ensure content is compliant with Accessibility Checkin
[WiX-users] Reliable major upgrade
Hi, I have a msi created with wix, which installs and uninstalls fine. But if I use it as upgrade, some files are kept in the prior version. This happens to .NET assemblies if the version is the same as before. That's easy to fix. But what happens to unversioned files during a major upgrade? What's about registry keys? Is it possible to have the major upgrade behave exactly like uninstall, install? Are there some guidelines what should be payed attention to? Michael -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Help with giving permissions to folder
Thanks for you help. I understand now. Can you tell what I might have missed to cause the ACL not to be set on the MachineKeys folder? Have I missed something in how I've configured this? I've added the following code to a separate Fragment file and my understanding is that this file will be pulled into the installer. I have not referenced the file anywhere. The full path to the MachineKeys folder is: C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys Thanks again for your help. On Tue, Jun 14, 2011 at 7:43 AM, David Watson wrote: > No it will not overwrite it or cause it to be removed on uninstall. > > The code example is to set permissions on the windows\temp folder which > pre-exists and the permission is added to the ACL of the folder. > > > > -Original Message- > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > Sent: 14 June 2011 11:15 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Help with giving permissions to folder > > I do not want to recreate or overwrite the MachineKeys folder that already > exists. Will adding as you suggest below overwrite the > existing folder? If so, how can I avoid that, but still add the permission > I > need to the folder? > > On Tue, Jun 14, 2011 at 5:23 AM, David Watson wrote: > > > The relevant parent of util:permissionex is createfolder. > > > > Put a component in your directory tree that has a CreateFolder with a > > permissionsEx nexted in it. > > > > An example... > > > > > > > > > Action="write" Value="1" Root="HKLM" Key="$(var.RegistryPath)" > > Name="windowstempfolderpermissions" KeyPath="yes"/> > > > > > Domain="[ComputerName]" /> > > > > > > > > > > -Original Message- > > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > > Sent: 13 June 2011 17:28 > > To: General discussion for Windows Installer XML toolset. > > Subject: [WiX-users] Help with giving permissions to folder > > > > My installer needs to encrypt the ConnectionStrings section of the > > web.config file for our web application. This part I have working with no > > problems, but as part of the process I need to provide the Network > Service > > with full control access to the following folder: > > > > *C:\Documents and Settings\All Users\Application > > Data\Microsoft\Crypto\RSA\MachineKeys* > > > > I have not been able to figure out how to configure this with in my > > installer. > > > > I've tried adding the following to my Product.wxs, but it gives a build > > error of: "The Directory element contains an unexpected child element > > 'util:PermissionEx'.". And xmlns:util has been added to the beginning of > my > > Product.wxs. > > > > > > > > > > > > > > > > > > > > > > GenericAll="yes" > > ChangePermission="yes" /> > > > > > > > > > > > > > > > > > > How can this be done? > > > > > > - > > - > > EditLive Enterprise is the world's most technically advanced content > > authoring tool. Experience the power of Track Changes, Inline Image > > Editing and ensure content is compliant with Accessibility Checking. > > http://p.sf.net/sfu/ephox-dev2dev > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > SDL PLC confidential, all rights reserved. > > If you are not the intended recipient of this mail SDL requests and > > requires that you delete it without acting upon or copying any of its > > contents, and we further request that you advise us. > > SDL PLC is a public limited company registered in England and Wales. > > Registered number: 02675207. > > Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire > SL6 > > 7DY, UK. > > > > > > > > > > - > - > > EditLive Enterprise is the world's most technically advanced content > > authoring tool. Experience the power of Track Changes, Inline Image > > Editing and ensure content is compliant with Accessibility Checking. > > http://p.sf.net/sfu/ephox-dev2dev > > ___ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > - > - > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the pow
[WiX-users] unsubscribe
-- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Component Request: null eventhough parent featureisinADDLOCAL
Did you run heat twice, once each on the original and upgrade MSIs, or did you retain the same source code for both versions ? You should be retaining the code. Other than that, it seems OK. -Original Message- From: Tobberoth [mailto:tobber...@gmail.com] Sent: 14 June 2011 12:33 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Component Request: null eventhough parent featureisinADDLOCAL Absolutely, let me know what information is needed. Here's my patch file, which is basically straight up from the tutorial on the wix page: The components are defined in a .wxs created by heat, something like this: If I can post anything more to help you help me, just let me know. On Mon, Jun 13, 2011 at 11:34 AM, Peter Shirtcliffe wrote: > Sorry I was ambiguous. When I say "edited", I mean "edited the installed > version", not the version used to build the MSI. It sounds like you've done > it correctly. > > If the file was not edited on the target machine and you didn't find any > advertising in the log and vamus doesn't help, then I'm not sure what could > be wrong from the information given. Can you post extracts of your patch > wxs > and component definitions ? > > -Original Message- > From: Tobberoth [mailto:tobber...@gmail.com] > Sent: 13 June 2011 09:00 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Component Request: null eventhough parent > featureis > inADDLOCAL > > Thanks for your reply. > > Yes, the text file has been edited after the install. I build msi 1, > install > it. I edit the text file, create msi 2, create msp from the two msi's and > run it (with REINSTALLMODE=vamus). File is not updated nor requested. > I looked at your link and only found 2 parts. In both, the problem seemed > to have something to do with advertise, but "advertise" is not mentioned in > my patch log, so I don't think either article is relevant to my issue :( > > Any more advice would be very appreciated. > On Fri, Jun 10, 2011 at 4:36 PM, Peter Shirtcliffe > wrote: > > > Has the text file been edited since it was installed ? Ensure that the > > modification and creation dates and times are the same before applying > the > > msp. > > > > There is no reinstallmode at component level. You could try > > REINSTALLMODE=vamus to force an overwrite regardless of "version" just to > > see > > if that works. > > > > This series of 3 articles may suggest avenues of inquiry > > > > > > http://blogs.msdn.com/b/windows_installer_team/archive/2005/08/17/451516.aspx > > > > > > -Original Message- > > From: Tobberoth [mailto:tobber...@gmail.com] > > Sent: 10 June 2011 15:11 > > To: wix-users@lists.sourceforge.net > > Subject: [WiX-users] Component Request: null eventhough parent feature is > > inADDLOCAL > > > > Hello everyone, > > > > I'm trying to make an MSP which can update a few files and run a few SQL > > scripts. It has taken me ages to get anywhere because of boatloads of > > issues, but I'm finally in a situation where my MSP runs and completes, > > updating the database properly. Unfortunately, it doesn't actually update > > files and I can't understand why. My setup is like this: > > > > * I make an msi which includes a .txt file. > > * I make a second msi which includes the same .txt after it has been > > updated. > > * I make a minor upgrade .msp from the two .msi files. > > > > I run the first msi, it works great. If I run the second one (as a major > > upgrade) that works as well, it contains the updated .txt file. However, > if > > I run the first msi then run the msp, the .txt file isn't updated, even > > though opening the .msp in InstaEd! shows that the patch .cab contains > the > > updated .txt file. Running with verbose log, it looks good for the > feature: > > > > MSI (s) (6C:00) [15:37:48:756]: Feature: FEAT_Main; Installed: Local; > > Request: Local; Action: Local > > > > It's installed but it's requested to be installed again, as it should be > > since I'm running with REINSTALL=ALL and REINSTALLMODE=vomus. Sweet. > > > > However, the component which is part of the feature is showing something > > else: > > > > MSI (s) (6C:00) [15:37:48:756]: Component: > > cmp432C3967A6AA13C06D8D1E0E95348403; Installed: Local; Request: Null; > > Action: Null > > > > What? How can the component possibly not be requested when the feature > > which > > owns it is? Another component in the same feature (.sql file) is > requested > > to local as expected. > > > > Does the MSP by default not understand that it's supposed to overwrite > > files > > which have changed between packages? How can I force Request: local on > the > > component level s
Re: [WiX-users] Help with giving permissions to folder
No it will not overwrite it or cause it to be removed on uninstall. The code example is to set permissions on the windows\temp folder which pre-exists and the permission is added to the ACL of the folder. -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: 14 June 2011 11:15 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Help with giving permissions to folder I do not want to recreate or overwrite the MachineKeys folder that already exists. Will adding as you suggest below overwrite the existing folder? If so, how can I avoid that, but still add the permission I need to the folder? On Tue, Jun 14, 2011 at 5:23 AM, David Watson wrote: > The relevant parent of util:permissionex is createfolder. > > Put a component in your directory tree that has a CreateFolder with a > permissionsEx nexted in it. > > An example... > > > > Action="write" Value="1" Root="HKLM" Key="$(var.RegistryPath)" > Name="windowstempfolderpermissions" KeyPath="yes"/> > > Domain="[ComputerName]" /> > > > > > -Original Message- > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > Sent: 13 June 2011 17:28 > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Help with giving permissions to folder > > My installer needs to encrypt the ConnectionStrings section of the > web.config file for our web application. This part I have working with no > problems, but as part of the process I need to provide the Network Service > with full control access to the following folder: > > *C:\Documents and Settings\All Users\Application > Data\Microsoft\Crypto\RSA\MachineKeys* > > I have not been able to figure out how to configure this with in my > installer. > > I've tried adding the following to my Product.wxs, but it gives a build > error of: "The Directory element contains an unexpected child element > 'util:PermissionEx'.". And xmlns:util has been added to the beginning of my > Product.wxs. > > > > > > > > > > > ChangePermission="yes" /> > > > > > > > > > How can this be done? > > - > - > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > SDL PLC confidential, all rights reserved. > If you are not the intended recipient of this mail SDL requests and > requires that you delete it without acting upon or copying any of its > contents, and we further request that you advise us. > SDL PLC is a public limited company registered in England and Wales. > Registered number: 02675207. > Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 > 7DY, UK. > > > > - - > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > - - EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Component Request: null eventhough parent featureis inADDLOCAL
Absolutely, let me know what information is needed. Here's my patch file, which is basically straight up from the tutorial on the wix page: The components are defined in a .wxs created by heat, something like this: If I can post anything more to help you help me, just let me know. On Mon, Jun 13, 2011 at 11:34 AM, Peter Shirtcliffe wrote: > Sorry I was ambiguous. When I say "edited", I mean "edited the installed > version", not the version used to build the MSI. It sounds like you've done > it correctly. > > If the file was not edited on the target machine and you didn't find any > advertising in the log and vamus doesn't help, then I'm not sure what could > be wrong from the information given. Can you post extracts of your patch > wxs > and component definitions ? > > -Original Message- > From: Tobberoth [mailto:tobber...@gmail.com] > Sent: 13 June 2011 09:00 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Component Request: null eventhough parent > featureis > inADDLOCAL > > Thanks for your reply. > > Yes, the text file has been edited after the install. I build msi 1, > install > it. I edit the text file, create msi 2, create msp from the two msi's and > run it (with REINSTALLMODE=vamus). File is not updated nor requested. > I looked at your link and only found 2 parts. In both, the problem seemed > to have something to do with advertise, but "advertise" is not mentioned in > my patch log, so I don't think either article is relevant to my issue :( > > Any more advice would be very appreciated. > On Fri, Jun 10, 2011 at 4:36 PM, Peter Shirtcliffe > wrote: > > > Has the text file been edited since it was installed ? Ensure that the > > modification and creation dates and times are the same before applying > the > > msp. > > > > There is no reinstallmode at component level. You could try > > REINSTALLMODE=vamus to force an overwrite regardless of "version" just to > > see > > if that works. > > > > This series of 3 articles may suggest avenues of inquiry > > > > > > http://blogs.msdn.com/b/windows_installer_team/archive/2005/08/17/451516.aspx > > > > > > -Original Message- > > From: Tobberoth [mailto:tobber...@gmail.com] > > Sent: 10 June 2011 15:11 > > To: wix-users@lists.sourceforge.net > > Subject: [WiX-users] Component Request: null eventhough parent feature is > > inADDLOCAL > > > > Hello everyone, > > > > I'm trying to make an MSP which can update a few files and run a few SQL > > scripts. It has taken me ages to get anywhere because of boatloads of > > issues, but I'm finally in a situation where my MSP runs and completes, > > updating the database properly. Unfortunately, it doesn't actually update > > files and I can't understand why. My setup is like this: > > > > * I make an msi which includes a .txt file. > > * I make a second msi which includes the same .txt after it has been > > updated. > > * I make a minor upgrade .msp from the two .msi files. > > > > I run the first msi, it works great. If I run the second one (as a major > > upgrade) that works as well, it contains the updated .txt file. However, > if > > I run the first msi then run the msp, the .txt file isn't updated, even > > though opening the .msp in InstaEd! shows that the patch .cab contains > the > > updated .txt file. Running with verbose log, it looks good for the > feature: > > > > MSI (s) (6C:00) [15:37:48:756]: Feature: FEAT_Main; Installed: Local; > > Request: Local; Action: Local > > > > It's installed but it's requested to be installed again, as it should be > > since I'm running with REINSTALL=ALL and REINSTALLMODE=vomus. Sweet. > > > > However, the component which is part of the feature is showing something > > else: > > > > MSI (s) (6C:00) [15:37:48:756]: Component: > > cmp432C3967A6AA13C06D8D1E0E95348403; Installed: Local; Request: Null; > > Action: Null > > > > What? How can the component possibly not be requested when the feature > > which > > owns it is? Another component in the same feature (.sql file) is > requested > > to local as expected. > > > > Does the MSP by default not understand that it's supposed to overwrite > > files > > which have changed between packages? How can I force Request: local on > the > > component level since it isn't enough on the feature level? > > > > Regards > > /Tobias Dersén > > > > > > - > > - > > EditLive Enterprise is the world's most technically advanced content > > authoring tool. Experience the power of Track Changes, Inline Image > > Editing and ensure content is compliant with Accessibility Checking. > > http://p.sf.net/sfu/ephox-dev2dev > >
Re: [WiX-users] looking for some help on a file-copying task during install
The Component Table MSDN page (http://msdn.microsoft.com/en-us/library/aa368007.aspx) has this to say about the Condition field: "The Condition field enables or disables a component only during the CostFinalize action. To enable or disable a component after CostFinalize, you must use a custom action or the DoAction ControlEvent to call MsiSetComponentState." Which is what I think you're running into. Bob Arnson wrote a blog article explaining the confusion here a while back -> http://www.joyofsetup.com/2008/04/09/feature-states-in-component-conditi ons/ The simple solution is to add a ComponentRef for CMP_BaseCopyConfig to BaseFeature. You're trying to make that Component install only when the Feature is installed so the logical solution would be to make it part of it & skip Conditioning it all together since it's unnecessary. Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** 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: Dave Combs [mailto:dave.co...@kaazing.com] Sent: 13 June 2011 23:29 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] looking for some help on a file-copying task duringinstall I figured out the 'insufficient privileges' problem (it was because I had another window open on the directory at the time, so everything just failed, but with the odd message.) That ran me into another problem. With the stuff below I can write a condition to conditionally do the copying of the file base-config.xml to config.xml. However, this test always fails, even when I choose to install the base feature. However, if I choose to install the base feature but change the condition to NOT (&BaseFeature=3), the copying occurs. Of course, it's not what I want. Can anybody suggest why the reference to &BaseFeature above doesn't seem to return a usable value? Here's the complete code block: The fileId FILE_31 points to the base-config.xml file. Dave On Mon, Jun 13, 2011 at 11:18 AM, Dave Combs wrote: > Actually, I ended up doing something I found in the list archives from 19 > Oct 2006: > > I also found another way of solving this issue. put the component > (that contained the ) into a > element. This is possible because I specify both source (by FileId) > and destination (by DestinationProperty) explicitely in the > element. I consider this way of doing it to be cleaner, since I avoid > an artificial element. > > Thanks for all the replies anyway. > > Jarl > > -- > Jarl Friis > > > However, I now run into a different problem that I'm once again looking for > clarification or suggestions: > > The install proceeds correctly until near the end (when it's supposed to do > the CopyFile stuff) and I now get an error saying: > > The installer has insufficient privileges to access this directory: > C:\Program Files (x86)\Kaazing\JMS\3.2\Gateway\conf. The installation > cannot continue. Log on as administrator or contact your system > administrator. > > My confusion is because a) I have administrator privileges on the system, > and b) the installer has already copied several files into the conf > directory--all I'm doing is adding another one. Any idea why I would get > this error, given that? > > Thanks, > Dave > > > On Mon, Jun 13, 2011 at 10:35 AM, Daniel Madill wrote: > >> I would assume you just need to add a CreateFolder element to ensure the >> destination directory is created. For example: >> >> >> >> Dan >> >> -Original Message- >> From: Dave Combs [mailto:dave.co...@kaazing.com] >> Sent: Monday, June 13, 2011 1:10 PM >> To: General discussion for Windows Installer XML toolset. >> Subject: Re: [WiX-users] looking for some help on a file-copying task >> during install >> >> Actually, I did run into an issue with trying your solution, and was >> curious >> if you or anybody else had an idea: >> >> In the that contains the 'base-config.xml' and >> 'extras-config.xml' Components I put the following: >> >> > Guid="2E5C60C4-956A-11E0-BC3C-BCD94824019B"> >>NOT &ExtrasFeature=3 >>> SourceName="base-config.xml" >> DestinationDirectory="DIR_6" >> DestinationName="config.xml" /> >> >> >> > Guid="399EA6B8-956A-11E0-8EC6-CBD94824019B"> >>&ExtrasFeature=3 AND NOT >> !ExtrasFeature=3 >>> SourceName="extras-config.xml" >> DestinationDirectory="DIR_6" >> DestinationName="config.xml" /> >> >> >> In this, DIR_6 is the ID of the directory I'm copying to, DIR_36 is the ID >> of the containing that I'm copying from. >> With the above I get the following
Re: [WiX-users] Help with giving permissions to folder
I do not want to recreate or overwrite the MachineKeys folder that already exists. Will adding as you suggest below overwrite the existing folder? If so, how can I avoid that, but still add the permission I need to the folder? On Tue, Jun 14, 2011 at 5:23 AM, David Watson wrote: > The relevant parent of util:permissionex is createfolder. > > Put a component in your directory tree that has a CreateFolder with a > permissionsEx nexted in it. > > An example... > > > > Action="write" Value="1" Root="HKLM" Key="$(var.RegistryPath)" > Name="windowstempfolderpermissions" KeyPath="yes"/> > > Domain="[ComputerName]" /> > > > > > -Original Message- > From: CoolBreeze [mailto:coolbreeze...@googlemail.com] > Sent: 13 June 2011 17:28 > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Help with giving permissions to folder > > My installer needs to encrypt the ConnectionStrings section of the > web.config file for our web application. This part I have working with no > problems, but as part of the process I need to provide the Network Service > with full control access to the following folder: > > *C:\Documents and Settings\All Users\Application > Data\Microsoft\Crypto\RSA\MachineKeys* > > I have not been able to figure out how to configure this with in my > installer. > > I've tried adding the following to my Product.wxs, but it gives a build > error of: "The Directory element contains an unexpected child element > 'util:PermissionEx'.". And xmlns:util has been added to the beginning of my > Product.wxs. > > > > > > > > > > > ChangePermission="yes" /> > > > > > > > > > How can this be done? > > - > - > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > SDL PLC confidential, all rights reserved. > If you are not the intended recipient of this mail SDL requests and > requires that you delete it without acting upon or copying any of its > contents, and we further request that you advise us. > SDL PLC is a public limited company registered in England and Wales. > Registered number: 02675207. > Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 > 7DY, UK. > > > > -- > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Help with giving permissions to folder
The relevant parent of util:permissionex is createfolder. Put a component in your directory tree that has a CreateFolder with a permissionsEx nexted in it. An example... -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: 13 June 2011 17:28 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Help with giving permissions to folder My installer needs to encrypt the ConnectionStrings section of the web.config file for our web application. This part I have working with no problems, but as part of the process I need to provide the Network Service with full control access to the following folder: *C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys* I have not been able to figure out how to configure this with in my installer. I've tried adding the following to my Product.wxs, but it gives a build error of: "The Directory element contains an unexpected child element 'util:PermissionEx'.". And xmlns:util has been added to the beginning of my Product.wxs. How can this be done? - - EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
