Re: [WiX-users] Latest build - specifically MSMQ extension
Both files have 5/10 as time stamps on my machine. In an earlier release (2 weeks ago or so) I had problems with the strong names too. After installing the latest build using the .msi (not the zip) it's now working again. Best regards, Sebastian Brand Instyler Software - http://www.instyler.com On Oct 16, 2007, at 5:24 PM, Vaclav Haken wrote: One question though, I am having public key mismatch for wix.dll vs dark.exe, funnily enough their datetime stamps are differnent 5/10 vs 13/9. Tried to force .net framework to skip verification for these but to no success. Are you using those builds? Vaclav On 10/16/07, Vaclav Haken [EMAIL PROTECTED] wrote: I realized that only seconds after posting my message (deleted already). Thanks for reply though. Vaclav On 10/16/07, Sebastian Brand [EMAIL PROTECTED] wrote: The weekly release can be downloaded here: http://wix.sourceforge.net/releases/ Best regards, Sebastian Brand Instyler Software - http://www.instyler.com On Oct 16, 2007, at 4:33 PM, VaclavK wrote: Hi, is it possible for someone to share latest build - official v3 build is 2925 but it does not contain msmq extension. I am unable to connect to cvs server now. -- View this message in context: http://www.nabble.com/Latest-build--- specifically-MSMQ-extension-tf4634567.html#a13234759 Sent from the wix-users mailing list archive at Nabble.com. -- --- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Fragment/Ref in Merge Module?
Hello, I have the following challenge: 1. I transformed the heat-output for my purposes with xslt to a files.wxs so that I can use it within the build-process. 2. I created a slim merge module: Directory Id=TARGETDIR Name=SourceDir Directory Id=MyProgram Name=MyProgram/ /Directory I found out that it is not possible to have Fragments in MergeModule for any reason. How can I get the files.wxs into the merge-module? The files.wxs looks like that: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment DirectoryRef Id=MyProgram . /DirectoryRef /Fragment /Wix Thanx, Chris - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 64-bit Questions
Do you also know how the ProcessorArchitecture attribute of the file element is actually used during deployment. _ From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: 17 October 2007 06:07 To: Stone, Darren (HBOS FS, IT , DDC Infrastructure) Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] 64-bit Questions [EMAIL PROTECTED] wrote: * I have seen that you can mark a Component as 64 bit (i.e. Win64='yes'). However I am not 100% clear on whether this is neccessary for .Net Assemblies as they are effectively only copied to my deployment directory. If a component is marked as 32-bit, MSI won't put it into 64-bit portions of the file system or registry. * I have also seen posts that state that 32-Bit and 64-Bit components should be deployed to different directories (I have 2 assemblies that need to be 32-Bit and several thousand that should run as 64-Bit!). Is this a neccessity or just good practice, and what is the reason for it. That's more of a Windows thing, keeping 32-bit and 64-bit portions of the system separate. -- sig://boB http://joyofsetup.com/ . HBOS plc, Registered in Scotland No. SC218813. Registered Office: The Mound, Edinburgh EH1 1YZ. HBOS plc is a holding company, subsidiaries of which are authorised and regulated by the Financial Services Authority. == - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patch element and creation of patch in 3.0
Thank you Peter for information... Does anybody know any tool, which can create delta patch from two versions of MSI? I tried MSI Patch Builder, it's not so bad, but on any project settings it crashes too. I was able to create .EXE patch only... Thanks. David. 2007/10/16, Peter Marcu [EMAIL PROTECTED]: Delta patching is not supported using the Patch element yet. Also, using the WiX 3.0 patch build system, you cannot patch things that come from MSM's. The suggested way to share setup logic is to use Wixlibs, if your msm's are built using wix, then you could consider that. Alternatively, you can create admin images of your target and upgrade layouts and run torch with the -ax switch. You can then pass those transforms as inputs into pyro along with Patch authoring. This is a way to get your msm logic into you patch. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Stindl Sent: Tuesday, October 16, 2007 5:38 AM To: WiX Users Subject: [WiX-users] Patch element and creation of patch in 3.0 Hallo all, could you anybody explain me, how to create patch in 3.0 WiX version? I've read any samples from Peter Marcu (e.g. http://blogs.msdn.com/pmarcu/archive/2007/06/28/sample-patch.aspx) but it is not enough for solution of my problem. I also can't find any documentation of Patch 3.0 WiX element. My problem is following: I have really big MSI installation, which is built on our build server every day and from time to time we need to apply delta patch on our production platform. Unfortunately with 2.0 WiX + PatchWiz we were not successful, because of crash of PatchWiz utility every time. The MSI packages are packages, where we have about 30 features (MSM modules), MSI are created by WiX version 2.0. Thanks a lot for help, otherwise I'm going to be crazy from that... :-/ David There is the main MSI source: -- Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; !-- Product definition -- Product Id=2EDDF5B5-FACA-437e-A5AF-E5EB84B47FB5 UpgradeCode='457F1CC2-0441-4114-A317-F640D32F8712' Language=1033 Codepage=1252 Version=4.2 Name=Product Manufacturer=Company.. !-- Package definition -- Package Id='----' InstallerVersion=200 Compressed=yes Manufacturer=Company Comments=a comment / !-- Media definitions -- Media Id='1' Cabinet='Foris.cab' EmbedCab='yes' DiskPrompt=CD-ROM #1 / Property Id='DiskPrompt' Value=Product Installation [1] / Property Id=ALLUSERS1/Property !-- Upgrade properties -- Upgrade Id='457F1CA2-0441-4114-A317-F640D32F8712' UpgradeVersion OnlyDetect='yes' Property='PATCHFOUND' Minimum='4.2.0' IncludeMinimum='yes' / UpgradeVersion OnlyDetect='yes' Property='NEWERFOUND' Minimum='4.2.0' IncludeMinimum='no' / /Upgrade CustomAction Id='AlreadyUpdated' Error='[ProductName] is already installed.' / CustomAction Id='NoDowngrade' Error='A later version of [ProductName] is already installed.' / !-- Installer Directories -- Directory Id='TARGETDIR' Name='SourceDir' Directory Id='ProgramFilesFolder' Name='PFiles' Directory Id='INSTALLDIR' Name='4.2' Merge Id=FNGInstallLib.971AF99B-8195-4248-9C21-776B2B3FD6C5 Language=1033 SourceFile=FNGInstallLib.msm DiskId=1 / /Directory /Directory /Directory /Directory /Directory !-- Installer Features -- Feature Id='Complete' Title=Product 4.2 Installation' Description='The complete Product 4.2 package.' Display='expand' Level='300' ConfigurableDirectory='INSTALLDIR' /Feature !-- ### Component Instalation Fragments ### -- FragmentRef Id='BaseFragment_FF'/ FragmentRef Id='BaseFragment_PP'/ FragmentRef Id='BaseFragment_PCT'/ FragmentRef Id='BaseFragment_RE'/ FragmentRef Id='BaseFragment_BM'/ FragmentRef Id='BaseFragment_CM'/ FragmentRef Id='BaseFragment_CMO'/ FragmentRef Id='BaseFragment_BE'/ FragmentRef Id='BaseFragment_AR'/ FragmentRef Id='BaseFragment_C'/ FragmentRef Id='BaseFragment_DF'/ FragmentRef Id='BaseFragment_V'/ FragmentRef Id='BaseFragment_MG'/ FragmentRef Id='BaseFragment_RI'/ FragmentRef Id='BaseFragment_RT'/ FragmentRef Id='BaseFragment_NE'/ FragmentRef Id='BaseFragment_UM'/ FragmentRef Id='BaseFragment_TU'/ !-- Installer GUI -- UIRef Id=WixUI_Mondo / UIRef Id=WixUI_ErrorProgressText / !-- Installer Seguinces -- InstallExecuteSequence Custom Action='AlreadyUpdated' After='FindRelatedProducts'PATCHFOUND/Custom Custom Action='NoDowngrade' After='FindRelatedProducts'NEWERFOUND/Custom RemoveExistingProducts After='InstallFinalize' / StartServices Suppress='yes'/ /InstallExecuteSequence /Product /Wix --
Re: [WiX-users] WixUI_Mondo.wxs + AdminInstallUI
I did the UI-less admin install and the error still occurred so it's safe to say it's not in my UI. This is my wxs fileUnfortunately I don't know enough about WiX yet to understand if there are any problems with it. http://www.nabble.com/file/p13248873/eProject.wxs eProject.wxs I'm not getting any errors when I build the package using: candle.exe eProject.wxs light.exe -out eProject.msi eProject.wixobj eprojectwixui.wixlib -loc WixUI_en-us.wxl -- View this message in context: http://www.nabble.com/WixUI_Mondo.wxs-%2B-AdminInstallUI-tf4621303.html#a13248873 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data
Bob Arnson-6 wrote: Karim MacDonald wrote: would replace the Class element, or if this particular Heat bug (think I saw it logged but can't find it now!) is likely to be fixed any time soon? So far, nobody's volunteered to maintain Heat so the bug isn't likely to fixed soon. I may see if I can fix this particular bug on my own system. I don't know how patch submissions work, but naively expect that I might then be able to submit a patch for inclusion at some date? Bob Arnson-6 wrote: Both are bad because they violate component rules. Could you be more specific about which rules they break please Bob? I've checked MSDN and although the same registry value is being written to twice, I can't see a component rule problem as long as this all happens within one component. Bob Arnson-6 wrote: Is it not enough to remove the mscoree.dll InprocServer32 value? Unfortunately the mscoree.dll value is correct not the problem: it's needed so that COM knows to prod .NET when the object is CoCreated. The root problem (I think) is that Heat is wrongly guessing the content of that registry value when it doesn't need to. A clean work-around would be a short dark.exe segue and then ditch the Class element from the authored code (I might do this). -- View this message in context: http://www.nabble.com/heating-COM-componnents-and-getting-LGHT0130-on-generated-registry-data-tf2815472.html#a13250119 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data
Karthik wrote: The problem is that autogenerated Id is not unique. It should be simple to write a temporary postprocessor that goes through and adds Id=[unique value] to each RegistryValue element. Thank you for your reply Karthik. I don't think this is the problem, as each generated Id seems to be unique to a given registry path+value. This seems sensible, as you wouldn't normally want to be writing from the reg-table to the same reg-value twice in the same setup. -- View this message in context: http://www.nabble.com/heating-COM-componnents-and-getting-LGHT0130-on-generated-registry-data-tf2815472.html#a13250236 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] (no subject)
Nick, I've had good success using NSIS (http://nsis.sourceforge.net) to create my bootstrapper. It can easily launch any application you may need. I've also heard good things about InnoSetup (http://www.jrsoftware.org/isinfo.php), but I have not used it myself. Hope this helps. Regards, Richard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nick Sent: Wednesday, October 17, 2007 1:33 AM To: [EMAIL PROTECTED] Cc: wix-users@lists.sourceforge.net Subject: [WiX-users] (no subject) Can you recommend another bootstrapper that can kick off an .exe (instead of the .msi)? Something tells me I might be writing my own bootstrapper tomorrow. * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Quixote Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper/Decryption
Yes and no. As a former SMS 2003 guy, I'd just use filemon to sniff out the extracted MSI location and break it out into it's own SMS package. I rarely used setup chainers because SMS has it's own chaining tool. You end up consuming less space on your distribution points, pull less bits ( pun intended for people who know what BITS is ) and you get better SMS status messages from the client when you let SMS own the chain. Another reason for me insisting on extracting the MSI is for source resilency. SMS can understand a relationship betwen an insalled application ( ProductCode ) and an MSI package sitting on a distribution point and automatically make it available to MSI if the DP is considered `local` to the subnet. I've also written utilities that query the SMS database and add source points that are also considered `remote` to the subnet. Bob Arnson [EMAIL PROTECTED] wrote: I'm not familiar with the VS bootstrapper but if it could kick off an .exe, write a C# app to do the decryption and launch the MSI. From a network management perspective, what you have can't be deployed by SMS or other similar tools (assuming your CA runs from the UI). __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] (no subject)
Can it handle silent installation stories and understand ProductCodes, PackageCodes to do things like invoke first time install, minor upgrades and maintenance UI stories? [EMAIL PROTECTED] wrote: Nick, I've had good success using NSIS (http://nsis.sourceforge.net) to create my bootstrapper. It can easily launch any application you may need. I've also heard good things about InnoSetup (http://www.jrsoftware.org/isinfo.php), but I have not used it myself. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Weekly builds - binaries.zip issues
It appears that the wix.dll included in the wix3-binaries.zip is a different from the one included in the .MSI, at least for the last couple of weekly builds. The one within the .MSI appears to be the correct one, with the right Public Key Token. Just a heads up for anyone that is trying to get the updated versions for the XmlConfig fix. K - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] NSis or InnoSetup as bootstrappers (was Re: (no subject))
Silent installations yes or at least it used to... I haven't tried recently because any user running the bootstrapper is doing so interactively and wants feedback on the process. Advanced users who want a fully silent installation handle the prerequisites for themselves, then trigger our main MSI. Understanding product and package codes... I'm sure it could, but I don't believe there is any native support for that. For the items I need to include in our bootstrapper, the presence of a supported version can typically be detected by examining the Windows registry. Both NSIS and InnoSetup belong to the older type of installation solution - procedural via a scripting language rather than data driven. As such you are able to do a lot of things that you really shouldn't! The *only* thing I use it for is the installation of third party dependencies. All other operations are handled in our product's MSI. Hope this helps, Regards, Richard On Wed, 2007-10-17 at 07:05 -0700, Christopher Painter wrote: Can it handle silent installation stories and understand ProductCodes, PackageCodes to do things like invoke first time install, minor upgrades and maintenance UI stories? [EMAIL PROTECTED] wrote: Nick, I've had good success using NSIS (http://nsis.sourceforge.net) to create my bootstrapper. It can easily launch any application you may need. I've also heard good things about InnoSetup (http://www.jrsoftware.org/isinfo.php), but I have not used it myself. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Quixote Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Bootstrapper/Decryption
I think I found what Bob recommends - Bootstrapper Manifest Generator http://www.codeplex.com/bmg I'll definitely check out NSIS and InnoSetup as well; thanks for all the help! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 17, 2007 07:30 AM To: [EMAIL PROTECTED] Cc: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] (no subject) Nick, I've had good success using NSIS (http://nsis.sourceforge.net) to create my bootstrapper. It can easily launch any application you may need. I've also heard good things about InnoSetup (http://www.jrsoftware.org/isinfo.php), but I have not used it myself. Hope this helps. Regards, Richard -Original Message- From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 17, 2007 00:09 AM To: Nick Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrapper/Decryption I'm not familiar with the VS bootstrapper but if it could kick off an .exe, write a C# app to do the decryption and launch the MSI. From a network management perspective, what you have can't be deployed by SMS or other similar tools (assuming your CA runs from the UI). -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] heating COM componnents and getting LGHT0130 on generated registry data
Yeah, you're right. I wrote something that autogenerated Id's as a fix to get my test build working, but my coworker, who had to use it in his project, ended up using regasm /regfile to generate the right entries. On 10/17/07, Karim MacDonald [EMAIL PROTECTED] wrote: Karthik wrote: The problem is that autogenerated Id is not unique. It should be simple to write a temporary postprocessor that goes through and adds Id=[unique value] to each RegistryValue element. Thank you for your reply Karthik. I don't think this is the problem, as each generated Id seems to be unique to a given registry path+value. This seems sensible, as you wouldn't normally want to be writing from the reg-table to the same reg-value twice in the same setup. -- View this message in context: http://www.nabble.com/heating-COM-componnents-and-getting-LGHT0130-on-generated-registry-data-tf2815472.html#a13250236 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WIX2 Windows Vista
Hello, I have custom action in C++ dll that opens installed file and modifies it. But in Windows Vista if file needs admin rights(for example if file is under Program Files tree) opening file for writing fails. I'm trying to use CustomAction Id=SettingUpConfigFile BinaryKey=InstallHelper DllEntry=SetUpConfig Execute='deferred'/ Custom Action=SettingUpConfigFile After=PublishProductNOT Installed/Custom Any ideas how to solve this problem? Thanks for helping, Benas - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 64-bit Questions
I believe this ends up in the MsiAssemblyName table together with some other assembly name attributes. If you get it wrong the usual symptom is that the assembly won't be uninstalled from the GAC. Assuming this is for the MsiAssemblyName table, IMO WiX should be getting this value for you automatically rather than having you specify it. Phil Wilson From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, October 17, 2007 12:35 AM To: [EMAIL PROTECTED] Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] 64-bit Questions Do you also know how the ProcessorArchitecture attribute of the file element is actually used during deployment. From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: 17 October 2007 06:07 To: Stone, Darren (HBOS FS, IT , DDC Infrastructure) Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] 64-bit Questions [EMAIL PROTECTED] wrote: * I have seen that you can mark a Component as 64 bit (i.e. Win64='yes'). However I am not 100% clear on whether this is neccessary for .Net Assemblies as they are effectively only copied to my deployment directory. If a component is marked as 32-bit, MSI won't put it into 64-bit portions of the file system or registry. * I have also seen posts that state that 32-Bit and 64-Bit components should be deployed to different directories (I have 2 assemblies that need to be 32-Bit and several thousand that should run as 64-Bit!). Is this a neccessity or just good practice, and what is the reason for it. That's more of a Windows thing, keeping 32-bit and 64-bit portions of the system separate. -- sig://boB http://joyofsetup.com/ . HBOS plc, Registered in Scotland No. SC218813. Registered Office: The Mound, Edinburgh EH1 1YZ. HBOS plc is a holding company, subsidiaries of which are authorised and regulated by the Financial Services Authority. == - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] French accents and Windows Installer
Sorry if this has been covered already, but I couldn't find anything in the archives. I was looking for a French Translation of WixUI, and found an almost complete one at http://www.tramontana.co.hu/wix/loc/index.php. The only problem I ran into is that anything that had an accented character (é etc) showed up as a ? in the installer (even though they display fine in other applications). Is there something else that needs to be done to compile with the correct fonts? The French file only uses standard ASCII characters, so they should be present on the target system. Has anyone else encountered this? Thanks, Chris - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIX2 Windows Vista
Does it fail even if you run your setup elevated? If you’re able to run your MSI non-elevated, it’s probably using the compatibility features to write to a mirror program files directory under the user profile, not the real one. If you run your msi, does Windows ask if you want to elevate? If not (and you want to force it), a simple way to do it would be to generate a bootstrapper-one of the checks that the OS does to determine if you need elevation is to check if the app is named “setup.exe”. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Benas Sent: Wednesday, October 17, 2007 2:33 PM To: WiX-users Subject: [WiX-users] WIX2 Windows Vista Hello, I have custom action in C++ dll that opens installed file and modifies it. But in Windows Vista if file needs admin rights(for example if file is under Program Files tree) opening file for writing fails. I'm trying to use CustomAction Id=SettingUpConfigFile BinaryKey=InstallHelper DllEntry=SetUpConfig Execute='deferred'/ Custom Action=SettingUpConfigFile After=PublishProductNOT Installed/Custom Any ideas how to solve this problem? Thanks for helping, Benas - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Break up wix code
I am a newbie with WiX. I had a quick question regarding structuring my WiX wxs file. The way I have it set up is that all the UI code is in this one large .WXS file. I was wondering if I could break up this WXS file into smaller files (maybe like each UI Dialog in its own file or something) so that changes can be multiple developers can work on different areas simultaneously. Appreciate your help. Thanks, - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Permission in ServiceInstall fails
The process to create a user, create a service, and then set the service to run as the user is fairly straitforward. I have User and ServiceInstall elements and I've verified that they're working fine by themselves; both the user and the service are created upon install. The problem comes when I try to assign the user the appropriate rights to start the service. I have the appropriate Permission element underneath ServiceInstall, but whenever I run my MSI with that element, I get the following error message in my install log: ExecSecureObjects: Error 0x80070424: failed to get security info for object: hmr_db As best as I can tell, both the user and the service are being created before this message is logged; I see these two log messages prior to the error: Action 13:53:44: CreateUser. Action 13:53:48: InstallServices. Installing new services Here's the appropriate parts of my WXS file: Component Id=postgresql_service Guid=9BDBC894-66D1-4F38-BB0B-15E564F82130 File Id=pg_ctl.exe LongName=pg_ctl.exe Name=PG_CTL.EXE Source=..\..\..\..\..\..\..\Program Files\pgsql\bin\pg_ctl.exe KeyPath=yes DiskId=1 / ServiceInstall Id=postgresql_service Description=Hybrid Medical Records Database Server DisplayName=HMR Database ErrorControl=critical Name=[SERVICE_NAME] Start=auto Type=ownProcess Vital=yes Arguments=runservice -W -N quot;[SERVICE_NAME]quot; -D quot;[postgresql_data]quot; Account=[DATABASE_USER_DOMAIN]\[DATABASE_USER_NAME] Password=[DATABASE_USER_PASSWORD] Permission User=[DATABASE_USER_NAME] Domain=[DATABASE_USER_DOMAIN] ServiceStart=yes ServiceStop=yes ServiceInterrogate=yes ServicePauseContinue=yes ServiceQueryConfig=yes ServiceQueryStatus=yes Extended=yes ServiceChangeConfig=yes ServiceEnumerateDependents=yes ServiceUserDefinedControl=yes / /ServiceInstall /Component [...snip...] Component Id=postgresql_account Guid=E67E92FE-6926-46F7-8F86-E5BD981CD84C User Id=postgresql_user Name=[DATABASE_USER_NAME] CanNotChangePassword=yes CreateUser=yes Disabled=no Domain=[DATABASE_USER_DOMAIN] FailIfExists=no Password=[DATABASE_USER_PASSWORD] PasswordExpired=no PasswordNeverExpires=yes RemoveOnUninstall=yes UpdateIfExists=yes / /Component (The two Components are in different Directorys, if that matters. I can supply the full WXS and log file if necessary. The SERVICE_NAME property is set to hmr_db; the error message does appear to be referring to the service with the correct name.) As I mentioned, the user and service are being created correctly (although the service can't start due to the missing permissions), but the minute that I add in Permission the install fails. I've Googled all over the net for any information on this problem to no avail. Can anyone help with this? It looks like a WIX/MSI bug to me; is there a workaround? Thanks, Craig - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix-3.0 and MDAC27ENU merge module
Did you ever find a solution? I am seeing the same warning. My initial guess is that its happening because my merge modules are in Wix 1.0 and since then they must have added more rules to the ICE validation Thanks, -M David Howell-2 wrote: Hi Again, I am now trying to using the MDAC27ENU.MSM in my wix-3.0 project. Again, this msm was obtained from the InstallShield (or MS) website. When I run light, I receive the following warnings and errors: Microsoft (R) Windows Installer Xml Linker version 3.0.2015.0 Copyright (C) Microsoft Corporation 2003. All rights reserved. .wxs(28) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'DesktopFolder' which cannot be merged from the merge module 'C:\Merge Modules\mdac27enu.MSM'. 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. .wxs(28) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'ProgramFilesFolder' which cannot be merged from the merge module 'C:\Merge Modules\mdac27enu.MSM'. 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. .wxs(28) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'SystemFolder' which cannot be merged from the merge module 'C:\Merge Modules\mdac27enu.MSM'. 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. light.exe : error LGHT0204 : ICE99: The directory name: PrimaryVolumePath is the same as one of the MSI Public Properties and can cause unforeseen side effects. light.exe : error LGHT0204 : ICE99: The directory name: WindowsVolume is the same as one of the MSI Public Properties and can cause unforeseen side effects. If I don't include this particular merge module, I don't receive any warnings or errors. I understand I can ignore the warnings, however how do I overcome the errors? Cheers, David. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://www.nabble.com/Wix-3.0-and-MDAC27ENU-merge-module-tf2156640.html#a13262200 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Break up wix code
The commonly accepted solution is breaking up the code into fragments. The source code of WiX UI (wixui.wixlib) might be of your interest, as it is a good example (I think, what I write at least stands for WiX 2.x). In this case, for each level of UI - depending on how far it is reduced - different dialog collections are obtained from the same dialogs using DialogRef elements (each dialog is in a separate WiX file, and there is one another atomic file for the binaries like bitmaps). 2007/10/17, Sajo Jacob [EMAIL PROTECTED]: I am a newbie with WiX. I had a quick question regarding structuring my WiX wxs file. The way I have it set up is that all the UI code is in this one large .WXS file. I was wondering if I could break up this WXS file into smaller files (maybe like each UI Dialog in its own file or something) so that changes can be multiple developers can work on different areas simultaneously. Appreciate your help. Thanks, - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] French accents and Windows Installer
You need to set the codepage attribute to the Franch codepage. Than it will work. _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Bardon Sent: Wednesday, October 17, 2007 2:44 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] French accents and Windows Installer Sorry if this has been covered already, but I couldn't find anything in the archives. I was looking for a French Translation of WixUI, and found an almost complete one at http://www.tramontana.co.hu/wix/loc/index.php. The only problem I ran into is that anything that had an accented character (é etc) showed up as a ? in the installer (even though they display fine in other applications). Is there something else that needs to be done to compile with the correct fonts? The French file only uses standard ASCII characters, so they should be present on the target system. Has anyone else encountered this? Thanks, Chris - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom EULA
You can e.g. replace the license.rtf file found in the wix binaries directory, but that would be a bit rude solution. I think otherwise the file should be placed in the folder with the .wixobj files to be built with light. I hope someone corrects me if I'm wrong. 2007/10/17, Levon Levonian [EMAIL PROTECTED]: Hi All, I am using WixUI_Minimal, but I want to have my custom EULA. The tutorial says: To specify your product's license, include a License.rtf file in the current directory when you run *light*. Well, I included such a file, but nothing happens. Any ideas? Thanks! ** READER BEWARE: Unencrypted, unsigned Internet e-mail is inherently insecure. Internet messages may be corrupted, incomplete, misdirected or may incorrectly identify the sender. Therefore, nothing in this message or attachments may be considered legally binding. THIS MESSAGE IS ONLY INTENDED FOR THE USE OF THE INDIVIDUAL OR ENTITY TO WHICH IT IS ADDRESSED AND MAY BE PRIVILEGED. If you are not the intended recipient or their authorized agent, you may not forward or copy this information and must delete or destroy all copies of this message and attachments received. If you have received this communication in error, please notify Matrikon Inc. by telephone at (780) 448-1010. ** - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Custom EULA
Hi All, I am using WixUI_Minimal, but I want to have my custom EULA. The tutorial says: To specify your product's license, include a License.rtf file in the current directory when you run light. Well, I included such a file, but nothing happens. Any ideas? Thanks! ** READER BEWARE: Unencrypted, unsigned Internet e-mail is inherently insecure. Internet messages may be corrupted, incomplete, misdirected or may incorrectly identify the sender. Therefore, nothing in this message or attachments may be considered legally binding. THIS MESSAGE IS ONLY INTENDED FOR THE USE OF THE INDIVIDUAL OR ENTITY TO WHICH IT IS ADDRESSED AND MAY BE PRIVILEGED. If you are not the intended recipient or their authorized agent, you may not forward or copy this information and must delete or destroy all copies of this message and attachments received. If you have received this communication in error, please notify Matrikon Inc. by telephone at (780) 448-1010. ** - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom EULA
Thanks, but I tried putting it into the /obj directory, into /obj/debug, then into the same dir as the *.wxs file, but it just doesn't include my License.rtf. I wonder if anybody did that successfully. Or is there some command line switch to include the EULA? From: János Brezniczky [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 17, 2007 15:48 To: Levon Levonian Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Custom EULA You can e.g. replace the license.rtf file found in the wix binaries directory, but that would be a bit rude solution. I think otherwise the file should be placed in the folder with the .wixobj files to be built with light. I hope someone corrects me if I'm wrong. 2007/10/17, Levon Levonian [EMAIL PROTECTED]: Hi All, I am using WixUI_Minimal, but I want to have my custom EULA. The tutorial says: To specify your product's license, include a License.rtf file in the current directory when you run light. Well, I included such a file, but nothing happens. Any ideas? Thanks! ** READER BEWARE: Unencrypted, unsigned Internet e-mail is inherently insecure. Internet messages may be corrupted, incomplete, misdirected or may incorrectly identify the sender. Therefore, nothing in this message or attachments may be considered legally binding. THIS MESSAGE IS ONLY INTENDED FOR THE USE OF THE INDIVIDUAL OR ENTITY TO WHICH IT IS ADDRESSED AND MAY BE PRIVILEGED. If you are not the intended recipient or their authorized agent, you may not forward or copy this information and must delete or destroy all copies of this message and attachments received. If you have received this communication in error, please notify Matrikon Inc. by telephone at (780) 448-1010. ** - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX v3 Sql Extension not executing SqlScript
Hi, Is this still an issue with the version 3.0.2925.0? I have a WiX v3 installation which uses the SqlDatabase to create a database. This works great. However, as soon as I add a child SqlScript and a corresponding Binary my installation just hangs until I kill the process and never executes the sql in the referenced file. I put a trace on SQL Server and I don't even see the statements that were previously getting executed successfully by the SqlDatabase node before adding that SqlScript. I tried executing the first statement in my (unfortunately) long sql script through the SqlString element, and it was successful, but I was hoping to avoid the extra work involved in translating all those statements in my scripts into strings. I saw a couple posts regarding similar, but not the same problems. Is there something obvious I might be doing wrong, or do I just need to steer clear of the SqlScript for now? ... Component Id=CreateDatabases Guid=66B197B5-42D0-462F-A97E-760D984C38FC sql:SqlDatabase Id=IVantageDatabase Server=[SQLSERVER] Database=[DATABASENAME] User=InstallationSqlUser CreateOnInstall=yes DropOnUninstall=yes sql:SqlFileSpec Id=IVantageDatabaseFile Filename=[DataDirectory][DATABASEFILENAME].mdf Name=[DATABASEFILENAME] / sql:SqlLogFileSpec Id=IVantageDatabaseLogFile Filename=[DataDirectory][DATABASEFILENAME]_Log.ldf Name=[DATABASEFILENAME]_Log / sql:SqlScript Id=ExecuteIVantageDLLSql BinaryKey=ExecuteIVantageDDLSqlBin ExecuteOnInstall=yes ContinueOnError=no RollbackOnUninstall=yes Sequence=001 User=InstallationSqlUser / /sql:SqlDatabase /Component ... Feature Id=iVantage Title=iVantage 5.0 Level=1 ... ComponentRef Id=CreateDatabases / ... /Feature util:User Id=InstallationSqlUser Name=[SQLUSER] Password=[SQLUSERPASSWORD] xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; / Binary Id=ExecuteIVantageDDLSqlBin SourceFile=..\Business\Data\iVantage40DDL.sql / ... Thanks, Amy Rosewater Sr. Development Programmer/Analyst SPECTRUM Human Resource Systems Corporation 707 Seventeenth Street, Suite 3800 Denver, CO 80202-3438 (303) 592-3403 Phone (800) 334-5660 Toll Free (303) 592-3233 Fax [EMAIL PROTECTED] - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX v3 Sql Extension not executing SqlScript
I am able to use these elements successfully with 3.0.3328.0. This is the first v3 build I've used so don't know if there was an intentional change between these releases. Amy Rosewater wrote: Hi, Is this still an issue with the version 3.0.2925.0? I have a WiX v3 installation which uses the SqlDatabase to create a database. This works great. However, as soon as I add a child SqlScript and a corresponding Binary my installation just hangs until I kill the process and never executes the sql in the referenced file. I put a trace on SQL Server and I don't even see the statements that were previously getting executed successfully by the SqlDatabase node before adding that SqlScript. snip -- View this message in context: http://www.nabble.com/WiX-v3-Sql-Extension-not-executing-SqlScript-tf4643760.html#a13265661 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Dialog disappearing instantly
Hi, I have the following in UI sequence Show Dialog=PrereqCheck After=CostFinalize![CDATA[Installed= AND NOT RESUME]]/Show Show Dialog=Installing After=PrereqCheck![CDATA[Installed= AND NOT RESUME]]/Show Now the problem is I can see the PrereqCheck dialog, but it instantly disappears and the Installing dialog is shown. Is there any way I can block the Installing dialog and force the user to do some action in PrereqCheck dialog? Thanks, Nitin DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to add newline in Condition message
Hi, I tried the following, but it doesn't work Condition Message=Not Admin \n\r don't have 2.0(NOT Priviledged) AND MsiNetAssemblySupport lt;= 2.0.50727/Condition How to display message in multiple lines. Thanks, Nitin DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to add newline in Condition message
Hi WiX does not directly support this. But you can create the Public Property from Custom Action (e.g. CRLF) and this property will contain the new line sequence \r\n. After that you can write your message in the following way: Condition Message=Not Admin [CRLF] don’t have 2.0(NOT Priviledged) AND MsiNetAssemblySupport lt;= 2.0.50727/Condition BTW: It would be nice if WiX could generate such PublicProperty during creation of MSI package... regards Stefan Nitin Chaudhari wrote: Hi, I tried the following, but it doesn’t work Condition Message=Not Admin \n\r don’t have 2.0(NOT Priviledged) AND MsiNetAssemblySupport lt;= 2.0.50727/Condition How to display message in multiple lines. Thanks, Nitin DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Ltd. does not accept any liability for virus infected mails. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Stefan Pavlik | [EMAIL PROTECTED] Whitestein Technologies s.r.o. | www.whitestein.com Panenska 28 | 811 03 Bratislava | Slovak Republic Main +421 2 5443-5502 | Direct +421 2 5930-0735 - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIX2 Windows Vista
You are missing Impersonate=no in your CustomAction element. On Vista, the action runs impersonating the installing user, who (with UAC turned on) does not have write permission under Program Files, since it is the user before the elevation prompt. If you set Impersonate=no, then the custom action will be called from SYSTEM, which does have that right. From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Benas [EMAIL PROTECTED] Sent: Wednesday, October 17, 2007 11:33 AM To: WiX-users Subject: [WiX-users] WIX2 Windows Vista Hello, I have custom action in C++ dll that opens installed file and modifies it. But in Windows Vista if file needs admin rights(for example if file is under Program Files tree) opening file for writing fails. I'm trying to use CustomAction Id=SettingUpConfigFile BinaryKey=InstallHelper DllEntry=SetUpConfig Execute='deferred'/ Custom Action=SettingUpConfigFile After=PublishProductNOT Installed/Custom Any ideas how to solve this problem? Thanks for helping, Benas - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
