Re: [WiX-users] How to dynamically create check boxes in WIX UI
You can't 'dynamically generate' UI under Windows Installer without a custom UI handler. You can, however, have a standard dialog and simply disable/hide controls that are not in use. Check the ControlCondition table - http://msdn.microsoft.com/en-us/library/aa368035(VS.85).aspx On Mon, Jul 7, 2008 at 12:43 AM, Nimisha Saboo [EMAIL PROTECTED] wrote: Hi, I am new to Wix programming. I need to dynamically generate check boxes in WIX UI, depending on the number of some external parameters. Is there a way to accomplish this? Thanks and regards, Nimisha - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Calling a custom action from a push button
Thanks Bob, Really appreciate it... Andrew Lamb If you've received this email by mistake, we're sorry for bothering you. It may contain information that's confidential, so please delete it without sharing it. And if you let us know, we can try to stop it from happening again. Thank you. We may monitor any emails sent or received by us, or on our behalf. If we do, this will be in line with relevant law and our own policies. Sage (UK) Limited. Registered in England at North Park, Newcastle upon Tyne, NE13 9AA. Registered number 1045967. - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Keep optional directory on upgrade
Our application is available in two different versions - one with embedded Java Runtime Environment (JRE) and one without. The JRE is nothing else than a directory in the installation directory (no special registry settings). We don't provide special update packages (containing just the differences), but instead all packages we provide are complete packages (without thinking about the JRE). When a user first installs a version with JRE and later a new version without JRE, the jre-directory is removed/uninstalled. What would be the best solution to uninstall the JRE only if the user uninstalls the application using Add/Remove, but not when installing a newer version on top? Thanks in advance, Tom - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] TRCH0001 : Item has already been added.
Hi, Any idea what causes this? I'm trying to follow the steps defined here: http://blogs.msdn.com/pmarcu/archive/2007/06/28/sample-patch.aspx to create a patch for my application, using wix 3. I've created two wixout files, using light.exe -xo ... When I try and create a transform, torch says: torch.exe : error TRCH0001 : Item has already been added. Key in dictionary: 'ADMIN_INSTALL_SPEECH' Key being added: 'ADMIN_INSTALL_SPEECH' Does anyone know why this might happen? Thanks, Simon CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. Logotron is a limited company registered in England, number 04113866. The registered office is Logotron Ltd, Denny Lodge Business Park, Chittering, Cambridge, CB25 9PH. - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to dynamically create check boxes in WIX UI
Jason- MSI is a relational database that supports temporary records. It's entirely possible to dynamically emit controls at runtime: http://blog.deploymentengineering.com/2008/07/dynamic-windows-installer-ui.html But otherwise you are correct. The general practice is to have a bunch of disabled controls that are dynamically enabled. Regards, Chris Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me --- On Mon, 7/7/08, Jason [EMAIL PROTECTED] wrote: From: Jason [EMAIL PROTECTED] Subject: Re: [WiX-users] How to dynamically create check boxes in WIX UI To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Monday, July 7, 2008, 1:43 AM You can't 'dynamically generate' UI under Windows Installer without a custom UI handler. You can, however, have a standard dialog and simply disable/hide controls that are not in use. Check the ControlCondition table - http://msdn.microsoft.com/en-us/library/aa368035(VS.85).aspx On Mon, Jul 7, 2008 at 12:43 AM, Nimisha Saboo [EMAIL PROTECTED] wrote: Hi, I am new to Wix programming. I need to dynamically generate check boxes in WIX UI, depending on the number of some external parameters. Is there a way to accomplish this? Thanks and regards, Nimisha - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WixUI_nl-nl.wxl missing entries for latest build (4227.0)
The latest build (4227.0) has an outdated UI localization file for Dutch.
Missing entries below.
Danny
---
?xml version=1.0 encoding=utf-8?
!--
Copyright (c) Microsoft Corporation. All rights reserved.
The use and distribution terms for this software are covered by the
Common Public License 1.0 (http://opensource.org/licenses/cpl.php)
which can be found in the file CPL.TXT at the root of this distribution.
By using this software in any fashion, you are agreeing to be bound by
the terms of this license.
You must not remove this notice, or any other, from this software.
--
WixLocalization Culture=nl-nl
xmlns=http://schemas.microsoft.com/wix/2003/11/localization;
String Id=AdvancedWelcomeEulaDlg_Title Overridable=yes[ProductName]
Setup/String
String Id=AdvancedWelcomeEulaDlgBannerBitmap
Overridable=yesWixUI_Bmp_Banner/String
String Id=AdvancedWelcomeEulaDlgTitle
Overridable=yes{\WixUI_Font_Title}Lees aub de [ProductName]
Licentie-overeenkomst/String
String Id=AdvancedWelcomeEulaDlgLicenseAcceptedCheckBox
Overridable=yesIk amp;aanvaard de voorwaarden in de
Licentie-overeenkomst/String
String Id=AdvancedWelcomeEulaDlgDescriptionPerMachine
Overridable=yesKlik installeer om het product te installeren met de
standaard opties voor alle gebruikers. Klik geavanceerd om de opties voor de
installatie te wijzigen./String
String Id=AdvancedWelcomeEulaDlgDescriptionPerUser Overridable=yesKlik
installeer om het product te installeren met de standaard opties enkel voor de
huidige gebruiker. Klik geavanceerd om de opties voor de installatie te
wijzigen./String
String Id=AdvancedWelcomeEulaDlgInstall
Overridable=yesamp;Installeer/String
String Id=AdvancedWelcomeEulaDlgAdvanced
Overridable=yesGeavanceeramp;d/String
String Id=Advanced_Font_Normal_Size Overridable=yes8/String
String Id=Advanced_Font_Bigger_Size Overridable=yes12/String
String Id=Advanced_Font_Title_Size Overridable=yes9/String
String Id=Advanced_Font_Emphasized_Size Overridable=yes8/String
String Id=Advanced_Font_FaceName Overridable=yesTahoma/String
String Id=FeaturesDlg_Title Overridable=yes[ProductName] Setup/String
String Id=FeaturesDlgTree Overridable=yesProduct opties/String
String Id=FeaturesDlgBannerBitmap
Overridable=yesWixUI_Bmp_Banner/String
String Id=FeaturesDlgDescription Overridable=yesSelecteer de manier
waarop u het product wil installeren./String
String Id=FeaturesDlgTitle Overridable=yes{\WixUI_Font_Title}Product
Opties/String
String Id=FeaturesDlgItemDescription
Overridable=yesFeaturesDlgItemDescription/String
String Id=FeaturesDlgItemSize
Overridable=yesFeaturesDlgItemSize/String
String Id=FeaturesDlgInstall Overridable=yesamp;Installeer/String
String Id=FeaturesDlgChange Overridable=yesamp;Wijzig/String
String Id=InstallScopeDlg_Title Overridable=yes[ProductName]
Setup/String
String Id=InstallScopeDlgBannerBitmap
Overridable=yesWixUI_Bmp_Banner/String
String Id=InstallScopeDlgDescription Overridable=yesSelecteer de
installatiewijze en map/String
String Id=InstallScopeDlgTitle
Overridable=yes{\WixUI_Font_Title}Installatiewijze/String
String Id=InstallScopeDlgPerUser
Overridable=yes{\WixUI_Font_Emphasized}Installeer amp;enkel voor de huidige
gebruiker: ([USERNAME])/String
String Id=InstallScopeDlgPerUserDescription
Overridable=yes[ProductName] wordt geïnstalleerd in een map per gebruiker en
is enkel beschikbaar voor uw huidig gebruikersaccount. De installatie vereist
geen administrator rechten./String
String Id=InstallScopeDlgNoPerUserDescription
Overridable=yes[ProductName] ondersteunt geen installatie per
gebruiker./String
String Id=InstallScopeDlgPerMachine
Overridable=yes{\WixUI_Font_Emphasized}Installeer voor alle gebruikers van
deze amp;computer/String
String Id=InstallScopeDlgPerMachineDescription
Overridable=yes[ProductName] wordt standaard geïnstalleerd in een
gemeenschappelijke map en is beschikbaar voor alle gebruikers. U kan de
installatiemap wijzigen. Hiervoor zijn locale administrator rechten
nodig./String
String Id=InstallScopeDlgFolderLabel Overridable=yesInstallatie
amp;map:/String
String Id=InstallScopeDlgChange Overridable=yesamp;Wijzig.../String
String Id=InvalidDirDlg_Title Overridable=yes[ProductName]
Setup/String
String Id=InvalidDirDlgText Overridable=yesInstallatiemap moet op een
locale harde schijf./String
String Id=InvalidDirDlgIcon Overridable=yesWixUI_Ico_Info/String
String Id=InvalidDirDlgIconTooltip Overridable=yesInformation
icon/String
String Id=MaintenanceTypeDlgRemoveDisabledText
Overridable=yes[ProductName] kan niet worden verwijderd./String
String Id=MaintenanceTypeDlgRepairDisabledText
Overridable=yes[ProductName] kan niet worden hersteld./String
String Id=UITextNewFolder Overridable=yesMap|Nieuwe Map/String
/WixLocalization
===
30 september Cevi
Re: [WiX-users] Installing different files depending on ComputerName (Wix 2)
On Sun, 06 Jul 2008, jmcfadyen wrote: what I would do is create 3 components for your 3 certs. Condition each of your components with a valid condition such as PROD=true TESt=true etc then using an Immediate CA chop up the computer name or domain name env var's then use the results to set the desired conditions to match the components conditions. [..] Could all of these three components all install files into the same place on the target system (and then it's up to me to make sure only one gets fired off at once?) Or should I install them to different places, an then have a commit CA move them into the correct place? Nick - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to dynamically create check boxes in WIX UI
You are correct. I always forget about temporary rows.. However like your post details that still requires a custom action and doesn't get the benefit of validation. On Mon, Jul 7, 2008 at 10:08 AM, Christopher Painter [EMAIL PROTECTED] wrote: Jason- MSI is a relational database that supports temporary records. It's entirely possible to dynamically emit controls at runtime: http://blog.deploymentengineering.com/2008/07/dynamic-windows-installer-ui.html But otherwise you are correct. The general practice is to have a bunch of disabled controls that are dynamically enabled. Regards, Chris Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me --- On Mon, 7/7/08, Jason [EMAIL PROTECTED] wrote: From: Jason [EMAIL PROTECTED] Subject: Re: [WiX-users] How to dynamically create check boxes in WIX UI To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Monday, July 7, 2008, 1:43 AM You can't 'dynamically generate' UI under Windows Installer without a custom UI handler. You can, however, have a standard dialog and simply disable/hide controls that are not in use. Check the ControlCondition table - http://msdn.microsoft.com/en-us/library/aa368035(VS.85).aspx On Mon, Jul 7, 2008 at 12:43 AM, Nimisha Saboo [EMAIL PROTECTED] wrote: Hi, I am new to Wix programming. I need to dynamically generate check boxes in WIX UI, depending on the number of some external parameters. Is there a way to accomplish this? Thanks and regards, Nimisha - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to dynamically create check boxes in WIX UI
True. I just wanted to clarify that it `could` be done and I'm sure with the proper attention to detail, could even be done reliably if it was ever truely needed. Regardless, the original poster is probably more interested in some way of dynamically generating WiX UI XML from an external dataset and then passing it on to candle anyways. The ControlConditions scenario can work, provided that the disabled controls can exist in the MSI. I've worked at companies where this would not be allowed because it would be a security violation to have certain product line capabilities exist within a package (and visible via orca) where they don't belong even if they are disabled. Regards, Chris Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me --- On Mon, 7/7/08, Jason [EMAIL PROTECTED] wrote: From: Jason [EMAIL PROTECTED] Subject: Re: [WiX-users] How to dynamically create check boxes in WIX UI To: [EMAIL PROTECTED], General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Monday, July 7, 2008, 12:24 PM You are correct. I always forget about temporary rows.. However like your post details that still requires a custom action and doesn't get the benefit of validation. On Mon, Jul 7, 2008 at 10:08 AM, Christopher Painter [EMAIL PROTECTED] wrote: Jason- MSI is a relational database that supports temporary records. It's entirely possible to dynamically emit controls at runtime: http://blog.deploymentengineering.com/2008/07/dynamic-windows-installer-ui.html But otherwise you are correct. The general practice is to have a bunch of disabled controls that are dynamically enabled. Regards, Chris Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me --- On Mon, 7/7/08, Jason [EMAIL PROTECTED] wrote: From: Jason [EMAIL PROTECTED] Subject: Re: [WiX-users] How to dynamically create check boxes in WIX UI To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Monday, July 7, 2008, 1:43 AM You can't 'dynamically generate' UI under Windows Installer without a custom UI handler. You can, however, have a standard dialog and simply disable/hide controls that are not in use. Check the ControlCondition table - http://msdn.microsoft.com/en-us/library/aa368035(VS.85).aspx On Mon, Jul 7, 2008 at 12:43 AM, Nimisha Saboo [EMAIL PROTECTED] wrote: Hi, I am new to Wix programming. I need to dynamically generate check boxes in WIX UI, depending on the number of some external parameters. Is there a way to accomplish this? Thanks and regards, Nimisha - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net
[WiX-users] Integration of WiX v3 on team build server
Hi, I want compile WiX projects on team build server, but I don't want install WiX on build server, so I am planning add all needed files to source control. I have some problem when I am compile wixproj file. wixproj file contains those 2 lines: WixTargetsPath Condition= '$(WixTargetsPath)' == '' $(MSBuildExtensionsPath)\Microsoft\WiX\v3.0\Wix.targets/WixTargetsPath Import Project=$(WixTargetsPath) / Since WiX not installed on build machine I override CoreCompile target of Microsoft.TeamFoundation.Build.targets in my TFSBuild.proj file, so I can transfer WixTargetsPath to MSBuild task. The problems that build failed since I have error: Solution file warning MSB4122: Scanning project dependencies for project MyProj.wixProj failed. Blablabla since WixTargetsPath not exist. What I need to do to resolve this problem? Thanks in advance, Dima - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Integration of WiX v3 on team build server
How would you expect the build server to be able to use the WiX tools without them being installed? I mean, strictly speaking you don't need to install them, just make them available. But what would be the benefit? Chris On Mon, Jul 7, 2008 at 4:01 PM, Dmitry Berkovich [EMAIL PROTECTED] wrote: Hi, I want compile WiX projects on team build server, but I don't want install WiX on build server, so I am planning add all needed files to source control. I have some problem when I am compile wixproj file. wixproj file contains those 2 lines: WixTargetsPath Condition= '$(WixTargetsPath)' == '' $(MSBuildExtensionsPath)\Microsoft\WiX\v3.0\Wix.targets/WixTargetsPath Import Project=$(WixTargetsPath) / Since WiX not installed on build machine I override CoreCompile target of Microsoft.TeamFoundation.Build.targets in my TFSBuild.proj file, so I can transfer WixTargetsPath to MSBuild task. The problems that build failed since I have error: Solution file warning MSB4122: Scanning project dependencies for project MyProj.wixProj failed. Blablabla since WixTargetsPath not exist. What I need to do to resolve this problem? Thanks in advance, Dima - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Integration of WiX v3 on team build server
I can add wix.targets, light.exe, etc to source control, so build server will take all this files with my sources, I will pass all required parameters to wix.targets file, so I will able to compile link wix project without installing WiX on build machine. Dima On Mon, Jul 7, 2008 at 11:25 PM, Christopher Karper [EMAIL PROTECTED] wrote: How would you expect the build server to be able to use the WiX tools without them being installed? I mean, strictly speaking you don't need to install them, just make them available. But what would be the benefit? Chris On Mon, Jul 7, 2008 at 4:01 PM, Dmitry Berkovich [EMAIL PROTECTED] wrote: Hi, I want compile WiX projects on team build server, but I don't want install WiX on build server, so I am planning add all needed files to source control. I have some problem when I am compile wixproj file. wixproj file contains those 2 lines: WixTargetsPath Condition= '$(WixTargetsPath)' == '' $(MSBuildExtensionsPath)\Microsoft\WiX\v3.0\Wix.targets/WixTargetsPath Import Project=$(WixTargetsPath) / Since WiX not installed on build machine I override CoreCompile target of Microsoft.TeamFoundation.Build.targets in my TFSBuild.proj file, so I can transfer WixTargetsPath to MSBuild task. The problems that build failed since I have error: Solution file warning MSB4122: Scanning project dependencies for project MyProj.wixProj failed. Blablabla since WixTargetsPath not exist. What I need to do to resolve this problem? Thanks in advance, Dima - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Integration of WiX v3 on team build server
2 big benefits I can think of: 1) Machine maintenance If you have 5 build machines, you don't have to update WiX on all 5 of the build machines. The synch process pulls down the appropriate WiX version during the build process. 2) Large projects that share Build machines don't need to all share the same version of WiX. Individual projects within a greater product build process could use different /specific versions of WiX. If 1 of your 50 projects needs to move to a later version of WiX (bug fixes, feature enhancements, etc...) it can do so without wondering what side effects might be introduced to the other projects should they all have moved to the later version of WiX. Etc... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: Monday, July 07, 2008 3:25 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Integration of WiX v3 on team build server How would you expect the build server to be able to use the WiX tools without them being installed? I mean, strictly speaking you don't need to install them, just make them available. But what would be the benefit? Chris On Mon, Jul 7, 2008 at 4:01 PM, Dmitry Berkovich [EMAIL PROTECTED] wrote: Hi, I want compile WiX projects on team build server, but I don't want install WiX on build server, so I am planning add all needed files to source control. I have some problem when I am compile wixproj file. wixproj file contains those 2 lines: WixTargetsPath Condition= '$(WixTargetsPath)' == '' $(MSBuildExtensionsPath)\Microsoft\WiX\v3.0\Wix.targets/WixTargetsPath Import Project=$(WixTargetsPath) / Since WiX not installed on build machine I override CoreCompile target of Microsoft.TeamFoundation.Build.targets in my TFSBuild.proj file, so I can transfer WixTargetsPath to MSBuild task. The problems that build failed since I have error: Solution file warning MSB4122: Scanning project dependencies for project MyProj.wixProj failed. Blablabla since WixTargetsPath not exist. What I need to do to resolve this problem? Thanks in advance, Dima - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Integration of WiX v3 on team build server
Interesting read... http://www.testearly.com/2006/07/25/the-magic-machine-antipattern/ Personally I build the build box. There are some really cool things you can do with virtualization and TFS to break the magic machine antipattern. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me --- On Mon, 7/7/08, Christopher Karper [EMAIL PROTECTED] wrote: From: Christopher Karper [EMAIL PROTECTED] Subject: Re: [WiX-users] Integration of WiX v3 on team build server To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Monday, July 7, 2008, 3:25 PM How would you expect the build server to be able to use the WiX tools without them being installed? I mean, strictly speaking you don't need to install them, just make them available. But what would be the benefit? Chris On Mon, Jul 7, 2008 at 4:01 PM, Dmitry Berkovich [EMAIL PROTECTED] wrote: Hi, I want compile WiX projects on team build server, but I don't want install WiX on build server, so I am planning add all needed files to source control. I have some problem when I am compile wixproj file. wixproj file contains those 2 lines: WixTargetsPath Condition= '$(WixTargetsPath)' == '' $(MSBuildExtensionsPath)\Microsoft\WiX\v3.0\Wix.targets/WixTargetsPath Import Project=$(WixTargetsPath) / Since WiX not installed on build machine I override CoreCompile target of Microsoft.TeamFoundation.Build.targets in my TFSBuild.proj file, so I can transfer WixTargetsPath to MSBuild task. The problems that build failed since I have error: Solution file warning MSB4122: Scanning project dependencies for project MyProj.wixProj failed. Blablabla since WixTargetsPath not exist. What I need to do to resolve this problem? Thanks in advance, Dima - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Integration of WiX v3 on team build server
Jonh, This is a reason that I am trying to inegrate WiX on build server in this way, Thanks that you wrote those reason. Did anybody have any idea how to do it? I have found some ugly way to pass parameters: I just write some task that add all my required properties to task.BuildEngine.GlobalProperties collection, but I am doing it by reflection, since task.BuildEngine implement IBuildEngine inerface, where class that implement this interface is : Microsoft.Build.BuildEngine.EngineProxy. So I am looking for more nice way to integrate WiX to team build. Dima On Mon, Jul 7, 2008 at 11:33 PM, John Nannenga [EMAIL PROTECTED] wrote: 2 big benefits I can think of: 1) Machine maintenance If you have 5 build machines, you don't have to update WiX on all 5 of the build machines. The synch process pulls down the appropriate WiX version during the build process. 2) Large projects that share Build machines don't need to all share the same version of WiX. Individual projects within a greater product build process could use different /specific versions of WiX. If 1 of your 50 projects needs to move to a later version of WiX (bug fixes, feature enhancements, etc...) it can do so without wondering what side effects might be introduced to the other projects should they all have moved to the later version of WiX. Etc... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: Monday, July 07, 2008 3:25 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Integration of WiX v3 on team build server How would you expect the build server to be able to use the WiX tools without them being installed? I mean, strictly speaking you don't need to install them, just make them available. But what would be the benefit? Chris On Mon, Jul 7, 2008 at 4:01 PM, Dmitry Berkovich [EMAIL PROTECTED] wrote: Hi, I want compile WiX projects on team build server, but I don't want install WiX on build server, so I am planning add all needed files to source control. I have some problem when I am compile wixproj file. wixproj file contains those 2 lines: WixTargetsPath Condition= '$(WixTargetsPath)' == '' $(MSBuildExtensionsPath)\Microsoft\WiX\v3.0\Wix.targets/WixTargetsPath Import Project=$(WixTargetsPath) / Since WiX not installed on build machine I override CoreCompile target of Microsoft.TeamFoundation.Build.targets in my TFSBuild.proj file, so I can transfer WixTargetsPath to MSBuild task. The problems that build failed since I have error: Solution file warning MSB4122: Scanning project dependencies for project MyProj.wixProj failed. Blablabla since WixTargetsPath not exist. What I need to do to resolve this problem? Thanks in advance, Dima - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to use Wix FilesInUse dialog?
I picked this dialog from some Wix UI scheme and it is now compiled into my project. However, I have no idea how to use it or how to get the system to invoke it !? Namely, during my testing, some other, system-provided dialog (i.e. not part of any UI that I added) pops up and offers to close the applications keeping the files open. When I click the button to proceed with that task dialog comes back with the message sorry but it couldn't kill the apps. Totally useless. Of course, then I use Task Manager to successfully kill the apps. I would prefer to avoid system-provided dialog and instead have my custom version of FilesInUse dialog invoked. Assuming that is somehow doable should I invoke my custom actions (i.e. call DoAction) on button clicks of that dialog to perform killing of apps, for example? Thanks for any input - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Integration of WiX v3 on team build server
I would imagine the best way to do this would be to manually edit your .wixproj files. Either change the reference to your WiX.targets file to be relative to the project directory, or set the WixTargetsPath in a Property/Property section. If you go that route, you can make it conditional on being a TFS build by using a statement similar to: PropertyGroup WixTargetsPath Condition= '$(TeamProject)' != '' ..\..\WiX\/triCeratTasksPath /PropertyGroup I don't know, it seems like it should work to me. Good luck! Chris On Mon, Jul 7, 2008 at 4:40 PM, Dmitry Berkovich [EMAIL PROTECTED] wrote: Jonh, This is a reason that I am trying to inegrate WiX on build server in this way, Thanks that you wrote those reason. Did anybody have any idea how to do it? I have found some ugly way to pass parameters: I just write some task that add all my required properties to task.BuildEngine.GlobalProperties collection, but I am doing it by reflection, since task.BuildEngine implement IBuildEngine inerface, where class that implement this interface is : Microsoft.Build.BuildEngine.EngineProxy. So I am looking for more nice way to integrate WiX to team build. Dima On Mon, Jul 7, 2008 at 11:33 PM, John Nannenga [EMAIL PROTECTED] wrote: 2 big benefits I can think of: 1) Machine maintenance If you have 5 build machines, you don't have to update WiX on all 5 of the build machines. The synch process pulls down the appropriate WiX version during the build process. 2) Large projects that share Build machines don't need to all share the same version of WiX. Individual projects within a greater product build process could use different /specific versions of WiX. If 1 of your 50 projects needs to move to a later version of WiX (bug fixes, feature enhancements, etc...) it can do so without wondering what side effects might be introduced to the other projects should they all have moved to the later version of WiX. Etc... -Original Message- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: Monday, July 07, 2008 3:25 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Integration of WiX v3 on team build server How would you expect the build server to be able to use the WiX tools without them being installed? I mean, strictly speaking you don't need to install them, just make them available. But what would be the benefit? Chris On Mon, Jul 7, 2008 at 4:01 PM, Dmitry Berkovich [EMAIL PROTECTED] wrote: Hi, I want compile WiX projects on team build server, but I don't want install WiX on build server, so I am planning add all needed files to source control. I have some problem when I am compile wixproj file. wixproj file contains those 2 lines: WixTargetsPath Condition= '$(WixTargetsPath)' == '' $(MSBuildExtensionsPath)\Microsoft\WiX\v3.0\Wix.targets/WixTargetsPath Import Project=$(WixTargetsPath) / Since WiX not installed on build machine I override CoreCompile target of Microsoft.TeamFoundation.Build.targets in my TFSBuild.proj file, so I can transfer WixTargetsPath to MSBuild task. The problems that build failed since I have error: Solution file warning MSB4122: Scanning project dependencies for project MyProj.wixProj failed. Blablabla since WixTargetsPath not exist. What I need to do to resolve this problem? Thanks in advance, Dima - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users
Re: [WiX-users] Integration of WiX v3 on team build server
I believe that WiX should just work with TFS since we use MSBuild. Admittedly, I haven't tried TFS builds before, but from what I understand, they're also driven by MSBuild. My guess is that you're not defining $(WixTargetsPath) early enough - you Import Project=yourproject.wixproj / before defining $(WixTargetsPath). If that's the case, you just need to make sure you define $(WixTargetsPath) before importing the wixproj file. Perhaps I'm misunderstanding your question, however. I do know that there are teams that successfully use TFS with building wixproj files, though, so it should work. Justin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dmitry Berkovich Sent: Monday, July 07, 2008 1:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Integration of WiX v3 on team build server Jonh, This is a reason that I am trying to inegrate WiX on build server in this way, Thanks that you wrote those reason. Did anybody have any idea how to do it? I have found some ugly way to pass parameters: I just write some task that add all my required properties to task.BuildEngine.GlobalProperties collection, but I am doing it by reflection, since task.BuildEngine implement IBuildEngine inerface, where class that implement this interface is : Microsoft.Build.BuildEngine.EngineProxy. So I am looking for more nice way to integrate WiX to team build. Dima On Mon, Jul 7, 2008 at 11:33 PM, John Nannenga [EMAIL PROTECTED] wrote: 2 big benefits I can think of: 1) Machine maintenance If you have 5 build machines, you don't have to update WiX on all 5 of the build machines. The synch process pulls down the appropriate WiX version during the build process. 2) Large projects that share Build machines don't need to all share the same version of WiX. Individual projects within a greater product build process could use different /specific versions of WiX. If 1 of your 50 projects needs to move to a later version of WiX (bug fixes, feature enhancements, etc...) it can do so without wondering what side effects might be introduced to the other projects should they all have moved to the later version of WiX. Etc... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: Monday, July 07, 2008 3:25 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Integration of WiX v3 on team build server How would you expect the build server to be able to use the WiX tools without them being installed? I mean, strictly speaking you don't need to install them, just make them available. But what would be the benefit? Chris On Mon, Jul 7, 2008 at 4:01 PM, Dmitry Berkovich [EMAIL PROTECTED] wrote: Hi, I want compile WiX projects on team build server, but I don't want install WiX on build server, so I am planning add all needed files to source control. I have some problem when I am compile wixproj file. wixproj file contains those 2 lines: WixTargetsPath Condition= '$(WixTargetsPath)' == '' $(MSBuildExtensionsPath)\Microsoft\WiX\v3.0\Wix.targets/WixTargetsPath Import Project=$(WixTargetsPath) / Since WiX not installed on build machine I override CoreCompile target of Microsoft.TeamFoundation.Build.targets in my TFSBuild.proj file, so I can transfer WixTargetsPath to MSBuild task. The problems that build failed since I have error: Solution file warning MSB4122: Scanning project dependencies for project MyProj.wixProj failed. Blablabla since WixTargetsPath not exist. What I need to do to resolve this problem? Thanks in advance, Dima - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential
Re: [WiX-users] Integration of WiX v3 on team build server
Or, if I were smarter, I'd suggest you put the PropertyGroup structure in your Team Build .proj file instead, without the condition at all. Chris On Mon, Jul 7, 2008 at 4:58 PM, Christopher Karper [EMAIL PROTECTED] wrote: I would imagine the best way to do this would be to manually edit your .wixproj files. Either change the reference to your WiX.targets file to be relative to the project directory, or set the WixTargetsPath in a Property/Property section. If you go that route, you can make it conditional on being a TFS build by using a statement similar to: PropertyGroup WixTargetsPath Condition= '$(TeamProject)' != '' ..\..\WiX\/triCeratTasksPath /PropertyGroup I don't know, it seems like it should work to me. Good luck! Chris On Mon, Jul 7, 2008 at 4:40 PM, Dmitry Berkovich [EMAIL PROTECTED] wrote: Jonh, This is a reason that I am trying to inegrate WiX on build server in this way, Thanks that you wrote those reason. Did anybody have any idea how to do it? I have found some ugly way to pass parameters: I just write some task that add all my required properties to task.BuildEngine.GlobalProperties collection, but I am doing it by reflection, since task.BuildEngine implement IBuildEngine inerface, where class that implement this interface is : Microsoft.Build.BuildEngine.EngineProxy. So I am looking for more nice way to integrate WiX to team build. Dima On Mon, Jul 7, 2008 at 11:33 PM, John Nannenga [EMAIL PROTECTED] wrote: 2 big benefits I can think of: 1) Machine maintenance If you have 5 build machines, you don't have to update WiX on all 5 of the build machines. The synch process pulls down the appropriate WiX version during the build process. 2) Large projects that share Build machines don't need to all share the same version of WiX. Individual projects within a greater product build process could use different /specific versions of WiX. If 1 of your 50 projects needs to move to a later version of WiX (bug fixes, feature enhancements, etc...) it can do so without wondering what side effects might be introduced to the other projects should they all have moved to the later version of WiX. Etc... -Original Message- From: [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: Monday, July 07, 2008 3:25 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Integration of WiX v3 on team build server How would you expect the build server to be able to use the WiX tools without them being installed? I mean, strictly speaking you don't need to install them, just make them available. But what would be the benefit? Chris On Mon, Jul 7, 2008 at 4:01 PM, Dmitry Berkovich [EMAIL PROTECTED] wrote: Hi, I want compile WiX projects on team build server, but I don't want install WiX on build server, so I am planning add all needed files to source control. I have some problem when I am compile wixproj file. wixproj file contains those 2 lines: WixTargetsPath Condition= '$(WixTargetsPath)' == '' $(MSBuildExtensionsPath)\Microsoft\WiX\v3.0\Wix.targets/WixTargetsPath Import Project=$(WixTargetsPath) / Since WiX not installed on build machine I override CoreCompile target of Microsoft.TeamFoundation.Build.targets in my TFSBuild.proj file, so I can transfer WixTargetsPath to MSBuild task. The problems that build failed since I have error: Solution file warning MSB4122: Scanning project dependencies for project MyProj.wixProj failed. Blablabla since WixTargetsPath not exist. What I need to do to resolve this problem? Thanks in advance, Dima - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting
Re: [WiX-users] Integration of WiX v3 on team build server
Just a thought but why not put the WiX MSI in TFS and then do a silent install of WiX at the start of the build. Then you get the best of both worlds, a standard WiX install and WiX being automatically updated on all build machines. Also, if the WiX tool set gets some new tools or config you don't need to figure out how they need to be installed. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Nannenga Sent: 07 July 2008 21:33 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Integration of WiX v3 on team build server 2 big benefits I can think of: 1) Machine maintenance If you have 5 build machines, you don't have to update WiX on all 5 of the build machines. The synch process pulls down the appropriate WiX version during the build process. 2) Large projects that share Build machines don't need to all share the same version of WiX. Individual projects within a greater product build process could use different /specific versions of WiX. If 1 of your 50 projects needs to move to a later version of WiX (bug fixes, feature enhancements, etc...) it can do so without wondering what side effects might be introduced to the other projects should they all have moved to the later version of WiX. Etc... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: Monday, July 07, 2008 3:25 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Integration of WiX v3 on team build server How would you expect the build server to be able to use the WiX tools without them being installed? I mean, strictly speaking you don't need to install them, just make them available. But what would be the benefit? Chris On Mon, Jul 7, 2008 at 4:01 PM, Dmitry Berkovich [EMAIL PROTECTED] wrote: Hi, I want compile WiX projects on team build server, but I don't want install WiX on build server, so I am planning add all needed files to source control. I have some problem when I am compile wixproj file. wixproj file contains those 2 lines: WixTargetsPath Condition= '$(WixTargetsPath)' == '' $(MSBuildExtensionsPath)\Microsoft\WiX\v3.0\Wix.targets/WixTargetsPat h Import Project=$(WixTargetsPath) / Since WiX not installed on build machine I override CoreCompile target of Microsoft.TeamFoundation.Build.targets in my TFSBuild.proj file, so I can transfer WixTargetsPath to MSBuild task. The problems that build failed since I have error: Solution file warning MSB4122: Scanning project dependencies for project MyProj.wixProj failed. Blablabla since WixTargetsPath not exist. What I need to do to resolve this problem? Thanks in advance, Dima - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Integration of WiX v3 on team build server
Can TFS do concurrent builds? If more than one build kicked off at the same time, that could be pretty bad. Chris On Mon, Jul 7, 2008 at 5:35 PM, Neil Sleightholm [EMAIL PROTECTED] wrote: Just a thought but why not put the WiX MSI in TFS and then do a silent install of WiX at the start of the build. Then you get the best of both worlds, a standard WiX install and WiX being automatically updated on all build machines. Also, if the WiX tool set gets some new tools or config you don't need to figure out how they need to be installed. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Nannenga Sent: 07 July 2008 21:33 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Integration of WiX v3 on team build server 2 big benefits I can think of: 1) Machine maintenance If you have 5 build machines, you don't have to update WiX on all 5 of the build machines. The synch process pulls down the appropriate WiX version during the build process. 2) Large projects that share Build machines don't need to all share the same version of WiX. Individual projects within a greater product build process could use different /specific versions of WiX. If 1 of your 50 projects needs to move to a later version of WiX (bug fixes, feature enhancements, etc...) it can do so without wondering what side effects might be introduced to the other projects should they all have moved to the later version of WiX. Etc... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: Monday, July 07, 2008 3:25 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Integration of WiX v3 on team build server How would you expect the build server to be able to use the WiX tools without them being installed? I mean, strictly speaking you don't need to install them, just make them available. But what would be the benefit? Chris On Mon, Jul 7, 2008 at 4:01 PM, Dmitry Berkovich [EMAIL PROTECTED] wrote: Hi, I want compile WiX projects on team build server, but I don't want install WiX on build server, so I am planning add all needed files to source control. I have some problem when I am compile wixproj file. wixproj file contains those 2 lines: WixTargetsPath Condition= '$(WixTargetsPath)' == '' $(MSBuildExtensionsPath)\Microsoft\WiX\v3.0\Wix.targets/WixTargetsPat h Import Project=$(WixTargetsPath) / Since WiX not installed on build machine I override CoreCompile target of Microsoft.TeamFoundation.Build.targets in my TFSBuild.proj file, so I can transfer WixTargetsPath to MSBuild task. The problems that build failed since I have error: Solution file warning MSB4122: Scanning project dependencies for project MyProj.wixProj failed. Blablabla since WixTargetsPath not exist. What I need to do to resolve this problem? Thanks in advance, Dima - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08
Re: [WiX-users] Integration of WiX v3 on team build server
TFS enforces a mutex of 1 running build per build server per project. Otherwise it's possible to get multiple builds going at once on a single build server if they build out of seperate TFS projects. InstallShield craps out when attempting to do this and I've repeatedly tried to get them to fix it. As an aside, one company that I used to work for did about 50,000 builds per year. The product line is broken down into chunks of assets and a series of sometimes dozens of builds is needed to compose a product. Using BuildForge and ESX, they use a farm of virtual machines with the ability to create complex chains of builds that get randomly assigned to build machines that match the configuration requirements of a given build. Concurrent builds are needed to keep up the tempo. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me --- On Mon, 7/7/08, Christopher Karper [EMAIL PROTECTED] wrote: From: Christopher Karper [EMAIL PROTECTED] Subject: Re: [WiX-users] Integration of WiX v3 on team build server To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Monday, July 7, 2008, 4:41 PM Can TFS do concurrent builds? If more than one build kicked off at the same time, that could be pretty bad. Chris On Mon, Jul 7, 2008 at 5:35 PM, Neil Sleightholm [EMAIL PROTECTED] wrote: Just a thought but why not put the WiX MSI in TFS and then do a silent install of WiX at the start of the build. Then you get the best of both worlds, a standard WiX install and WiX being automatically updated on all build machines. Also, if the WiX tool set gets some new tools or config you don't need to figure out how they need to be installed. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Nannenga Sent: 07 July 2008 21:33 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Integration of WiX v3 on team build server 2 big benefits I can think of: 1) Machine maintenance If you have 5 build machines, you don't have to update WiX on all 5 of the build machines. The synch process pulls down the appropriate WiX version during the build process. 2) Large projects that share Build machines don't need to all share the same version of WiX. Individual projects within a greater product build process could use different /specific versions of WiX. If 1 of your 50 projects needs to move to a later version of WiX (bug fixes, feature enhancements, etc...) it can do so without wondering what side effects might be introduced to the other projects should they all have moved to the later version of WiX. Etc... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: Monday, July 07, 2008 3:25 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Integration of WiX v3 on team build server How would you expect the build server to be able to use the WiX tools without them being installed? I mean, strictly speaking you don't need to install them, just make them available. But what would be the benefit? Chris On Mon, Jul 7, 2008 at 4:01 PM, Dmitry Berkovich [EMAIL PROTECTED] wrote: Hi, I want compile WiX projects on team build server, but I don't want install WiX on build server, so I am planning add all needed files to source control. I have some problem when I am compile wixproj file. wixproj file contains those 2 lines: WixTargetsPath Condition= '$(WixTargetsPath)' == '' $(MSBuildExtensionsPath)\Microsoft\WiX\v3.0\Wix.targets/WixTargetsPat h Import Project=$(WixTargetsPath) / Since WiX not installed on build machine I override CoreCompile target of Microsoft.TeamFoundation.Build.targets in my TFSBuild.proj file, so I can transfer WixTargetsPath to MSBuild task. The problems that build failed since I have error: Solution file warning MSB4122: Scanning project dependencies for project MyProj.wixProj failed. Blablabla since WixTargetsPath not exist. What I need to do to resolve this problem? Thanks in advance, Dima - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix V3 - setupbld.exe - Error 0x80070013: Failed to CreateSetup
Hi Wix experts, We are getting this error when we try to use setupbld.exe. setupbld.exe -out D:\AGPM_30\source.binaries.x86fre\agpm_30\agpm_30_server_x86.exe -mt D:\AGPM_30\source.binaries.x86fre\agpm_30\agpm_30_server.x86.en-US.msi -u 1031 D:\AGPM_30\source.binaries.x86fre\agpm_30\server_de-DE.mst -u 3082 D:\AGPM_30\source.binaries.x86fre\agpm_30\server_es-ES.mst -u 1036 D:\AGPM_30\source.binaries.x86fre\agpm_30\server_fr-FR.mst -u 1040 D:\AGPM_30\source.binaries.x86fre\agpm_30\server_it-IT.mst -u 1041 D:\AGPM_30\source.binaries.x86fre\agpm_30\server_ja-JP.mst -u 1042 D:\AGPM_30\source.binaries.x86fre\agpm_30\server_ko-KR.mst -u 1046 D:\AGPM_30\source.binaries.x86fre\agpm_30\server_pt-BR.mst -u 1049 D:\AGPM_30\source.binaries.x86fre\agpm_30\server_ru-RU.mst -u 2052 D:\AGPM_30\source.binaries.x86fre\agpm_30\server_zh-CN.mst -u 1028 D:\AGPM_30\source.binaries.x86fre\agpm_30\server_zh-TW.mst -setup D:\AGPM_30\source\tools\wix3\setup.exe Error 0x80070013: Failed to CreateSetup. I looked up the HRESULT and it looks like 0x80070013 is The media is write protected. If I try to do the command manually it is successful. Do u have any trouble shooting ideas? Thanks so much! Lindsay - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to dynamically create check boxes in WIX UI
Hi all, A nice example chris I never thought of that option.. I have done it completely differently, my current code is quite messy as I was trying to find a way to do this first. It really needs to be refactored using a serializer or something. We use a master xml file here which contains environment specific configuration for a huge distributed website. Within the config are multiple PUBLIC properties which are used to set config files and various other items. During our build process I parse a master config and dynamically generate the WiX UI fragments. Due to my current role having IP restrictions I am not allowed to share the code however I can certainly share the concept i used. Basically a tool which acts in much the same was as Tallow except for UI. I enumerate one of my site config files for all properties which are being set then generate Text box / Edit box UI controls for each of those properties. I also use a 3rd value which determines which UI page the controls should go on. Using the 3rd values i then do a select distinct name to get a list of the dialogs (UI pages) that need to be generated. In the master templates I create references to two dynamically generated fragments. One fragment contains a list of the controls for each dialog. The other fragment contains a list of the dialog fragments as references. If you need more detail let me know.. Sorry about being vague with the code I had to sign NDA's on this role. Cheers, John Christopher Painter-2 wrote: True. I just wanted to clarify that it `could` be done and I'm sure with the proper attention to detail, could even be done reliably if it was ever truely needed. Regardless, the original poster is probably more interested in some way of dynamically generating WiX UI XML from an external dataset and then passing it on to candle anyways. The ControlConditions scenario can work, provided that the disabled controls can exist in the MSI. I've worked at companies where this would not be allowed because it would be a security violation to have certain product line capabilities exist within a package (and visible via orca) where they don't belong even if they are disabled. Regards, Chris Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me --- On Mon, 7/7/08, Jason [EMAIL PROTECTED] wrote: From: Jason [EMAIL PROTECTED] Subject: Re: [WiX-users] How to dynamically create check boxes in WIX UI To: [EMAIL PROTECTED], General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Monday, July 7, 2008, 12:24 PM You are correct. I always forget about temporary rows.. However like your post details that still requires a custom action and doesn't get the benefit of validation. On Mon, Jul 7, 2008 at 10:08 AM, Christopher Painter [EMAIL PROTECTED] wrote: Jason- MSI is a relational database that supports temporary records. It's entirely possible to dynamically emit controls at runtime: http://blog.deploymentengineering.com/2008/07/dynamic-windows-installer-ui.html But otherwise you are correct. The general practice is to have a bunch of disabled controls that are dynamically enabled. Regards, Chris Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me --- On Mon, 7/7/08, Jason [EMAIL PROTECTED] wrote: From: Jason [EMAIL PROTECTED] Subject: Re: [WiX-users] How to dynamically create check boxes in WIX UI To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Monday, July 7, 2008, 1:43 AM You can't 'dynamically generate' UI under Windows Installer without a custom UI handler. You can, however, have a standard dialog and simply disable/hide controls that are not in use. Check the ControlCondition table - http://msdn.microsoft.com/en-us/library/aa368035(VS.85).aspx On Mon, Jul 7, 2008 at 12:43 AM, Nimisha Saboo [EMAIL PROTECTED] wrote: Hi, I am new to Wix programming. I need to dynamically generate check boxes in WIX UI, depending on the number of some external parameters. Is there a way to accomplish this? Thanks and regards, Nimisha - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Building VsTemplatePaths
Has anyone seen this error while building the Votive2008.csproj? If so, what is the resolve? [exec] Done building project Votive2008.csproj -- FAILED. [exec] [exec] Build FAILED. [exec] C:\PROJECTS\Microsoft\WIX_DROP_1\src\votive\SDK_VS2008\Tools\Build\Microsoft.VsSDK.targets(348,5): error MSB4062: The VsTemplatePaths task could not be loaded from the assembly C:\PROJECTS\Microsoft\WIX_DROP_1\src\votive\SDK_VS2008\Tools\Build\Microsoft.VsSDK.Build.Tasks.dll. Could not load file or assembly 'file:///C:\PROJECTS\Microsoft\WIX_DROP_1\src\votive\SDK_VS2008\Tools\Build\Microsoft.VsSDK.Build.Tasks.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the UsingTask declaration is correct, and that the assembly and all its dependencies are available. [exec] 0 Warning(s) [exec] 1 Error(s) Thanks, -- Brian Rogers Intelligence removes complexity. - Me http://www.codeplex.com/wixml/ - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 64-bit wix tools (heat/etc...)
Pyro.exe would be broken by making it a 64-bit tool, since it has to interop with a 32-bit dll (not via COM) that does not exist in a 64-bit version. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Sunday, July 06, 2008 4:24 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] 64-bit wix tools (heat/etc...) Aaron Averbuch wrote: What's the latest timeframe expected on 64-bit tools, especially compiling heat.exe for both x64 and x86 for .NET? Heat is the only tool that might benefit from it. Heat doesn't currently have an owner, though, so I'm not aware of any plans to make an x64 version of it. Feel free to file a feature request or, better yet, submit a patch. -- sig://boB http://joyofsetup.com/ - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Integration of WiX v3 on team build server
Hi, Thanks for a nice discussion, but last mails are missed a point of the problem. I will try explain how MSBuild working: If you are will look inside of teambuild.proj you will see at the begin importMicrosoft.TeamFoundation.Build.targets/ where this target file have target with name CoreBuild that execute MSBuild task for each solution that declared in teambuild.proj. When MSBuild task execute it very similar to executing to msbuild.exe from cmd line, so if you are not providing any properties to MSBuild task solution will not receive any new property that dide't created by default by msbuld. So to put declaration of : PropertyGroup WixTargetsPath Condition= '$(TeamProject)' != '' ..\..\WiX\/triCeratTasksPath /PropertyGroup or simillar its not enough. Default implementation of CoreBuild in Microsoft.TeamFoundation.Build.targets only pass about 5 parameters to MSBuild task, so I did override of this target with my that pass additional parameters ( I saw in some blogs that this feature will be added in next version of team build). The problem here that its not works as expected: I saw in msbuild logs that I received warning that Importc:\prgrams files\msbuld\Microsoft\WiX\v3.0\Wix.targets not exists (it happend because msbuild think that i didn't provide WixTargetsPath property) but at next line it start compile again my solution where my property was passed to msbuild. So at the end of MSBuild i receive error that build failed with 0 errors 0 warning. My question is: Did anybody use team build without installing WiX on build machine? Thanks Dima On Tue, Jul 8, 2008 at 12:46 AM, Christopher Painter [EMAIL PROTECTED] wrote: TFS enforces a mutex of 1 running build per build server per project. Otherwise it's possible to get multiple builds going at once on a single build server if they build out of seperate TFS projects. InstallShield craps out when attempting to do this and I've repeatedly tried to get them to fix it. As an aside, one company that I used to work for did about 50,000 builds per year. The product line is broken down into chunks of assets and a series of sometimes dozens of builds is needed to compose a product. Using BuildForge and ESX, they use a farm of virtual machines with the ability to create complex chains of builds that get randomly assigned to build machines that match the configuration requirements of a given build. Concurrent builds are needed to keep up the tempo. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me --- On Mon, 7/7/08, Christopher Karper [EMAIL PROTECTED] wrote: From: Christopher Karper [EMAIL PROTECTED] Subject: Re: [WiX-users] Integration of WiX v3 on team build server To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Monday, July 7, 2008, 4:41 PM Can TFS do concurrent builds? If more than one build kicked off at the same time, that could be pretty bad. Chris On Mon, Jul 7, 2008 at 5:35 PM, Neil Sleightholm [EMAIL PROTECTED] wrote: Just a thought but why not put the WiX MSI in TFS and then do a silent install of WiX at the start of the build. Then you get the best of both worlds, a standard WiX install and WiX being automatically updated on all build machines. Also, if the WiX tool set gets some new tools or config you don't need to figure out how they need to be installed. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Nannenga Sent: 07 July 2008 21:33 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Integration of WiX v3 on team build server 2 big benefits I can think of: 1) Machine maintenance If you have 5 build machines, you don't have to update WiX on all 5 of the build machines. The synch process pulls down the appropriate WiX version during the build process. 2) Large projects that share Build machines don't need to all share the same version of WiX. Individual projects within a greater product build process could use different /specific versions of WiX. If 1 of your 50 projects needs to move to a later version of WiX (bug fixes, feature enhancements, etc...) it can do so without wondering what side effects might be introduced to the other projects should they all have moved to the later version of WiX. Etc... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: Monday, July 07, 2008 3:25 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Integration of WiX v3 on team build server How would you expect the build server to be able to use the WiX tools without them being installed? I mean, strictly speaking you
Re: [WiX-users] Integration of WiX v3 on team build server
Well, to be fair, there's a syntax error in my XML which would make it not work. I messed up copying the example code and retyping it for here, and the closing tag is not the same as the opening tag. Find a property that team build is passing that wouldn't be present in a local workstation build and use that as the condition. I don't have TFS here at home, so I can't go any further. http://msdn.microsoft.com/en-us/bb399127.aspx Check the section on how to pass in properties to the build. I have not tried this exact configuration before, but I am trying to give you some helpful advice on how to accomplish what you wish. Just like the rest of us, the bulk of the work is on your shoulders to fulfill your requirements. Chris On Tue, Jul 8, 2008 at 12:18 AM, Dmitry Berkovich [EMAIL PROTECTED] wrote: Hi, Thanks for a nice discussion, but last mails are missed a point of the problem. I will try explain how MSBuild working: If you are will look inside of teambuild.proj you will see at the begin importMicrosoft.TeamFoundation.Build.targets/ where this target file have target with name CoreBuild that execute MSBuild task for each solution that declared in teambuild.proj. When MSBuild task execute it very similar to executing to msbuild.exe from cmd line, so if you are not providing any properties to MSBuild task solution will not receive any new property that dide't created by default by msbuld. So to put declaration of : PropertyGroup WixTargetsPath Condition= '$(TeamProject)' != '' ..\..\WiX\/triCeratTasksPath /PropertyGroup or simillar its not enough. Default implementation of CoreBuild in Microsoft.TeamFoundation.Build.targets only pass about 5 parameters to MSBuild task, so I did override of this target with my that pass additional parameters ( I saw in some blogs that this feature will be added in next version of team build). The problem here that its not works as expected: I saw in msbuild logs that I received warning that Importc:\prgrams files\msbuld\Microsoft\WiX\v3.0\Wix.targets not exists (it happend because msbuild think that i didn't provide WixTargetsPath property) but at next line it start compile again my solution where my property was passed to msbuild. So at the end of MSBuild i receive error that build failed with 0 errors 0 warning. My question is: Did anybody use team build without installing WiX on build machine? Thanks Dima On Tue, Jul 8, 2008 at 12:46 AM, Christopher Painter [EMAIL PROTECTED] wrote: TFS enforces a mutex of 1 running build per build server per project. Otherwise it's possible to get multiple builds going at once on a single build server if they build out of seperate TFS projects. InstallShield craps out when attempting to do this and I've repeatedly tried to get them to fix it. As an aside, one company that I used to work for did about 50,000 builds per year. The product line is broken down into chunks of assets and a series of sometimes dozens of builds is needed to compose a product. Using BuildForge and ESX, they use a farm of virtual machines with the ability to create complex chains of builds that get randomly assigned to build machines that match the configuration requirements of a given build. Concurrent builds are needed to keep up the tempo. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me --- On Mon, 7/7/08, Christopher Karper [EMAIL PROTECTED] wrote: From: Christopher Karper [EMAIL PROTECTED] Subject: Re: [WiX-users] Integration of WiX v3 on team build server To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Monday, July 7, 2008, 4:41 PM Can TFS do concurrent builds? If more than one build kicked off at the same time, that could be pretty bad. Chris On Mon, Jul 7, 2008 at 5:35 PM, Neil Sleightholm [EMAIL PROTECTED] wrote: Just a thought but why not put the WiX MSI in TFS and then do a silent install of WiX at the start of the build. Then you get the best of both worlds, a standard WiX install and WiX being automatically updated on all build machines. Also, if the WiX tool set gets some new tools or config you don't need to figure out how they need to be installed. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Nannenga Sent: 07 July 2008 21:33 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Integration of WiX v3 on team build server 2 big benefits I can think of: 1) Machine maintenance If you have 5 build machines, you don't have to update WiX on all 5 of the build machines. The synch process pulls down the appropriate WiX version during the build process. 2) Large projects that share
Re: [WiX-users] Integration of WiX v3 on team build server
Chris, I just have croped full error in email, so its reason that you see syntax error. Thanks for this article, but this one for VS2008, where I am using VS2005. But I did override some target in Microsoft.TeamFoundation.Build.targets file, so my syntax in proj file looks same as in example that you sent me. Dima On Tue, Jul 8, 2008 at 7:36 AM, Christopher Karper [EMAIL PROTECTED] wrote: Well, to be fair, there's a syntax error in my XML which would make it not work. I messed up copying the example code and retyping it for here, and the closing tag is not the same as the opening tag. Find a property that team build is passing that wouldn't be present in a local workstation build and use that as the condition. I don't have TFS here at home, so I can't go any further. http://msdn.microsoft.com/en-us/bb399127.aspx Check the section on how to pass in properties to the build. I have not tried this exact configuration before, but I am trying to give you some helpful advice on how to accomplish what you wish. Just like the rest of us, the bulk of the work is on your shoulders to fulfill your requirements. Chris On Tue, Jul 8, 2008 at 12:18 AM, Dmitry Berkovich [EMAIL PROTECTED] wrote: Hi, Thanks for a nice discussion, but last mails are missed a point of the problem. I will try explain how MSBuild working: If you are will look inside of teambuild.proj you will see at the begin importMicrosoft.TeamFoundation.Build.targets/ where this target file have target with name CoreBuild that execute MSBuild task for each solution that declared in teambuild.proj. When MSBuild task execute it very similar to executing to msbuild.exe from cmd line, so if you are not providing any properties to MSBuild task solution will not receive any new property that dide't created by default by msbuld. So to put declaration of : PropertyGroup WixTargetsPath Condition= '$(TeamProject)' != '' ..\..\WiX\/triCeratTasksPath /PropertyGroup or simillar its not enough. Default implementation of CoreBuild in Microsoft.TeamFoundation.Build.targets only pass about 5 parameters to MSBuild task, so I did override of this target with my that pass additional parameters ( I saw in some blogs that this feature will be added in next version of team build). The problem here that its not works as expected: I saw in msbuild logs that I received warning that Importc:\prgrams files\msbuld\Microsoft\WiX\v3.0\Wix.targets not exists (it happend because msbuild think that i didn't provide WixTargetsPath property) but at next line it start compile again my solution where my property was passed to msbuild. So at the end of MSBuild i receive error that build failed with 0 errors 0 warning. My question is: Did anybody use team build without installing WiX on build machine? Thanks Dima On Tue, Jul 8, 2008 at 12:46 AM, Christopher Painter [EMAIL PROTECTED] wrote: TFS enforces a mutex of 1 running build per build server per project. Otherwise it's possible to get multiple builds going at once on a single build server if they build out of seperate TFS projects. InstallShield craps out when attempting to do this and I've repeatedly tried to get them to fix it. As an aside, one company that I used to work for did about 50,000 builds per year. The product line is broken down into chunks of assets and a series of sometimes dozens of builds is needed to compose a product. Using BuildForge and ESX, they use a farm of virtual machines with the ability to create complex chains of builds that get randomly assigned to build machines that match the configuration requirements of a given build. Concurrent builds are needed to keep up the tempo. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me --- On Mon, 7/7/08, Christopher Karper [EMAIL PROTECTED] wrote: From: Christopher Karper [EMAIL PROTECTED] Subject: Re: [WiX-users] Integration of WiX v3 on team build server To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Monday, July 7, 2008, 4:41 PM Can TFS do concurrent builds? If more than one build kicked off at the same time, that could be pretty bad. Chris On Mon, Jul 7, 2008 at 5:35 PM, Neil Sleightholm [EMAIL PROTECTED] wrote: Just a thought but why not put the WiX MSI in TFS and then do a silent install of WiX at the start of the build. Then you get the best of both worlds, a standard WiX install and WiX being automatically updated on all build machines. Also, if the WiX tool set gets some new tools or config you don't need to figure out how they need to be installed. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Nannenga Sent: 07 July 2008 21:33 To: General discussion
Re: [WiX-users] Integration of WiX v3 on team build server
While we do not use WiX inside TFS, we do use WiX in a daily build process on a machine without installing WiX on the build machine. Instead, we have checked in all the WiX binaries and targets files into the tree. Basically, this is the contents of C:\Program Files\Windows Installer XML v3\bin and C:\Program Files\MSBuild\Microsoft\WiX\v3.0. These are all stored in, say enlistmentroot\tools\WiX in our source code enlistment. In our WiX project file we have removed the default WixTargetsPath property and added the following: PropertyGroup WixRootenlistmentroot\tools\wix\/WixRoot WixTargetsPath$(WixRoot)wix.targets/WixTargetsPath WixTasksPath$(WixRoot)WixTasks.dll/WixTasksPath /PropertyGroup You need to specify both WixTargetsPath and WixTasksPath for the build to work. There should be no need to create any kind of CoreBuild anything. Neil From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Dmitry Berkovich [EMAIL PROTECTED] Sent: Monday, July 07, 2008 9:18 PM To: [EMAIL PROTECTED]; General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Integration of WiX v3 on team build server Hi, Thanks for a nice discussion, but last mails are missed a point of the problem. I will try explain how MSBuild working: If you are will look inside of teambuild.proj you will see at the begin importMicrosoft.TeamFoundation.Build.targets/ where this target file have target with name CoreBuild that execute MSBuild task for each solution that declared in teambuild.proj. When MSBuild task execute it very similar to executing to msbuild.exe from cmd line, so if you are not providing any properties to MSBuild task solution will not receive any new property that dide't created by default by msbuld. So to put declaration of : PropertyGroup WixTargetsPath Condition= '$(TeamProject)' != '' ..\..\WiX\/triCeratTasksPath /PropertyGroup or simillar its not enough. Default implementation of CoreBuild in Microsoft.TeamFoundation.Build.targets only pass about 5 parameters to MSBuild task, so I did override of this target with my that pass additional parameters ( I saw in some blogs that this feature will be added in next version of team build). The problem here that its not works as expected: I saw in msbuild logs that I received warning that Importc:\prgrams files\msbuld\Microsoft\WiX\v3.0\Wix.targets not exists (it happend because msbuild think that i didn't provide WixTargetsPath property) but at next line it start compile again my solution where my property was passed to msbuild. So at the end of MSBuild i receive error that build failed with 0 errors 0 warning. My question is: Did anybody use team build without installing WiX on build machine? Thanks Dima On Tue, Jul 8, 2008 at 12:46 AM, Christopher Painter [EMAIL PROTECTED] wrote: TFS enforces a mutex of 1 running build per build server per project. Otherwise it's possible to get multiple builds going at once on a single build server if they build out of seperate TFS projects. InstallShield craps out when attempting to do this and I've repeatedly tried to get them to fix it. As an aside, one company that I used to work for did about 50,000 builds per year. The product line is broken down into chunks of assets and a series of sometimes dozens of builds is needed to compose a product. Using BuildForge and ESX, they use a farm of virtual machines with the ability to create complex chains of builds that get randomly assigned to build machines that match the configuration requirements of a given build. Concurrent builds are needed to keep up the tempo. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me --- On Mon, 7/7/08, Christopher Karper [EMAIL PROTECTED] wrote: From: Christopher Karper [EMAIL PROTECTED] Subject: Re: [WiX-users] Integration of WiX v3 on team build server To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Date: Monday, July 7, 2008, 4:41 PM Can TFS do concurrent builds? If more than one build kicked off at the same time, that could be pretty bad. Chris On Mon, Jul 7, 2008 at 5:35 PM, Neil Sleightholm [EMAIL PROTECTED] wrote: Just a thought but why not put the WiX MSI in TFS and then do a silent install of WiX at the start of the build. Then you get the best of both worlds, a standard WiX install and WiX being automatically updated on all build machines. Also, if the WiX tool set gets some new tools or config you don't need to figure out how they need to be installed. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Nannenga Sent: 07 July 2008 21:33 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Integration of WiX v3 on team build server 2 big benefits
