[WiX-users] How to change installation text on the last
On the last step of the installation, there are texts showing: Completed the productName Setup Wizard. I know productName is user provide, how about other text Completed the ... Setup Wizard , are they build with the tool, or can we customize those text ? Thanks, -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to change installation text on the last
On the last step of the installation, there are texts showing: Completed the productName Setup Wizard. I know productName is user provide, how about other text Completed the ... Setup Wizard , are they build with the tool, or can we customize those text ? You can add additional text using: Property Id=WIXUI_EXITDIALOGOPTIONALTEXT Value=Your text here. / Dave -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding a check box to the final page results in a grey background over the white property page
Does anyone know how to change the final property page from a white background to the default grey - so that an added check box doesn't look ridiculous (with its grey background over the white page)? Dave -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to change installation text on the last
On 15/08/2012 09:05, David Lowndes wrote:
I know productName is user provide, how about other text Completed the
... Setup Wizard , are they build with the tool, or can we customize those
text ?
You can add additional text using:
Property Id=WIXUI_EXITDIALOGOPTIONALTEXT Value=Your text here. /
Or change that text by adding (to a .wxl file in your project):
String Id=ExitDialogTitle{\WixUI_Font_Bigger}Replacement text
here/String
--
Bruce Cran
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing add-on files to an existing installation
Your solution sounds perfectly reasonable. To check compatibility in 3), youll need to have some way of discovering the version of the addons. You could either read the addon installer's product code in FindRelatedProducts or have the addon installer write its ProductVersion to a version-independent location in the registry and search for that. The latter has a slight advantage of not having to do multiple comparisons of GUIDs to check compatibility. It also assumes all addon installers are in a mutually exclusive series - no parallel installations. Your testing will have to include the possibility that the user runs both installers, then removes the base one, violating requirement 2). Although you dont mention any such requirement, you might be wanting to restrict which versions of each installer can be installed at the same time. It'll be hard to enforce that at installation time because each MSI can be removed or updated after the installation of the other, so such checks are best handled by the application. -Original Message- From: Chris Lord [mailto:chris.l...@atterotech.com] Sent: Tue 8/14/2012 8:35 PM To: wix-users Subject: [WiX-users] Installing add-on files to an existing installation Hi all, This should be a quick one, I have an installer that installs my application and its support files. Following a discussion earlier, it's possible I may need to install some additional add-on files. Here are my requirements. 1) The add-on files should be installed separately to the main base files. 2) The add-on files can only be installed if the base software is present. 3) The base installation should continue to be updatable without affecting the add-on files (assuming they are compatible of course). 4) The add-on files should be updatable but separately from the base installation. I would like to keep things as simple as possible and my initial thought is to create a second stand-alone MSI that has conditions such that it will exit if a FindReleatedProducts search for the base install fails. Would that be the best way of achieving my requirements or is there a better way? Any suggestions gratefully received. Thanks Chris Lord Product Engineer Attero Tech, LLC 1315 Directors Row, Suite 107 Fort Wayne, IN 46808 Ph: 260-496-9668 ext. 377, Fax 260-496-9879 email: chris.l...@atterotech.com Confidentiality Notice: This message is intended solely for the use of the addressees shown above. It may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient of this message, you are hereby notified that the copying, use or distribution of any information or materials transmitted in or with this message is strictly prohibited. If you received this message by mistake, please immediately contact me at (260) 496-9668 x 377 or chris.l...@atterotech.com and destroy the original message. Thank you. - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding a check box to the final page results in a grey background over the white property page
You need to supply you own version of background bitmap, see http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm. The variable to set is WixUIDialogBmp e.g. WixVariable Id=WixUIDialogBmp Value=Bitmaps\dlgbmp.bmp / Neil Does anyone know how to change the final property page from a white background to the default grey - so that an added check box doesn't look ridiculous (with its grey background over the white page)? Dave -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding a check box to the final page results in a grey background over the white property page
You need to supply you own version of background bitmap, see http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm. The variable to set is WixUIDialogBmp e.g. WixVariable Id=WixUIDialogBmp Value=Bitmaps\dlgbmp.bmp / Thanks Neil. I presume the stock bitmap is just plain white? Is there no way to remove the bitmap so that we get the same default grey as all the other pages? That would be better and more consistent anyway. I've tried setting the value to , but that just results in: LGHT0001: Value cannot be null. Dave -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding a check box to the final page results in a grey background over the white property page
Not sure if you can make it smaller, I would try and see what happens. If you want the originals you can find them in the source (src\ext\UIExtension\wixlib\Bitmaps) Neil You need to supply you own version of background bitmap, see http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm. The variable to set is WixUIDialogBmp e.g. WixVariable Id=WixUIDialogBmp Value=Bitmaps\dlgbmp.bmp / Thanks Neil. I presume the stock bitmap is just plain white? Is there no way to remove the bitmap so that we get the same default grey as all the other pages? That would be better and more consistent anyway. I've tried setting the value to , but that just results in: LGHT0001: Value cannot be null. Dave -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] What's the neatest way of adding a start menu shortcut to an installed file?
I've followed the instructions here: http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm, to add a start menu shortcut, and while that produces no warnings, I thought it would be more elegant to use [#MyApplicationFile] for the target like this: DirectoryRef Id=ApplicationProgramsFolder Component Id=ApplicationShortcut Guid=... Shortcut Id=ApplicationStartMenuShortcut Name=My Application Name Description=My Application Description Target=[#MyApplicationFile] WorkingDirectory=INSTALLFOLDER/ RemoveFolder Id=ApplicationProgramsFolder On=uninstall/ RegistryValue Root=HKCU Key=Software\MyCoConsoleTestApp Name=installed Type=integer Value=1 KeyPath=yes/ /Component /DirectoryRef While the above appears to work fine, it gives the following warning (which seems reasonable): warning LGHT1076: ICE69: Mismatched component reference. Entry 'ApplicationStartMenuShortcut' of the Shortcut table belongs to component 'ApplicationShortcut'. However, the formatted string in column 'Target' references file 'MyApplicationFile' which belongs to component 'ProductComponent'. Components are in the same feature. So, I tried moving the shortcut into the component 'ProductComponent'... ComponentGroup Id=ProductComponents Directory=INSTALLFOLDER Component Id=ProductComponent File Id=MyApplicationFile Name=$(var.ConsoleApplication1.TargetFileName) Source=$(var.ConsoleApplication1.TargetPath) DiskId=1 KeyPath=yes / RegistryKey Root=HKLM Key=Software\MyCo\TestProductRegistryKey RegistryValue Type=string Value=[INSTALLFOLDER] p1 p2 p3 Name=ThingyValue / /RegistryKey Shortcut Id=ApplicationStartMenuShortcut Directory=ApplicationProgramsFolder Name=My Application Name Description=My Application Description Target=[#MyApplicationFile] WorkingDirectory=INSTALLFOLDER / RegistryValue Root=HKCU Key=Software\MyCo\ConsoleTestApp Name=installed Type=integer Value=1 KeyPath=yes / /Component /ComponentGroup But that gives rise to: error CNDL0042: The Component element has multiple key paths set. The key path may only be set to 'yes' in extension elements that support it or one of the following locations: Component/@KeyPath, File/@KeyPath, RegistryValue/@KeyPath, or ODBCDataSource/@KeyPath. If I remove the KeyPath from the RegistryValue or the File elements, I get into a spiralling mess of more errors. So, what's the neatest way of installing a file and providing a start menu shortcut to it (and using [#idname] reference)? Dave -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Custom Exit text based on custom and wix defined variables
Hi All, Is there a nicer way to deliver logic that will satisfy the requirements below, other than the attached code ? Requirements; a) Display specific text if releasetype (full), product(professional) and install is not an upgrade b) Display specific text if releasetype(full), product(professional) and install is an upgrade Proposed Solution ; !---Delivers a specific exit message if product is not an upgrade/installed -- ?if $(var.releasetype)=full And $(var.product)=Professional ? Control Id=Description Type=Text X=135 Y=70 Width=220 Height=20 Transparent=yes NoPrefix=yes Text=!(loc.ExitDialogueDescription1) Condition Action = show NOT (Installed or WIX_UPGRADE_DETECTED)/Condition /Control ?endif? !---Delivers a specific exit message if the product is an upgrade/installed -- ?if $(var.releasetype)=full And $(var.product)=Professional ? Control Id=Description Type=Text X=135 Y=70 Width=220 Height=20 Transparent=yes NoPrefix=yes Text=!(loc.ExitDialogueDescription2) Condition Action = show Installed or WIX_UPGRADE_DETECTED /Condition /Control ?endif? Thanks, Alex -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] What's the neatest way of adding a start menu shortcut to an installed file?
I prefer to advertise my shortcuts to avoid all these problems. On Wed, Aug 15, 2012 at 4:19 AM, David Lowndes dav...@mvps.org wrote: I've followed the instructions here: http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm, to add a start menu shortcut, and while that produces no warnings, I thought it would be more elegant to use [#MyApplicationFile] for the target like this: DirectoryRef Id=ApplicationProgramsFolder Component Id=ApplicationShortcut Guid=... Shortcut Id=ApplicationStartMenuShortcut Name=My Application Name Description=My Application Description Target=[#MyApplicationFile] WorkingDirectory=INSTALLFOLDER/ RemoveFolder Id=ApplicationProgramsFolder On=uninstall/ RegistryValue Root=HKCU Key=Software\MyCoConsoleTestApp Name=installed Type=integer Value=1 KeyPath=yes/ /Component /DirectoryRef While the above appears to work fine, it gives the following warning (which seems reasonable): warning LGHT1076: ICE69: Mismatched component reference. Entry 'ApplicationStartMenuShortcut' of the Shortcut table belongs to component 'ApplicationShortcut'. However, the formatted string in column 'Target' references file 'MyApplicationFile' which belongs to component 'ProductComponent'. Components are in the same feature. So, I tried moving the shortcut into the component 'ProductComponent'... ComponentGroup Id=ProductComponents Directory=INSTALLFOLDER Component Id=ProductComponent File Id=MyApplicationFile Name=$(var.ConsoleApplication1.TargetFileName) Source=$(var.ConsoleApplication1.TargetPath) DiskId=1 KeyPath=yes / RegistryKey Root=HKLM Key=Software\MyCo\TestProductRegistryKey RegistryValue Type=string Value=[INSTALLFOLDER] p1 p2 p3 Name=ThingyValue / /RegistryKey Shortcut Id=ApplicationStartMenuShortcut Directory=ApplicationProgramsFolder Name=My Application Name Description=My Application Description Target=[#MyApplicationFile] WorkingDirectory=INSTALLFOLDER / RegistryValue Root=HKCU Key=Software\MyCo\ConsoleTestApp Name=installed Type=integer Value=1 KeyPath=yes / /Component /ComponentGroup But that gives rise to: error CNDL0042: The Component element has multiple key paths set. The key path may only be set to 'yes' in extension elements that support it or one of the following locations: Component/@KeyPath, File/@KeyPath, RegistryValue/@KeyPath, or ODBCDataSource/@KeyPath. If I remove the KeyPath from the RegistryValue or the File elements, I get into a spiralling mess of more errors. So, what's the neatest way of installing a file and providing a start menu shortcut to it (and using [#idname] reference)? Dave -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching http://RobMensching.com LLC -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX joins the Outercurve Foundation
Date: Tue, 14 Aug 2012 21:06:07 +0100 From: br...@cran.org.uk I'm a bit surprised that the license change wasn't highlighted - it seems WiX is now licensed under the Ms-Rl. I would appreciate some clarification on this license too. (A) Reciprocal Grants- For any file you distribute that contains code from the software (in source code or binary format), you must provide recipients the source code to that file along with a copy of this license, which license will govern that file. You may license other files that are entirely your own work and do not contain code from the software under any terms you choose. A Burn bundle contains WiX code in binary format so what source code do I need to provide? The .wxs file? Or the source code to my program? Peter -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX joins the Outercurve Foundation
On 15/08/2012 12:55, Peter Hull wrote: (A) Reciprocal Grants- For any file you distribute that contains code from the software (in source code or binary format), you must provide recipients the source code to that file along with a copy of this license, which license will govern that file. You may license other files that are entirely your own work and do not contain code from the software under any terms you choose. This sounds to me rather similar to requirement iv. under the previous CPL: iv. states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used for software exchange. -- Bruce Cran -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] What's the neatest way of adding a start menu shortcut to an installed file?
I prefer to advertise my shortcuts to avoid all these problems. OK, I started down that path too and also had problems with that. :( Do you know of a concise example of doing what I need using advertised shortcuts? Dave -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] What's the neatest way of adding a start menu shortcut to an installed file?
I prefer to advertise my shortcuts to avoid all these problems. OK, this example has sorted me out: http://blogs.technet.com/b/alexshev/archive/2008/02/20/from-msi-to-wix-part- 10-shortcuts.aspx It's hard to find the wheat from the chaff with all the WiX information around. :( Dave -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Adding a check box to the final page results in a grey background over the white property page
Not sure if you can make it smaller, I would try and see what happens. Nice idea, unfortunately it stretches the bitmap to fit over the whole page. :( Rob, would a bug report/suggestion to eliminate the background behaviour be something that would be possible? Dave -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn Install adds item to Programs and Features too soon.
Working with build 2928, it seems that the burn engine adds an entry that is visible in Programs and Features too soon. It adds it there before anything is installed. It can get you into some weird states. Scenario 1: Listed in Programs and Features but not installed There comes a point in the install process where the app is listed in Programs and Features before any packages are installed. There is a point where you can kill the process where nothing was installed but the app is still listed in Programs and Features Scenario 2: Not listed in Programs and Featurs but installed Since the app can show up in Programs and Features prematurely, you can also ask it to uninstall before anything has been installed. You can then continue with the original install process and it installs fine. The result is the program is installed but not listed in Program and Features Any insights? Should I submit a bug? -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn /layout doesn't extract embedded resources from bundle
IIRC this worked a while ago with older WiX v3.6 builds but hasn't for a while. If I run my Bundle with the /layout switch, it will download the .NET 4.0 Client Profile redistributable any other MSI's or MSPs I have in my bundle which have a DownloadURL specified (and Compressed=no set). However any MSI or MSP which doesn't have a DownloadURL specified is embedded in the Bundle using the Compressed=yes attribute isn't extracted during the layout procedure. This means anyone who wants to use the MSI directly for managed deployment has to hack around with the Bundle to get at the MSI (run it as if to install, wait until it's extracted the embedded files to its temp directory, check the log to find the temp directory then copy them out of the temp directory cancel the install). Code: Chain PackageGroupRef Id=NetFx40ClientRedist/ MspPackage Id=SharedContentPatch SourceFile=..\..\..\install\VESharedContent.msp After=NetFx40ClientRedist Compressed=no DisplayInternalUI=yes DownloadUrl=http://cdn.iesve.com/ve/VESharedContent.msp; InstallSize=1 PerMachine=yes Permanent=yes Vital=yes Slipstream=yes / MsiPackage Id=ve SourceFile=..\..\..\install\ve2012.msi After=SharedContentPatch Compressed=yes DisplayInternalUI=yes ForcePerMachine=yes Permanent=no Visible=no Vital=yes / MsiPackage Id=SketchUpPlugin SourceFile=..\..\..\install\SketchUpPlugin2012.msi After=ve Compressed=yes DisplayInternalUI=yes ForcePerMachine=yes Permanent=no Visible=no Vital=no InstallCondition=SketchUp8Installed = 1 OR SketchUp7Installed = 1 OR SketchUp6Installed = 1 / MsiPackage Id=RevitPlugin SourceFile=..\..\..\install\RevitPlugin2012.msi After=SketchUpPlugin Compressed=yes DisplayInternalUI=yes ForcePerMachine=yes Permanent=no Visible=no Vital=no InstallCondition=RAC2008Installed = 1 OR RME2008Installed = 1 OR RAC2009Installed = 1 OR RME2009Installed = 1 OR RAC2009x64Installed = 1 OR RME2009x64Installed = 1 OR RAC2010Installed = 1 OR RME2010Installed = 1 OR RAC2010x64Installed = 1 OR RME2010x64Installed = 1 OR RAC2011Installed = 1 OR RME2011Installed = 1 OR RAC2011x64Installed = 1 OR RME2011x64Installed = 1 OR RAC2012Installed = 1 OR RME2012Installed = 1 OR RAC2012x64Installed = 1 OR RME2012x64Installed = 1 OR RAC2013Installed = 1 OR RME2013Installed = 1 OR RAC2013x64Installed = 1 OR RME2013x64Installed = 1 / /Chain Log - http://upload.iesve.com/downloads/burn_issues/layout.log Should I bug report this? Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn /layout doesn't extract embedded resources frombundle
That's the expected behaviour. The layout operation isn't meant to be an admin install or extraction, its just to create a bundle that can be installed without an internet connection. I think there was a thread about it a few weeks back. I reckon it would be a good feature request, if there isn't one already, to have an extract switch for the scenario you suggest. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Wed 8/15/2012 4:04 PM To: General discussion for Windows Installer XML toolset.(wix-users@lists.sourceforge.net) Subject: [WiX-users] Burn /layout doesn't extract embedded resources frombundle IIRC this worked a while ago with older WiX v3.6 builds but hasn't for a while. If I run my Bundle with the /layout switch, it will download the .NET 4.0 Client Profile redistributable any other MSI's or MSPs I have in my bundle which have a DownloadURL specified (and Compressed=no set). However any MSI or MSP which doesn't have a DownloadURL specified is embedded in the Bundle using the Compressed=yes attribute isn't extracted during the layout procedure. This means anyone who wants to use the MSI directly for managed deployment has to hack around with the Bundle to get at the MSI (run it as if to install, wait until it's extracted the embedded files to its temp directory, check the log to find the temp directory then copy them out of the temp directory cancel the install). Code: Chain PackageGroupRef Id=NetFx40ClientRedist/ MspPackage Id=SharedContentPatch SourceFile=..\..\..\install\VESharedContent.msp After=NetFx40ClientRedist Compressed=no DisplayInternalUI=yes DownloadUrl=http://cdn.iesve.com/ve/VESharedContent.msp; InstallSize=1 PerMachine=yes Permanent=yes Vital=yes Slipstream=yes / MsiPackage Id=ve SourceFile=..\..\..\install\ve2012.msi After=SharedContentPatch Compressed=yes DisplayInternalUI=yes ForcePerMachine=yes Permanent=no Visible=no Vital=yes / MsiPackage Id=SketchUpPlugin SourceFile=..\..\..\install\SketchUpPlugin2012.msi After=ve Compressed=yes DisplayInternalUI=yes ForcePerMachine=yes Permanent=no Visible=no Vital=no InstallCondition=SketchUp8Installed = 1 OR SketchUp7Installed = 1 OR SketchUp6Installed = 1 / MsiPackage Id=RevitPlugin SourceFile=..\..\..\install\RevitPlugin2012.msi After=SketchUpPlugin Compressed=yes DisplayInternalUI=yes ForcePerMachine=yes Permanent=no Visible=no Vital=no InstallCondition=RAC2008Installed = 1 OR RME2008Installed = 1 OR RAC2009Installed = 1 OR RME2009Installed = 1 OR RAC2009x64Installed = 1 OR RME2009x64Installed = 1 OR RAC2010Installed = 1 OR RME2010Installed = 1 OR RAC2010x64Installed = 1 OR RME2010x64Installed = 1 OR RAC2011Installed = 1 OR RME2011Installed = 1 OR RAC2011x64Installed = 1 OR RME2011x64Installed = 1 OR RAC2012Installed = 1 OR RME2012Installed = 1 OR RAC2012x64Installed = 1 OR RME2012x64Installed = 1 OR RAC2013Installed = 1 OR RME2013Installed = 1 OR RAC2013x64Installed = 1 OR RME2013x64Installed = 1 / /Chain Log - http://upload.iesve.com/downloads/burn_issues/layout.log Should I bug report this? Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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
[WiX-users] Burn - .NET 4.0 client profile fails to install on Windows XP 64-bit
My Burn package includes the .NET 4.0 client profile from WiXNetFxExtension like so: PackageGroupRef Id=NetFx40ClientRedist/ When I attempt to install on XP64, I get a spurious error in Burn 0x800713ec - Asia Log file - http://upload.iesve.com/downloads/burn_issues/xp64_net4clientprofile.log Burn screenshot - http://upload.iesve.com/downloads/burn_issues/xp64_burn_net4_error.png When I run the .NET 4.0 client profile redistributable manually on this machine I get the following error - http://upload.iesve.com/downloads/burn_issues/xp64_net4_install.png which suggests the PackageGroupRef in WiXNetFxExtension isn't installing a pre-requisite. The XP64 VM I'm testing on is up to date with Windows Updates. Should I bug report this? Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn - .NET 4.0 client profile fails to install onWindows XP 64-bit
WIC is definitely a prereq on Windows 2003 server so it probably is on Win xp 64 bit too. Looks like a bug to me. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Wed 8/15/2012 5:23 PM To: General discussion for Windows Installer XML toolset.(wix-users@lists.sourceforge.net) Subject: [WiX-users] Burn - .NET 4.0 client profile fails to install onWindows XP 64-bit My Burn package includes the .NET 4.0 client profile from WiXNetFxExtension like so: PackageGroupRef Id=NetFx40ClientRedist/ When I attempt to install on XP64, I get a spurious error in Burn 0x800713ec - Asia Log file - http://upload.iesve.com/downloads/burn_issues/xp64_net4clientprofile.log Burn screenshot - http://upload.iesve.com/downloads/burn_issues/xp64_burn_net4_error.png When I run the .NET 4.0 client profile redistributable manually on this machine I get the following error - http://upload.iesve.com/downloads/burn_issues/xp64_net4_install.png which suggests the PackageGroupRef in WiXNetFxExtension isn't installing a pre-requisite. The XP64 VM I'm testing on is up to date with Windows Updates. Should I bug report this? Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn - .NET 4.0 client profile fails to install onWindows XP 64-bit
.Net requires SP3 which x64does not have. Technically you can install it on machines with SP2 but requires additional prereqisites. WIC is one of them. Wes Sent from my iPad On 2012-08-15, at 1:29 PM, Peter Shirtcliffe pshirtcli...@sdl.com wrote: WIC is definitely a prereq on Windows 2003 server so it probably is on Win xp 64 bit too. Looks like a bug to me. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Wed 8/15/2012 5:23 PM To: General discussion for Windows Installer XML toolset.(wix-users@lists.sourceforge.net) Subject: [WiX-users] Burn - .NET 4.0 client profile fails to install onWindows XP 64-bit My Burn package includes the .NET 4.0 client profile from WiXNetFxExtension like so: PackageGroupRef Id=NetFx40ClientRedist/ When I attempt to install on XP64, I get a spurious error in Burn 0x800713ec - Asia Log file - http://upload.iesve.com/downloads/burn_issues/xp64_net4clientprofile.log Burn screenshot - http://upload.iesve.com/downloads/burn_issues/xp64_burn_net4_error.png When I run the .NET 4.0 client profile redistributable manually on this machine I get the following error - http://upload.iesve.com/downloads/burn_issues/xp64_net4_install.png which suggests the PackageGroupRef in WiXNetFxExtension isn't installing a pre-requisite. The XP64 VM I'm testing on is up to date with Windows Updates. Should I bug report this? Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WiX Suppress ICE Validation When Using MSBUILD At The Commandline
Hi everyone I've got a Visual Studio solution that contains two WiX Projects. In Visual Studio, I set the project properties to ignore the nearly-400 ICE30 output by light. The WiX code was written by another programmer and I don't currently have the time or the mandate to rewrite it so that it doesn't have any ICE errors. We were previously building it with Candle and Light, thus allowing us to do a -sice for ICE30. Right now, I'm trying to get it to work with MSBUILD at the commandline since we are changing our build process. I've managed to find all of the other commandline parameters I need through Google (such as setting the preprocessor variables) but I can't figure out how to set the parameter to suppress a specific ICE validation. Here are the two commandlines I've tried: MSBUILD C:\Code\Moxie\Dev\6.10\Build Workflow\Installation\Moxie WiX\Moxie WiX.sln /p:DefineConstants=BINARIESFOLDER=C:\Code\Moxie\Dev\6.10\Build Workflow\Binaries;LIBRARYFOLDER=C:\Code\Moxie\Dev\6.10\Build Workflow\Library;MANUALSFOLDER=C:\Code\Moxie\Dev\6.10\Build Workflow\Manuals;RESOURCESFOLDER=C:\Code\Moxie\Dev\6.10\Build Workflow\Installation\Installation Resources;MODULEZIPSFOLDER=C:\Code\Moxie\Dev\6.10\Build Workflow\Module Zips;PRODUCTVERSION=6.255.1.1;;OutputDir=C:\Code\Moxie\Dev\6.10\Build Workflow\MSIs;sice=30 MSBUILD C:\Code\Moxie\Dev\6.10\Build Workflow\Installation\Moxie WiX\Moxie WiX.sln /p:DefineConstants=BINARIESFOLDER=C:\Code\Moxie\Dev\6.10\Build Workflow\Binaries;LIBRARYFOLDER=C:\Code\Moxie\Dev\6.10\Build Workflow\Library;MANUALSFOLDER=C:\Code\Moxie\Dev\6.10\Build Workflow\Manuals;RESOURCESFOLDER=C:\Code\Moxie\Dev\6.10\Build Workflow\Installation\Installation Resources;MODULEZIPSFOLDER=C:\Code\Moxie\Dev\6.10\Build Workflow\Module Zips;PRODUCTVERSION=6.255.1.1; /p:OutputDir=C:\Code\Moxie\Dev\6.10\Build Workflow\MSIs /p:sice=30 Any thoughts about what I'm doing wrong? Many thanks - Shaun The information in this e-mail is intended solely for the addressee and access by anyone else is unauthorized. Omnivex accepts no liability for the content of this e-mail, or for the consequences of any actions taken on the basis of the information provided. Any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. Omnivex makes no warranties, express or implied and is not responsible for errors or omissions. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn - .NET 4.0 client profile fails to install onWindows XP 64-bit
Bug reported - https://sourceforge.net/tracker/?func=detailaid=3557976group_id=105970atid=642714 Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: 15 August 2012 17:33 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn - .NET 4.0 client profile fails to install onWindows XP 64-bit WIC is definitely a prereq on Windows 2003 server so it probably is on Win xp 64 bit too. Looks like a bug to me. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Wed 8/15/2012 5:23 PM To: General discussion for Windows Installer XML toolset.(wix-users@lists.sourceforge.net) Subject: [WiX-users] Burn - .NET 4.0 client profile fails to install onWindows XP 64-bit My Burn package includes the .NET 4.0 client profile from WiXNetFxExtension like so: PackageGroupRef Id=NetFx40ClientRedist/ When I attempt to install on XP64, I get a spurious error in Burn 0x800713ec - Asia Log file - http://upload.iesve.com/downloads/burn_issues/xp64_net4clientprofile.log Burn screenshot - http://upload.iesve.com/downloads/burn_issues/xp64_burn_net4_error.png When I run the .NET 4.0 client profile redistributable manually on this machine I get the following error - http://upload.iesve.com/downloads/burn_issues/xp64_net4_install.png which suggests the PackageGroupRef in WiXNetFxExtension isn't installing a pre-requisite. The XP64 VM I'm testing on is up to date with Windows Updates. Should I bug report this? Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn - .NET 4.0 client profile fails to install on Windows XP 64-bit
XP64 is a retrofitted Server 2003 x64. It has nothing to do with XP32 service packs. Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Wesley Manning [mailto:wmann...@dynagen.ca] Sent: 15 August 2012 17:58 To: General discussion for Windows Installer XML toolset. Cc: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Burn - .NET 4.0 client profile fails to install onWindows XP 64-bit .Net requires SP3 which x64does not have. Technically you can install it on machines with SP2 but requires additional prereqisites. WIC is one of them. Wes Sent from my iPad On 2012-08-15, at 1:29 PM, Peter Shirtcliffe pshirtcli...@sdl.com wrote: WIC is definitely a prereq on Windows 2003 server so it probably is on Win xp 64 bit too. Looks like a bug to me. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Wed 8/15/2012 5:23 PM To: General discussion for Windows Installer XML toolset.(wix-users@lists.sourceforge.net) Subject: [WiX-users] Burn - .NET 4.0 client profile fails to install onWindows XP 64-bit My Burn package includes the .NET 4.0 client profile from WiXNetFxExtension like so: PackageGroupRef Id=NetFx40ClientRedist/ When I attempt to install on XP64, I get a spurious error in Burn 0x800713ec - Asia Log file - http://upload.iesve.com/downloads/burn_issues/xp64_net4clientprofile.log Burn screenshot - http://upload.iesve.com/downloads/burn_issues/xp64_burn_net4_error.png When I run the .NET 4.0 client profile redistributable manually on this machine I get the following error - http://upload.iesve.com/downloads/burn_issues/xp64_net4_install.png which suggests the PackageGroupRef in WiXNetFxExtension isn't installing a pre-requisite. The XP64 VM I'm testing on is up to date with Windows Updates. Should I bug report this? Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer - - Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security,
[WiX-users] Tools used within a WCF service
Hi everyone, Can the WiX tools (e.g. candle, light, torch) be used within a WCF service method? Or is there some limitation or gotcha I should be aware of? I am wanting to answer an architectural question some of us had about the future of my InstallerBuilder (hereafter, IB) front end. This is basically a way to enforce installations of the right sort for of our environments; IB builds a WXS file behind the scenes using some user choice but enforces all the other constraints. Since to allow various teams to use IB and yet not stomp on each other's work easily we decided to temporarily (?) use mutexes and a commonly installed copy (w/ WiX, of course) on a small file-sharing type server that folks would log onto to use. This does not scale too well, and so we wondered if we could, long term, turn some of IB (like the creation of WXS files and the compile and link stages) into a bunch of WCF services that could be called from a front end on each machine. Keith Douglas Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 keith.doug...@statcan.gc.ca Telephone | Téléphone 613-951-4405 Facsimile | Télécopieur 613-951-1966 Government of Canada | Gouvernement du Canada -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Clarification on InstallCondition and DetectCondition
I am a bit confused on the use of the InstallCondition and DetectCondition attributes on the ExePackage element and would like some clarification on my understanding. Would you use InstallCondition to restrict the component being installed on various OS configurations e.g. one package for x86 and another for x64 or only install package on Windows XP? Then DetectCondition to actually determine whether the package is already installed? Regards Neil Neil Sleightholm X2 Systems Limited n...@x2systems.commailto:n...@x2systems.com -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Creating empty registry key under HKCU
Does anyone know the best method for writing an empty Registry key under
HKCU? This code isn't cutting it:
*ComponentGroup Id=ProductComponents Directory=PersonalFolder
Component Id=CMP_RegistryWrite
Guid={3BF28DC8-4AFC-43E8-B605-AA6456B06921}
RegistryKey
Root=HKCU
Key=Software\CompanyABC
ForceCreateOnInstall=yes
/RegistryKey
/Component
/ComponentGroup*
I am getting: ICE38: Component CMP_RegistryWrite installs to user profile.
It must use a registry key under HKCU as its KeyPath, not a file.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-empty-registry-key-under-HKCU-tp7579893.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
