Re: [WiX-users] Turoial for Burn
Thank you -Ursprüngliche Nachricht- Von: Rob Mensching [mailto:r...@robmensching.com] Gesendet: Mittwoch, 25. Mai 2011 10:54 An: General discussion for Windows Installer XML toolset. Betreff: Re: [WiX-users] Turoial for Burn WiX.chm has walk through for some basics. On Wed, May 4, 2011 at 1:36 AM, Christoph Goetz christoph.go...@giepa.dewrote: Hello, do you know if there is a tutorial for Burn Just some examples for all the commands. Thanks in advance, Christoph -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 ___ 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 featureisinADDLOCAL
I did indeed retain the code. Since nothing has changed except the internals of the two files, both heat-generated .wxs are identical. I'm glad to hear that it looks OK since I was worried I had made some obvious embaressing mistake... that said, it's quite unsettling that you can't find any problem. I've had SO many issues with Wix and I think my boss is getting less and less happy that I chose Wix for our development. While Major Upgrades are working well, I've been trying to get some form of MSP system to work for ages now and it just refuses to work. First I had major issues with the SqlExtension where SQL refused to run during MSPs. I never got that to work and I'm currently using a CAQuietExec to run sqlcmd instead. (At that point in time, the MSP actually did update files though). Now this. I'm on the verge of thinking that coding a whole installer myself in C# would have been easier and faster. On Tue, Jun 14, 2011 at 2:06 PM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: 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: Patch AllowRemoval=yes Manufacturer=Syscase DisplayName=Test Patch Description=Small Update Patch Classification=Update Media Id=5000 Cabinet=Sample.cab PatchBaseline Id=Sample/ /Media PatchFamilyRef Id=SamplePatchFamily/ /Patch Fragment PatchFamily Id='SamplePatchFamily' Version='5.1.0.0' Supersede='yes' ComponentRef Id=cmp432C3967A6AA13C06D8D1E0E95348403/ ComponentRef Id=cmpTestsql/ CustomActionRef Id=sqlcmd.cmd / /PatchFamily /Fragment The components are defined in a .wxs created by heat, something like this: Fragment DirectoryRef Id=INSTALLDIR Directory Id=dirFC51653BB9D6AD82C52CC25E1257C927 Name=readme Component Id=cmp432C3967A6AA13C06D8D1E0E95348403 Guid=84E0BEA1-95DA-4D37-A838-EAB8D0556A75 File Id=filFBC7318D3D0A5C9BDF1AE0C50DB2AF45 KeyPath=yes Source=SourceDir\..\Files\readme.txt / /Component /Directory Component Id=cmpTestsql Guid=58BE1C34-46EE-4AC0-98C4-58DF2C4726CF File Id=filTestSql KeyPath=yes Source=SourceDir\..\Files\Test.sql / /Component /DirectoryRef /Fragment Fragment ComponentGroup Id=NewFilesGroup ComponentRef Id=cmp432C3967A6AA13C06D8D1E0E95348403 / ComponentRef Id=cmpTestsql / /ComponentGroup /Fragment 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 pshirtcli...@sdl.comwrote: 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 pshirtcli...@sdl.comwrote: 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
Re: [WiX-users] Component Request: null eventhough parentfeatureisinADDLOCAL
That's a shame. We are currently struggling with a C#-based installation product written in-house by another team so we've seen how trading for short-term control yields long-term problems. Since we adopted Wix some years ago, which admittedly has a big learning curve mostly due to the underlying Windows Installer, the deployment side of our products has improved substantially. Getting the first version out is the hardest, but later versions get easier. Have a quick look at your build. We make our patches from admin installations rather than the full Wix-only method - if youre using the pure-Wix method then it'll differ somewhat. These are the command lines, taken from an MSBuild file used to build them. Maybe you can glean something from them. !-- Uses -ax (admin) instead of -xi (xml input) and add -xo when using -ax. -- torch.exe -t patch -xo -ax $(WorkingDir)\Binaries -p $(WorkingDir)\Release\$(MSIName) $(WorkingDir)\Update\$(MSIName) -out $(WorkingDir)\Diff.Wixmst candle.exe $(MSBuildProjectDirectory)\Patch.wxs -out $(WorkingDir)\Patch.wixobj light.exe $(WorkingDir)\Patch.wixobj -out $(WorkingDir)\Patch.WixMsp pyro.exe $(WorkingDir)\Patch.WixMsp -out $(MSBuildProjectDirectory)\$(PatchName) -pdbout $(WorkingDir)\$(PatchName).wixpdb -t $(Baseline) $(WorkingDir)\Diff.wixmst ! Note that the $(BaseLine) value must be the same as PatchBaseLine/@Id value in the patch wxs file. After checking your build I'd suggest two things that help me: trying and make a simple 1 file installer and patch. If that doesn't work then you have narrowed your search down. If it does work then you've verified that you are doing the right thing and just have to find where you didn't do it in the product. The other thing is to look at other patch logs and see what a successful patch looks like and where your log differs. The answer is nearly always there if only you know what to look for. Perhaps someone on here with better knowledge of patching can suggest where to look in the log, given the information so far. -Original Message- From: Tobberoth [mailto:tobber...@gmail.com] Sent: 15 June 2011 09:01 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Component Request: null eventhough parentfeatureisinADDLOCAL I did indeed retain the code. Since nothing has changed except the internals of the two files, both heat-generated .wxs are identical. I'm glad to hear that it looks OK since I was worried I had made some obvious embaressing mistake... that said, it's quite unsettling that you can't find any problem. I've had SO many issues with Wix and I think my boss is getting less and less happy that I chose Wix for our development. While Major Upgrades are working well, I've been trying to get some form of MSP system to work for ages now and it just refuses to work. First I had major issues with the SqlExtension where SQL refused to run during MSPs. I never got that to work and I'm currently using a CAQuietExec to run sqlcmd instead. (At that point in time, the MSP actually did update files though). Now this. I'm on the verge of thinking that coding a whole installer myself in C# would have been easier and faster. On Tue, Jun 14, 2011 at 2:06 PM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: 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: Patch AllowRemoval=yes Manufacturer=Syscase DisplayName=Test Patch Description=Small Update Patch Classification=Update Media Id=5000 Cabinet=Sample.cab PatchBaseline Id=Sample/ /Media PatchFamilyRef Id=SamplePatchFamily/ /Patch Fragment PatchFamily Id='SamplePatchFamily' Version='5.1.0.0' Supersede='yes' ComponentRef Id=cmp432C3967A6AA13C06D8D1E0E95348403/ ComponentRef Id=cmpTestsql/ CustomActionRef Id=sqlcmd.cmd / /PatchFamily /Fragment The components are defined in a .wxs created by heat, something like this: Fragment DirectoryRef Id=INSTALLDIR Directory Id=dirFC51653BB9D6AD82C52CC25E1257C927 Name=readme Component Id=cmp432C3967A6AA13C06D8D1E0E95348403 Guid=84E0BEA1-95DA-4D37-A838-EAB8D0556A75 File Id=filFBC7318D3D0A5C9BDF1AE0C50DB2AF45 KeyPath=yes Source=SourceDir\..\Files\readme.txt / /Component /Directory Component Id=cmpTestsql Guid=58BE1C34-46EE-4AC0-98C4-58DF2C4726CF
[WiX-users] conditional install based on contents of SQL table
Hello, I'd like to place a check in an install that confirms the version of the application's database. This info is stored in a versions table. The rationale is I'd only like install to go ahead once the database has been updated, but I want to keep this process separate from the installation. The application search functionality seems to be in the right area, but this only applies to files, directories and COM components as far as I can tell. I realise it is straightforward enough to include a SQL script and have the installer make the change, but that's not appropriate in this case. Would someone be kind enough to point me in the right direction? Thanks, Stu -- 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] InstallAware Help...
Make a major upgrade of your existing MSI. There's a help topic in the Wix help file called How To: Implement a Major Upgrade In Your Installer. Find the Upgrade Code from the previous installer and set it in your new installer. Make sure your new version number is higher than the old one. The product codes should be different too. You can use a Wix command line tool called dark.exe to convert the old MSI to Wix, although it's not always as clean as writing one from scratch. -Original Message- From: Tomer Cohen [mailto:tome...@qualisystems.com] Sent: 15 June 2011 06:44 To: wix-users@lists.sourceforge.net Subject: [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 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
Re: [WiX-users] Help with giving permissions to folder
http://msdn.microsoft.com/en-us/library/aa370905(VS.85).aspx AppDataFolder is for the current user. CommonAppDataFolder is for all users. -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: 14 June 2011 18:22 To: General discussion for Windows Installer XML toolset. Subject: 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 dwat...@sdl.com wrote: Either take it out of the fragment or use a DirectoryRef. Fragment DirectoryRef Id=TARGETDIR Directory Id=AppDataFolder Directory Id=dir6A68E13632B544EDA8F393F83B23F439 Name=Microsoft Directory Id=dir03FB174C3B8F4214AF6A130B8EAA7BA1 Name=Crypto Directory Id=dirE956646E44EE4A23B07BD0A84D969F55 Name=RSA Directory Id=dir9210B4F4F4A24357A3954AFC771C9E28 Name=MachineKeys Component Id=MachineKeysFolderPermissions Guid=352963FCB3794D8E9B9BE725929B5C47 CreateFolder util:PermissionEx User=NETWORK SERVICE GenericAll=yes ChangePermission=yes / /CreateFolder /Component /Directory /Directory /Directory /Directory /Directory /DirectoryRef /Fragment 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 dwat...@sdl.com 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 Fragment Directory Id=TARGETDIR Name=SourceDir Directory Id=AppDataFolder Directory Id=dir6A68E13632B544EDA8F393F83B23F439 Name=Microsoft Directory Id=dir03FB174C3B8F4214AF6A130B8EAA7BA1 Name=Crypto Directory Id=dirE956646E44EE4A23B07BD0A84D969F55 Name=RSA Directory Id=dir9210B4F4F4A24357A3954AFC771C9E28 Name=MachineKeys Component Id=MachineKeysFolderPermissions Guid=352963FCB3794D8E9B9BE725929B5C47 CreateFolder util:PermissionEx User=NETWORK SERVICE GenericAll=yes ChangePermission=yes /
Re: [WiX-users] logging
Hi Dave, Thank you for this link. I have been trying to implement it into my calls, but sadly it does not seem to work. I have tried the redirecting with a simple cmd call and it works fine. However I am creating an automation process using autoit, and im not sure if I would be using the redirection correctly. Autoit script: RunWait($WIX_FOLDER '\candle.exe myfile.txt -dmanufacturer='$MANUFACTURER_NAME' -dproductName='$productName' -dcabName='$CABINET_NAME'.cab -dcodepage='$wixInitLcidCode' -dproductGUID='$productCode' -out '$BUILD_FOLDER'\ '$BUILD_FOLDER'\*.wxs',$BUILD_FOLDER,@SW_MAXIMIZE) If anyone could point me in the right direction I would be incredibly grateful. Thanks! David Amey The Creative Engine Ltd Almac House, Church Lane, Bisley, Surrey, GU24 9DR T: +44 (0)1483 799200 F: +44 (0)1483 799111 -Original Message- From: Dave Andersen [mailto:d.ander...@gmail.com] Sent: 14 June 2011 19:28 To: wix-users@lists.sourceforge.net Subject: 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 -- 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
[WiX-users] XmlConfig in multiple MergeModules
Hello,
I was wondering if it is possible to use XmlConfig in multiple merge modules,
that will later be used in a single installer.
For example, I have MergeModule1, which has:
Fragment
Component Id=appConfigEdit Guid={1F53A85E-07AD-47B5-890E-D6768A65E343}
Directory=MANAGEMENTTOOLFOLDER KeyPath=yes
util:XmlConfig Id='Modules'
On='install'
Action='create'
Sequence='1'
File='[#appConfigFile]'
ElementPath=//configuration/appSettings/add[\[]@key='Modules'[\]]
Node=value
Name=value
Value='[MODULES]'/
util:XmlConfig Id='ConnectorServiceRelativePathDefinition'
On='install'
Action='create'
Sequence='2'
File='[#appConfigFile]'
ElementPath=//configuration/appSettings/add[\[]@key='ConnectorServiceFolderName'[\]]
Node=value
Name=value
Value='..\!(loc.ConnectorFolderName)'/
/Component
/Fragment
MergeModule2 has the following Component:
Fragment
Component Id=appConfigEditing
Guid={BC70F9B6-6CE1-4C49-8AB3-F7C36B616129} Directory=CONNECTORFOLDER
KeyPath=yes
util:XmlConfig Id='ModulesDefinition'
On='install'
Action='create'
Sequence='1'
File='[#file_E1F5BC4046FD48ADB558DE10AA3F4B50]'
ElementPath=//configuration/appSettings/add[\[]@key='Modules'[\]]
Node=value
Name=value
Value='[MODULES]'/
util:XmlConfig Id='GcwaRelativePathDefinition'
On='install'
Action='create'
Sequence='2'
File='[#file_E1F5BC4046FD48ADB558DE10AA3F4B50]'
ElementPath=//configuration/appSettings/add[\[]@key='PrivateApiFileServerRelativePath'[\]]
Node=value
Name=value
Value='..\!(loc.GcwaFolderNme)'/
/Component
/Fragment
This doesn't seem to work when I use both merge modules in an installer, and I
get a warning when compiling:
warning LGHT1055: The InstallExecuteSequence table contains an action
'SchedXmlConfig' which cannot be merged from the merge module 'blah'. This
action is likely colliding with an action in the database that is being
created. The colliding action may have been authored in the database or merged
in from another merge module. If this is a standard action, it is likely
colliding due to a difference in the condition for the action in the database
and merge module. If this is a custom action, it should only be declared in
the database or one merge module.
warning LGHT1056: The CustomAction table contains a row with primary key(s)
'SchedXmlConfig' which cannot be merged from the merge module 'blah'. This is
likely due to collision of rows with the same primary key(s) (but other
different values in other columns) between the database and the merge module.
warning LGHT1056: The CustomAction table contains a row with primary key(s)
'ExecXmlConfig' which cannot be merged from the merge module 'blah'. This is
likely due to collision of rows with the same primary key(s) (but other
different values in other columns) between the database and the merge module.
warning LGHT1056: The CustomAction table contains a row with primary key(s)
'ExecXmlConfigRollback' which cannot be merged from the merge module 'blah'.
This is likely due to collision of rows with the same primary key(s) (but other
different values in other columns) between the database and the merge module.
Obviously, when I try to install I get an error saying:
SchedXmlConfig: Error 0x8007007a: failed to copy XmlConfig record Id
SchedXmlConfig: Error 0x8007007a: failed to read XmlConfig table
Error 25540. There was a failure while configuring XML files.
Any tips on how to resolve this? It's far easier to have the configuration
within the merge module instead of the installer, since the MM's are used in
multiple installers, and would not like to add the XmlConfig in every single
installer if I can define it once in the MM and know that it will apply
anywhere it's used
Thanks,
Stel
This message is confidential and may be privileged. It is intended solely for
the named addressee. If you are not the intended recipient, please inform us.
Any unauthorised dissemination, distribution or copying hereof is prohibited.
Formicary Limited registered office in England and Wales, address 1 Taillar
Road, Hedon, East Yorkshire HU12 8GU, registration number 3894343, VAT number
747644304, does not guarantee that the integrity of this communication has been
maintained nor that this
Re: [WiX-users] Help with giving permissions to folder
Thanks Peter. As I've explained previously though each time I run the installer the installation files are installed into one location, then before the installer ends I need to have Network Service added to the MachineKeys folder. After the installer completes and I navigate to the following folder to verify that Network Service has been added with the permissions specified it is not there. C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys I thought Wix was able to perform a task such as this. Am I incorrect? This one piece has me stuck and I'm not sure how to resolve it. On Wed, Jun 15, 2011 at 5:09 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: http://msdn.microsoft.com/en-us/library/aa370905(VS.85).aspx AppDataFolder is for the current user. CommonAppDataFolder is for all users. -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: 14 June 2011 18:22 To: General discussion for Windows Installer XML toolset. Subject: 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 dwat...@sdl.com wrote: Either take it out of the fragment or use a DirectoryRef. Fragment DirectoryRef Id=TARGETDIR Directory Id=AppDataFolder Directory Id=dir6A68E13632B544EDA8F393F83B23F439 Name=Microsoft Directory Id=dir03FB174C3B8F4214AF6A130B8EAA7BA1 Name=Crypto Directory Id=dirE956646E44EE4A23B07BD0A84D969F55 Name=RSA Directory Id=dir9210B4F4F4A24357A3954AFC771C9E28 Name=MachineKeys Component Id=MachineKeysFolderPermissions Guid=352963FCB3794D8E9B9BE725929B5C47 CreateFolder util:PermissionEx User=NETWORK SERVICE GenericAll=yes ChangePermission=yes / /CreateFolder /Component /Directory /Directory /Directory /Directory /Directory /DirectoryRef /Fragment 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 dwat...@sdl.com 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
Re: [WiX-users] Help with giving permissions to folder
As Pete says, you are using the wrong directory ID use CommonAppDataFolder in place of AppDataFolder in your Directory. -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: 15 June 2011 14:46 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Help with giving permissions to folder Thanks Peter. As I've explained previously though each time I run the installer the installation files are installed into one location, then before the installer ends I need to have Network Service added to the MachineKeys folder. After the installer completes and I navigate to the following folder to verify that Network Service has been added with the permissions specified it is not there. C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys I thought Wix was able to perform a task such as this. Am I incorrect? This one piece has me stuck and I'm not sure how to resolve it. On Wed, Jun 15, 2011 at 5:09 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: http://msdn.microsoft.com/en-us/library/aa370905(VS.85).aspx AppDataFolder is for the current user. CommonAppDataFolder is for all users. -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: 14 June 2011 18:22 To: General discussion for Windows Installer XML toolset. Subject: 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 dwat...@sdl.com wrote: Either take it out of the fragment or use a DirectoryRef. Fragment DirectoryRef Id=TARGETDIR Directory Id=AppDataFolder Directory Id=dir6A68E13632B544EDA8F393F83B23F439 Name=Microsoft Directory Id=dir03FB174C3B8F4214AF6A130B8EAA7BA1 Name=Crypto Directory Id=dirE956646E44EE4A23B07BD0A84D969F55 Name=RSA Directory Id=dir9210B4F4F4A24357A3954AFC771C9E28 Name=MachineKeys Component Id=MachineKeysFolderPermissions Guid=352963FCB3794D8E9B9BE725929B5C47 CreateFolder util:PermissionEx User=NETWORK SERVICE GenericAll=yes ChangePermission=yes / /CreateFolder /Component /Directory /Directory /Directory /Directory /Directory /DirectoryRef /Fragment 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 dwat...@sdl.com 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
Re: [WiX-users] Help with giving permissions to folder
I already made that change. I ran the installer with logging turned on and saw where it executed my two CustomActions and the installation completed fine. It's just that Network Service never gets added to the MachineKeys folder nor are any permissions set in the folder. MSI (s) (58:A4) [10:34:24:193]: Doing action: CA_AclPermissions Action 10:34:24: CA_AclPermissions. Action start 10:34:24: CA_AclPermissions. Action ended 10:34:24: CA_AclPermissions. Return value 1. MSI (s) (58:A4) [10:34:24:383]: Doing action: CA_EncryptConnString Action 10:34:24: CA_EncryptConnString. Action start 10:34:24: CA_EncryptConnString. Action ended 10:34:27: CA_EncryptConnString. Return value 1. On Wed, Jun 15, 2011 at 10:04 AM, David Watson dwat...@sdl.com wrote: As Pete says, you are using the wrong directory ID use CommonAppDataFolder in place of AppDataFolder in your Directory. -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: 15 June 2011 14:46 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Help with giving permissions to folder Thanks Peter. As I've explained previously though each time I run the installer the installation files are installed into one location, then before the installer ends I need to have Network Service added to the MachineKeys folder. After the installer completes and I navigate to the following folder to verify that Network Service has been added with the permissions specified it is not there. C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys I thought Wix was able to perform a task such as this. Am I incorrect? This one piece has me stuck and I'm not sure how to resolve it. On Wed, Jun 15, 2011 at 5:09 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: http://msdn.microsoft.com/en-us/library/aa370905(VS.85).aspx AppDataFolder is for the current user. CommonAppDataFolder is for all users. -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: 14 June 2011 18:22 To: General discussion for Windows Installer XML toolset. Subject: 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 dwat...@sdl.com wrote: Either take it out of the fragment or use a DirectoryRef. Fragment DirectoryRef Id=TARGETDIR Directory Id=AppDataFolder Directory Id=dir6A68E13632B544EDA8F393F83B23F439 Name=Microsoft Directory Id=dir03FB174C3B8F4214AF6A130B8EAA7BA1 Name=Crypto Directory Id=dirE956646E44EE4A23B07BD0A84D969F55 Name=RSA Directory Id=dir9210B4F4F4A24357A3954AFC771C9E28 Name=MachineKeys Component Id=MachineKeysFolderPermissions Guid=352963FCB3794D8E9B9BE725929B5C47 CreateFolder util:PermissionEx User=NETWORK SERVICE GenericAll=yes ChangePermission=yes / /CreateFolder /Component /Directory /Directory /Directory /Directory /Directory /DirectoryRef /Fragment 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
[WiX-users] Custom dialogs in wix 3.5?
I'm just now migrating a wix project from wix 3.0 to wix 3.5. My 3.0 project had a customization of InstallDirDlg.wxs to allow the user to decline creation of a desktop icon. To add this customization required modification of the InstallDirDlg.wxs file that was part of the wix 3.0 source. It seems that source for 3.5 is not available (or I can't find it). How can I move to 3.5 and still have a checkbox to disable creation of a desktop icon? -- 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
Hi David, I am not expert in candle and light but I believe that redirection in DOS should happen at the end of the line: RunWait($WIX_FOLDER '\candle.exe -dmanufacturer='$MANUFACTURER_NAME' -dproductName='$productName' -dcabName='$CABINET_NAME'.cab -dcodepage='$wixInitLcidCode' -dproductGUID='$productCode' -out '$BUILD_FOLDER'\ '$BUILD_FOLDER'\*.wxs myfile.txt ',$BUILD_FOLDER,@SW_MAXIMIZE) Martin Kulov -Original Message- From: David Amey [mailto:da...@creative-engine.co.uk] Sent: Wednesday, June 15, 2011 12:17 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] logging Hi Dave, Thank you for this link. I have been trying to implement it into my calls, but sadly it does not seem to work. I have tried the redirecting with a simple cmd call and it works fine. However I am creating an automation process using autoit, and im not sure if I would be using the redirection correctly. Autoit script: RunWait($WIX_FOLDER '\candle.exe myfile.txt -dmanufacturer='$MANUFACTURER_NAME' -dproductName='$productName' -dcabName='$CABINET_NAME'.cab -dcodepage='$wixInitLcidCode' -dproductGUID='$productCode' -out '$BUILD_FOLDER'\ '$BUILD_FOLDER'\*.wxs',$BUILD_FOLDER,@SW_MAXIMIZE) If anyone could point me in the right direction I would be incredibly grateful. Thanks! David Amey The Creative Engine Ltd Almac House, Church Lane, Bisley, Surrey, GU24 9DR T: +44 (0)1483 799200 F: +44 (0)1483 799111 -Original Message- From: Dave Andersen [mailto:d.ander...@gmail.com] Sent: 14 June 2011 19:28 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] logging Something like this may help: http://blog.crankybit.com/redirecting-output-to-a-file-in-windows-batch-scri pts/ 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-tp6474 846p6475377.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 -- 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
[WiX-users] Security/Access to use Wix from IIS
I'm looking at using the WiX toolkit to build an MSI from a Webpate. Our current solution, which uses a script executed by the windows cscript command, requires elevated permissions. On some systems, especially Windows 2008 R2, this causes some problems. What I'm wondering is, will WiX be an ideal solution? I need to basically build an MSI that launches an embedded EXE. Each time it's downloaded, the MSI will need to be re-generated since the EXE contains time-sensitive data. Will I need elevated admin rights to do the above? I know my scenario is pretty general, if you need more details, please let me know. Thanks R. Scott -- 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
This is what I do CreateFolder Permission User=[SID_BUILTIN_USERS] GenericAll=yes / /CreateFolder Along with SIDLookup merge module so that the all the well know SIDs language natural -- 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] XmlConfig in multiple MergeModules
Figured this out. It was as simple as reducing the length an XmlConfig Id
('ConnectorServiceRelativePathDefinition') which was too long to handle
-Original Message-
From: Stelios Kyprou [mailto:stelios.kyp...@formicary.net]
Sent: 15 June 2011 12:35
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] XmlConfig in multiple MergeModules
Hello,
I was wondering if it is possible to use XmlConfig in multiple merge modules,
that will later be used in a single installer.
For example, I have MergeModule1, which has:
Fragment
Component Id=appConfigEdit Guid={1F53A85E-07AD-47B5-890E-
D6768A65E343} Directory=MANAGEMENTTOOLFOLDER KeyPath=yes
util:XmlConfig Id='Modules'
On='install'
Action='create'
Sequence='1'
File='[#appConfigFile]'
ElementPath=//configuration/appSettings/add[\[]@key='Modules'[\]]
Node=value
Name=value
Value='[MODULES]'/
util:XmlConfig Id='ConnectorServiceRelativePathDefinition'
On='install'
Action='create'
Sequence='2'
File='[#appConfigFile]'
ElementPath=//configuration/appSettings/add[\[]@key='ConnectorService
FolderName'[\]]
Node=value
Name=value
Value='..\!(loc.ConnectorFolderName)'/
/Component
/Fragment
MergeModule2 has the following Component:
Fragment
Component Id=appConfigEditing Guid={BC70F9B6-6CE1-4C49-8AB3-
F7C36B616129} Directory=CONNECTORFOLDER KeyPath=yes
util:XmlConfig Id='ModulesDefinition'
On='install'
Action='create'
Sequence='1'
File='[#file_E1F5BC4046FD48ADB558DE10AA3F4B50]'
ElementPath=//configuration/appSettings/add[\[]@key='Modules'[\]]
Node=value
Name=value
Value='[MODULES]'/
util:XmlConfig Id='GcwaRelativePathDefinition'
On='install'
Action='create'
Sequence='2'
File='[#file_E1F5BC4046FD48ADB558DE10AA3F4B50]'
ElementPath=//configuration/appSettings/add[\[]@key='PrivateApiFileSer
verRelativePath'[\]]
Node=value
Name=value
Value='..\!(loc.GcwaFolderNme)'/
/Component
/Fragment
This doesn't seem to work when I use both merge modules in an installer,
and I get a warning when compiling:
warning LGHT1055: The InstallExecuteSequence table contains an action
'SchedXmlConfig' which cannot be merged from the merge module 'blah'.
This action is likely colliding with an action in the database that is being
created. The colliding action may have been authored in the database or
merged in from another merge module. If this is a standard action, it is
likely
colliding due to a difference in the condition for the action in the database
and merge module. If this is a custom action, it should only be declared in
the database or one merge module.
warning LGHT1056: The CustomAction table contains a row with primary
key(s) 'SchedXmlConfig' which cannot be merged from the merge module
'blah'. This is likely due to collision of rows with the same primary key(s)
(but
other different values in other columns) between the database and the
merge module.
warning LGHT1056: The CustomAction table contains a row with primary
key(s) 'ExecXmlConfig' which cannot be merged from the merge module
'blah'. This is likely due to collision of rows with the same primary key(s)
(but
other different values in other columns) between the database and the
merge module.
warning LGHT1056: The CustomAction table contains a row with primary
key(s) 'ExecXmlConfigRollback' which cannot be merged from the merge
module 'blah'. This is likely due to collision of rows with the same primary
key(s) (but other different values in other columns) between the database
and the merge module.
Obviously, when I try to install I get an error saying:
SchedXmlConfig: Error 0x8007007a: failed to copy XmlConfig record Id
SchedXmlConfig: Error 0x8007007a: failed to read XmlConfig table Error
25540. There was a failure while configuring XML files.
Any tips on how to resolve this? It's far easier to have the configuration
within the merge module instead of the installer, since the MM's are used in
multiple installers, and would not like to add the XmlConfig in every single
installer if I can define it once in the MM and know that it will apply
anywhere
it's used
Thanks,
Stel
This message is confidential and may be privileged. It is intended solely for
the named addressee. If you are not the intended recipient,
Re: [WiX-users] Help with giving permissions to folder
The following works, I just tried it. Directory Id=CommonAppDataFolder Directory Id=Microsoft Name=Microsoft Directory Id=Crypto Name=Crypto Directory Id=RSA Name=RSA Directory Id=MachineKeys Name=MachineKeys Component Id=MachineKeysFolderPermissions Guid=352963FCB3794D8E9B9BE725929B5C47 CreateFolder util:PermissionEx User=NetworkService GenericAll=yes / /CreateFolder /Component /Directory /Directory /Directory /Directory /Directory -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: 15 June 2011 15:49 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Help with giving permissions to folder I already made that change. I ran the installer with logging turned on and saw where it executed my two CustomActions and the installation completed fine. It's just that Network Service never gets added to the MachineKeys folder nor are any permissions set in the folder. MSI (s) (58:A4) [10:34:24:193]: Doing action: CA_AclPermissions Action 10:34:24: CA_AclPermissions. Action start 10:34:24: CA_AclPermissions. Action ended 10:34:24: CA_AclPermissions. Return value 1. MSI (s) (58:A4) [10:34:24:383]: Doing action: CA_EncryptConnString Action 10:34:24: CA_EncryptConnString. Action start 10:34:24: CA_EncryptConnString. Action ended 10:34:27: CA_EncryptConnString. Return value 1. On Wed, Jun 15, 2011 at 10:04 AM, David Watson dwat...@sdl.com wrote: As Pete says, you are using the wrong directory ID use CommonAppDataFolder in place of AppDataFolder in your Directory. -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: 15 June 2011 14:46 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Help with giving permissions to folder Thanks Peter. As I've explained previously though each time I run the installer the installation files are installed into one location, then before the installer ends I need to have Network Service added to the MachineKeys folder. After the installer completes and I navigate to the following folder to verify that Network Service has been added with the permissions specified it is not there. C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys I thought Wix was able to perform a task such as this. Am I incorrect? This one piece has me stuck and I'm not sure how to resolve it. On Wed, Jun 15, 2011 at 5:09 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: http://msdn.microsoft.com/en-us/library/aa370905(VS.85).aspx AppDataFolder is for the current user. CommonAppDataFolder is for all users. -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: 14 June 2011 18:22 To: General discussion for Windows Installer XML toolset. Subject: 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 dwat...@sdl.com wrote: Either take it out of the fragment or use a DirectoryRef. Fragment DirectoryRef Id=TARGETDIR Directory Id=AppDataFolder Directory Id=dir6A68E13632B544EDA8F393F83B23F439 Name=Microsoft Directory Id=dir03FB174C3B8F4214AF6A130B8EAA7BA1 Name=Crypto Directory Id=dirE956646E44EE4A23B07BD0A84D969F55 Name=RSA Directory Id=dir9210B4F4F4A24357A3954AFC771C9E28 Name=MachineKeys Component Id=MachineKeysFolderPermissions Guid=352963FCB3794D8E9B9BE725929B5C47 CreateFolder util:PermissionEx User=NETWORK SERVICE GenericAll=yes ChangePermission=yes / /CreateFolder /Component /Directory /Directory /Directory /Directory /Directory /DirectoryRef /Fragment 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
Re: [WiX-users] Custom dialogs in wix 3.5?
On Wed, 15 Jun 2011 07:54:43 -0700 Nuno Romao nro...@gmail.com wrote: I'm just now migrating a wix project from wix 3.0 to wix 3.5. My 3.0 project had a customization of InstallDirDlg.wxs to allow the user to decline creation of a desktop icon. To add this customization required modification of the InstallDirDlg.wxs file that was part of the wix 3.0 source. It seems that source for 3.5 is not available (or I can't find it). How can I move to 3.5 and still have a checkbox to disable creation of a desktop icon? The code for WiX 3.5 can be found at http://wix.codeplex.com/SourceControl/list/changesets?branch=wix35 . By the way I think Microsoft recommends a desktop icon not be created by default. -- Bruce Cran -- 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
True this does create the folder at the root of C:\ and adds the Network Service user with the proper permissions. What I'm am trying to do though is add the Network Service user with the permissions specified to the EXISTING MachineKeys folder located at: C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys. I'm not trying to create a new folder just add the user to the existing folder along with permissions. On Wed, Jun 15, 2011 at 11:34 AM, David Watson dwat...@sdl.com wrote: The following works, I just tried it. Directory Id=CommonAppDataFolder Directory Id=Microsoft Name=Microsoft Directory Id=Crypto Name=Crypto Directory Id=RSA Name=RSA Directory Id=MachineKeys Name=MachineKeys Component Id=MachineKeysFolderPermissions Guid=352963FCB3794D8E9B9BE725929B5C47 CreateFolder util:PermissionEx User=NetworkService GenericAll=yes / /CreateFolder /Component /Directory /Directory /Directory /Directory /Directory -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: 15 June 2011 15:49 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Help with giving permissions to folder I already made that change. I ran the installer with logging turned on and saw where it executed my two CustomActions and the installation completed fine. It's just that Network Service never gets added to the MachineKeys folder nor are any permissions set in the folder. MSI (s) (58:A4) [10:34:24:193]: Doing action: CA_AclPermissions Action 10:34:24: CA_AclPermissions. Action start 10:34:24: CA_AclPermissions. Action ended 10:34:24: CA_AclPermissions. Return value 1. MSI (s) (58:A4) [10:34:24:383]: Doing action: CA_EncryptConnString Action 10:34:24: CA_EncryptConnString. Action start 10:34:24: CA_EncryptConnString. Action ended 10:34:27: CA_EncryptConnString. Return value 1. On Wed, Jun 15, 2011 at 10:04 AM, David Watson dwat...@sdl.com wrote: As Pete says, you are using the wrong directory ID use CommonAppDataFolder in place of AppDataFolder in your Directory. -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: 15 June 2011 14:46 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Help with giving permissions to folder Thanks Peter. As I've explained previously though each time I run the installer the installation files are installed into one location, then before the installer ends I need to have Network Service added to the MachineKeys folder. After the installer completes and I navigate to the following folder to verify that Network Service has been added with the permissions specified it is not there. C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys I thought Wix was able to perform a task such as this. Am I incorrect? This one piece has me stuck and I'm not sure how to resolve it. On Wed, Jun 15, 2011 at 5:09 AM, Peter Shirtcliffe pshirtcli...@sdl.comwrote: http://msdn.microsoft.com/en-us/library/aa370905(VS.85).aspx AppDataFolder is for the current user. CommonAppDataFolder is for all users. -Original Message- From: CoolBreeze [mailto:coolbreeze...@googlemail.com] Sent: 14 June 2011 18:22 To: General discussion for Windows Installer XML toolset. Subject: 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 dwat...@sdl.com wrote: Either take it out of the fragment or use a DirectoryRef. Fragment DirectoryRef Id=TARGETDIR Directory Id=AppDataFolder Directory Id=dir6A68E13632B544EDA8F393F83B23F439 Name=Microsoft Directory Id=dir03FB174C3B8F4214AF6A130B8EAA7BA1 Name=Crypto Directory Id=dirE956646E44EE4A23B07BD0A84D969F55 Name=RSA Directory Id=dir9210B4F4F4A24357A3954AFC771C9E28
[WiX-users] Error 2623
I think somebody a while back reported an undocumented error 2623 during an install. I just came across this error if anyone is still interested. It turned out to be: DEBUG: Error 2623: Calling ScheduleReboot from a multi-package transaction is not supported. This restriction is documented in MSDN Multiple Package Installations but that error number is still invisible. Phil Wilson 949-639-1680 *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77nav_id=80prev_id=77. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- 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
[WiX-users] .Net pre-requisite check when using Managed Bootstrapper application in Burn
Hi, I plan to use a managed bootstrapper application that instantiates a WPF UI to use with Burn chainer. I'd like to block users and provide a custom error message if they don't have .Net 4.0 installed. I have two questions on this - 1. Given that my bootstrapper itself depends on .Net 4.0, how can I implement this check? 2. Currently, I get this message in the logs when I run such a installer on a machine with no .Net installed - Loading prerequisite bootstrapper application because managed host could not be loaded, error: 0x80070490. Error 0x80070490: Failed to read the NETFX Package identifier from engine variable. Error 0x80070490: Failed to start bootstrapper application. The prerequisites were not successfully installed, error: 0x0. The bootstrapper application will be not reloaded. Error 0x80070490: Failed while running Error 0x80070490: Failed to run per-user mode. Is there a way I can add a custom message to the log in case there is no .Net installed on the machine? I'd really appreciate any pointers in this regard. Thanks, Shruthi -- 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
