Re: [WiX-users] Directory in Maintenance mode is not directoryinstalled to
That didn't work. I'll keep plugging away, but if anyone can see a possible cause of the problem, please let me know. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Wednesday, September 29, 2010 6:08 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Directory in Maintenance mode is not directoryinstalled to Try removing the ConfigurableDirectory attribute from all but your top level feature. I think that could be confusing Windows Installer about where to put the sub-features. Could be wrong though but it's worth a try. Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Younie, Bradford [mailto:bradford.you...@chasepaymentech.com] Sent: 28 September 2010 20:20 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Directory in Maintenance mode is not directoryinstalled to I'm using the WIXUI_INSTALLDIR functionality in my installer. When I install, it lets me change the install directory from the default path that I set to INSTALLLOCATION and it installs to that new directory perfectly fine. However, when I enter maintenance mode (by hitting Change in Add/Remove Programs or re-running the installer), and I try to add a feature that I hadn't yet installed, it will always install it to the default path, which is not where I installed the product to. Is there anything special I need to do to make that happen? Here's the code snippet of my installer: ?xml version='1.0'? !-- Copyright (c) Chase Paymentech Solutions, LLC. All rights reserved. -- Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:iis=http://schemas.microsoft.com/wix/IIsExtension; ?include Common\Config.wxi? ?include Common\PackageData.wxi? Product Id='*' Name='Chase Paymentech Spectrum SDK $(var.ProductVersion) for .Net $(var.NetVersion)' Language='1033' Version='$(var.ProductVersion)' Manufacturer='Chase Paymentech' UpgradeCode='$(var.UpgradeCode)' Package Description='Spectrum SDK for .Net $(var.NetVersion)' Comments='Installation of the Spectrum SDK for .Net $(var.NetVersion)' InstallerVersion='300' Compressed='yes' Platform='x86' / !-- To use the canned install sequence, but with a custom dialog -- Property Id=WIXUI_INSTALLDIR Value=INSTALLLOCATION/ UIRef Id=MyWixUI_InstallDir / Property Id=DOTNETVER Value=Net$(var.NetVersionShort) / Property Id=FRAMEWORKROOT RegistrySearch Id=FrameworkRootDir Root=HKLM Key=SOFTWARE\Microsoft\.NETFramework Type=directory Name=InstallRoot / /Property PropertyRef Id=NETFRAMEWORK$(var.NetVersionShort)/ Condition Message=The .NET Framework $(var.NetVersion) must be installed Installed OR NETFRAMEWORK$(var.NetVersionShort) /Condition Media Id='1' Cabinet='product.cab' EmbedCab='yes' / Directory Id='TARGETDIR' Name='SourceDir' Directory Id='ProgramFilesFolder' Name='PFiles' Directory Id='MyCompany' Name='My Company' Directory Id='INSTALLLOCATION' Name='MyProduct' ... /Directory /Directory /Directory /Directory Feature Id='Complete' Title='My Product' Description='The complete package.' TypicalDefault='install' Display='expand' Level='1' ConfigurableDirectory='INSTALLLOCATION' Feature Id='Core' Absent='disallow' Title='Core Software' Description='Core Runtime Components.' Level='1' ... /Feature Feature Id='Samples' Title='Sample Applications' Description='Sample Applications.' ConfigurableDirectory=INSTALLLOCATION Level='3' ... /Feature /Feature /Product /Wix Here is my InstallDir file Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment UI Id=MyWixUI_InstallDir TextStyle Id=WixUI_Font_Normal FaceName=Tahoma Size=8 / TextStyle Id=WixUI_Font_Bigger FaceName=Tahoma Size=12 / TextStyle Id=WixUI_Font_Title FaceName=Tahoma Size=9 Bold=yes / Property Id=DefaultUIFont Value=WixUI_Font_Normal / Property Id=WixUI_Mode Value=InstallDir / DialogRef Id=BrowseDlg / DialogRef Id=DiskCostDlg / DialogRef Id=ErrorDlg / DialogRef Id=FatalError / DialogRef Id=FilesInUse / DialogRef Id=MsiRMFilesInUse / DialogRef Id=PrepareDlg / DialogRef Id=ProgressDlg / DialogRef Id=ResumeDlg / DialogRef Id=UserExit / Publish Dialog=BrowseDlg Control=OK Event=DoAction Value=WixUIValidatePath Order=31/Publish Publish Dialog=BrowseDlg
Re: [WiX-users] Directory in Maintenance mode is not directoryinstalled to
I solved it! I don't know if this is the most efficient or preferred way, but here's what I did: I created a component that is in the main feature that is always installed. It creates a registry key that contains the INSTALLLOCATION value. Such as: Component Id='SetInstallLocation' Guid='[YOUR-GUID-GOES-HERE' RegistryValue Id='SetInstallLocation' Root='HKLM' Key='SOFTWARE\My Company\My Product\[ProductCode]' Name='InstallLocation' Action='write' Type='string' Value='[INSTALLLOCATION]' KeyPath='yes' / /Component Then, I created a property that reads that registry key into INSTALLLOCATION, like so: Property Id=INSTALLLOCATION RegistrySearch Id='GetInstallLocation' Type='raw' Root='HKLM' Key='SOFTWARE\My Company\My Product\[ProductCode]' Name='InstallLocation' / /Property INSTALLLOCATION gets set to the default value if the registry value doesn't exist, and gets set to the right value if it does. Thanks for your help! -Original Message- From: Younie, Bradford Sent: Wednesday, September 29, 2010 8:38 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Directory in Maintenance mode is not directoryinstalled to That didn't work. I'll keep plugging away, but if anyone can see a possible cause of the problem, please let me know. -Original Message- From: Pally Sandher [mailto:pally.sand...@iesve.com] Sent: Wednesday, September 29, 2010 6:08 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Directory in Maintenance mode is not directoryinstalled to Try removing the ConfigurableDirectory attribute from all but your top level feature. I think that could be confusing Windows Installer about where to put the sub-features. Could be wrong though but it's worth a try. Palbinder Sandher Software Deployment IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the Virtual Environment** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Younie, Bradford [mailto:bradford.you...@chasepaymentech.com] Sent: 28 September 2010 20:20 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Directory in Maintenance mode is not directoryinstalled to I'm using the WIXUI_INSTALLDIR functionality in my installer. When I install, it lets me change the install directory from the default path that I set to INSTALLLOCATION and it installs to that new directory perfectly fine. However, when I enter maintenance mode (by hitting Change in Add/Remove Programs or re-running the installer), and I try to add a feature that I hadn't yet installed, it will always install it to the default path, which is not where I installed the product to. Is there anything special I need to do to make that happen? Here's the code snippet of my installer: ?xml version='1.0'? !-- Copyright (c) Chase Paymentech Solutions, LLC. All rights reserved. -- Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:iis=http://schemas.microsoft.com/wix/IIsExtension; ?include Common\Config.wxi? ?include Common\PackageData.wxi? Product Id='*' Name='Chase Paymentech Spectrum SDK $(var.ProductVersion) for .Net $(var.NetVersion)' Language='1033' Version='$(var.ProductVersion)' Manufacturer='Chase Paymentech' UpgradeCode='$(var.UpgradeCode)' Package Description='Spectrum SDK for .Net $(var.NetVersion)' Comments='Installation of the Spectrum SDK for .Net $(var.NetVersion)' InstallerVersion='300' Compressed='yes' Platform='x86' / !-- To use the canned install sequence, but with a custom dialog -- Property Id=WIXUI_INSTALLDIR Value=INSTALLLOCATION/ UIRef Id=MyWixUI_InstallDir / Property Id=DOTNETVER Value=Net$(var.NetVersionShort) / Property Id=FRAMEWORKROOT RegistrySearch Id=FrameworkRootDir Root=HKLM Key=SOFTWARE\Microsoft\.NETFramework Type=directory Name=InstallRoot / /Property PropertyRef Id=NETFRAMEWORK$(var.NetVersionShort)/ Condition Message=The .NET Framework $(var.NetVersion) must be installed Installed OR NETFRAMEWORK$(var.NetVersionShort) /Condition Media Id='1' Cabinet='product.cab' EmbedCab='yes' / Directory Id='TARGETDIR' Name='SourceDir' Directory Id='ProgramFilesFolder' Name='PFiles' Directory Id='MyCompany' Name='My Company' Directory Id='INSTALLLOCATION' Name='MyProduct' ... /Directory /Directory /Directory /Directory Feature Id='Complete' Title='My Product' Description='The complete package.' TypicalDefault='install' Display='expand' Level='1
Re: [WiX-users] Directory in Maintenance mode is not directory installed to
That's much better, but I still needed the code that reads the InstallLocation into my property. Thanks! -Original Message- From: jhennessey [mailto:jack.hennes...@hyland.com] Sent: Wednesday, September 29, 2010 10:10 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Directory in Maintenance mode is not directory installed to If you set the ARPINSTALLLOCATION property to the value of INSTALLLOCATION it should work: !--Set ARPINSTALLLOCATION-- CustomAction Id=SetProperty_InstallLocation Property=ARPINSTALLLOCATION Value=[INSTALLLOCATION]/ InstallExecuteSequence Custom Action=SetProperty_InstallLocation After=InstallValidateNOT Installed/Custom /InstallExecuteSequence -- View this message in context: http://windows-installer-xml-wix- toolset.687559.n2.nabble.com/Directory-in-Maintenance-mode-is-not- directory-installed-to-tp5580924p5584068.html Sent from the wix-users mailing list archive at Nabble.com. --- --- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Learn more about Chase Paymentech Solutions,LLC payment processing services at www.chasepaymentech.com. THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Directory in Maintenance mode is not directory installed to
I'm using the WIXUI_INSTALLDIR functionality in my installer. When I install, it lets me change the install directory from the default path that I set to INSTALLLOCATION and it installs to that new directory perfectly fine. However, when I enter maintenance mode (by hitting Change in Add/Remove Programs or re-running the installer), and I try to add a feature that I hadn't yet installed, it will always install it to the default path, which is not where I installed the product to. Is there anything special I need to do to make that happen? Here's the code snippet of my installer: ?xml version='1.0'? !-- Copyright (c) Chase Paymentech Solutions, LLC. All rights reserved. -- Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:iis=http://schemas.microsoft.com/wix/IIsExtension; ?include Common\Config.wxi? ?include Common\PackageData.wxi? Product Id='*' Name='Chase Paymentech Spectrum SDK $(var.ProductVersion) for .Net $(var.NetVersion)' Language='1033' Version='$(var.ProductVersion)' Manufacturer='Chase Paymentech' UpgradeCode='$(var.UpgradeCode)' Package Description='Spectrum SDK for .Net $(var.NetVersion)' Comments='Installation of the Spectrum SDK for .Net $(var.NetVersion)' InstallerVersion='300' Compressed='yes' Platform='x86' / !-- To use the canned install sequence, but with a custom dialog -- Property Id=WIXUI_INSTALLDIR Value=INSTALLLOCATION/ UIRef Id=MyWixUI_InstallDir / Property Id=DOTNETVER Value=Net$(var.NetVersionShort) / Property Id=FRAMEWORKROOT RegistrySearch Id=FrameworkRootDir Root=HKLM Key=SOFTWARE\Microsoft\.NETFramework Type=directory Name=InstallRoot / /Property PropertyRef Id=NETFRAMEWORK$(var.NetVersionShort)/ Condition Message=The .NET Framework $(var.NetVersion) must be installed Installed OR NETFRAMEWORK$(var.NetVersionShort) /Condition Media Id='1' Cabinet='product.cab' EmbedCab='yes' / Directory Id='TARGETDIR' Name='SourceDir' Directory Id='ProgramFilesFolder' Name='PFiles' Directory Id='MyCompany' Name='My Company' Directory Id='INSTALLLOCATION' Name='MyProduct' ... /Directory /Directory /Directory /Directory Feature Id='Complete' Title='My Product' Description='The complete package.' TypicalDefault='install' Display='expand' Level='1' ConfigurableDirectory='INSTALLLOCATION' Feature Id='Core' Absent='disallow' Title='Core Software' Description='Core Runtime Components.' Level='1' ... /Feature Feature Id='Samples' Title='Sample Applications' Description='Sample Applications.' ConfigurableDirectory=INSTALLLOCATION Level='3' ... /Feature /Feature /Product /Wix Here is my InstallDir file Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment UI Id=MyWixUI_InstallDir TextStyle Id=WixUI_Font_Normal FaceName=Tahoma Size=8 / TextStyle Id=WixUI_Font_Bigger FaceName=Tahoma Size=12 / TextStyle Id=WixUI_Font_Title FaceName=Tahoma Size=9 Bold=yes / Property Id=DefaultUIFont Value=WixUI_Font_Normal / Property Id=WixUI_Mode Value=InstallDir / DialogRef Id=BrowseDlg / DialogRef Id=DiskCostDlg / DialogRef Id=ErrorDlg / DialogRef Id=FatalError / DialogRef Id=FilesInUse / DialogRef Id=MsiRMFilesInUse / DialogRef Id=PrepareDlg / DialogRef Id=ProgressDlg / DialogRef Id=ResumeDlg / DialogRef Id=UserExit / Publish Dialog=BrowseDlg Control=OK Event=DoAction Value=WixUIValidatePath Order=31/Publish Publish Dialog=BrowseDlg Control=OK Event=SpawnDialog Value=InvalidDirDlg Order=4![CDATA[WIXUI_INSTALLDIR_VALID1]]/Publish Publish Dialog=ExitDialog Control=Finish Event=EndDialog Value=Return Order=9991/Publish Publish Dialog=WelcomeDlg Control=Next Event=NewDialog Value=InstallDirDlg Order=11/Publish Publish Dialog=LicenseAgreementDlg Control=Back Event=NewDialog Value=WelcomeDlg1/Publish Publish Dialog=LicenseAgreementDlg Control=Next Event=NewDialog Value=InstallDirDlgLicenseAccepted = 1/Publish Publish Dialog=InstallDirDlg Control=Back Event=NewDialog Value=WelcomeDlg1/Publish Publish Dialog=InstallDirDlg Control=Next Order=1 Event=DoAction Value=FileExists1/Publish Publish Dialog=InstallDirDlg Control=Next Order=2 Event=SetTargetPath Value=[WIXUI_INSTALLDIR]1/Publish Publish Dialog=InstallDirDlg Control=Next Order=3 Event=DoAction Value=WixUIValidatePathNOT WIXUI_DONTVALIDATEPATH/Publish Publish Dialog=InstallDirDlg Control=Next Order=4 Event=SpawnDialog Value=InvalidDirDlg![CDATA[NOT WIXUI_DONTVALIDATEPATH AND WIXUI_INSTALLDIR_VALID1]]/Publish Publish Dialog=InstallDirDlg Control=Next Order=5 Event=NewDialog Value=MySetupTypeDlgFILE_EXISTS=0 AND (WIXUI_DONTVALIDATEPATH OR WIXUI_INSTALLDIR_VALID=1)/Publish Publish Dialog=InstallDirDlg
[WiX-users] How do you extract COM registration info from a 64-bit DLL or TLB?
This is with WiX 3.0. I have an installer that has a COM component. I'm using heat to harvest the COM configuration from both the DLL and TLB files into a fragment that I then include in my wix build. This works great. Now, I need to produce a 64-bit version of the same product, but I build it all on a 32-bit computer. When heat tries to harvest the data from the 64-bit DLL and TLB, it fails. I understand why it fails: it can't load the 64-bit DLL on a 32-bit system. But is there a way around it? Here's how I'm calling heat: heat.exe file MyProduct.dll -srd -suid -dr lib -gg -out MyProduct.wxs --- Bradford Younie Senior Software Engineer Chase Paymentech Solutions 4 NE Blvd Salem, NH 03079-1952 Fax: 603-896-813 bradford.you...@chasepaymentech.com -- Learn more about Chase Paymentech Solutions,LLC payment processing services at www.chasepaymentech.com. THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. -- ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Different versions of a single file to same location
I have two flavors of the SDK product that my company produces. I offer a merge module for each flavor to our VARs so that they can work the one they want easily into their installers. So far so good. I also provide a single installer for our normal customers that lets the user select which flavor of the SDK to install and it will install the appropriate one. This is what I'm developing now, and I'm having trouble with it. I have this installer project consume both merge modules, each one in a different feature. I have a dialog that lets the user select which flavor of the SDK he wants, and it will AddLocal the chosen feature and Remove the not chosen one. Sounds good so far. Here's the hitch: Both merge modules have different versions of the same binary files. They get installed to the same directory. Now, I know that the files from each will never be installed together, but the compiler doesn't know that and it gives the following error: error LGHT0204 : ICE30: The target file 'sc6wmn0u.inc|PriorAuthID.inc' is installed in '[TARGETDIR]\xml\templates\' by two different components on an LFN system: 'PriorAuthID.inc.A254A491_D1A5_43DC_88CF_363C10407599' and 'PriorAuthID.inc.29B29778_DD77_4C31_A8FA_A74751B94965'. This breaks component reference counting. Is there a way to make this work? -- Brad -- Learn more about Chase Paymentech Solutions,LLC payment processing services at www.chasepaymentech.com. THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Trouble creating an Install Location dialog
I'm trying to create a dialog that only asks for the destination
directory. I have it display the contents of INSTALLDIR, and the Browse
button works fine. The only problem is that when you OK the Browse
dialog and get back to the Destination Folder dialog, the label that
displays the selected path does not update to show the new path. If I
click Next to go to the next dialog, and then hit back, it will show the
new path. So, this seems to be a refresh problem.
Is there an event I can subscribe to that will cause a label to refresh
when the Browse dialog goes away?
Here's the dialog's code:
Dialog Id=DestinationDlg Width=370 Height=270
Title=[ProductName] [Setup] NoMinimize=yes TrackDiskSpace=yes
Control Id=Browse Type=PushButton X=304 Y=200
Width=56 Height=17 Text=[ButtonText_Browse]
!--Publish Event=SelectionBrowse
Value=BrowseDlg1/Publish--
Publish Event=SpawnDialog Value=BrowseDlg1/Publish
Condition Action=hideInstalled/Condition
/Control
Control Id=Back Type=PushButton X=180 Y=243 Width=56
Height=17 Text=[ButtonText_Back]
Publish Event=NewDialog
Value=MaintenanceTypeDlg![CDATA[InstallMode = Change]]/Publish
Publish Event=NewDialog
Value=SetupTypeDlg![CDATA[InstallMode = Custom]]/Publish
/Control
Control Id=Next Type=PushButton X=236 Y=243 Width=56
Height=17 Default=yes Text=[ButtonText_Next]
Publish Event=NewDialog Value=VerifyReadyDlg1/Publish
Subscribe Event=SelectionNoItems Attribute=Enabled /
/Control
Control Id=Cancel Type=PushButton X=304 Y=243
Width=56 Height=17 Cancel=yes Text=[ButtonText_Cancel]
Publish Event=SpawnDialog Value=CancelDlg1/Publish
/Control
Control Id=BannerBitmap Type=Bitmap X=0 Y=0 Width=370
Height=44 TabSkip=no Text=[BannerBitmap] /
Control Id=Description Type=Text X=25 Y=23 Width=280
Height=15 Transparent=yes NoPrefix=yes
TextSelect the way you want features to be installed./Text
/Control
Control Id=Text Type=Text X=25 Y=55 Width=320
Height=20
TextClick on the icons in the tree below to change the way
features will be installed./Text
/Control
Control Id=BottomLine Type=Line X=0 Y=234 Width=370
Height=0 /
Control Id=Title Type=Text X=15 Y=6 Width=200
Height=15 Transparent=yes NoPrefix=yes
Text{\DlgTitleFont}Custom Setup/Text
/Control
Control Id=BannerLine Type=Line X=0 Y=44 Width=370
Height=0 /
Control Id=Location Type=Text X=75 Y=200 Width=215
Height=20
Text[INSTALLDIR]/Text
Subscribe Event=EndDialog Attribute=BrowseDlg /
Condition Action=hideInstalled/Condition
/Control
Control Id=LocationLabel Type=Text X=25 Y=200
Width=50 Height=10 Text=Location:
/Control
/Dialog
And the Browse dialog, just in case you need to see it:
Dialog Id=BrowseDlg Width=370 Height=270
Title=[ProductName] [Setup] NoMinimize=yes
Control Id=PathEdit Type=PathEdit X=84 Y=202
Width=261 Height=18 Property=_BrowseProperty Indirect=yes /
Control Id=OK Type=PushButton X=304 Y=243 Width=56
Height=17 Default=yes Text=[ButtonText_OK]
Publish Event=SetTargetPath Value=INSTALLDIR1/Publish
Publish Event=EndDialog Value=Return1/Publish
/Control
Control Id=Cancel Type=PushButton X=240 Y=243
Width=56 Height=17 Cancel=yes Text=[ButtonText_Cancel]
Publish Event=Reset Value=01/Publish
Publish Event=EndDialog Value=Return1/Publish
/Control
Control Id=ComboLabel Type=Text X=25 Y=58 Width=44
Height=10 TabSkip=no Text=amp;Look in: /
Control Id=DirectoryCombo Type=DirectoryCombo X=70 Y=55
Width=220 Height=80 Property=INSTALLDIR Indirect=no Fixed=yes
Remote=yes
Subscribe Event=IgnoreChange Attribute=IgnoreChange /
/Control
Control Id=Up Type=PushButton X=298 Y=55 Width=19
Height=19 ToolTip=Up One Level Icon=yes FixedSize=yes
IconSize=16 Text=Up
Publish Event=DirectoryListUp Value=01/Publish
/Control
Control Id=NewFolder Type=PushButton X=325 Y=55
Width=19 Height=19 ToolTip=Create A New Folder Icon=yes
FixedSize=yes IconSize=16 Text=New
Publish Event=DirectoryListNew Value=01/Publish
/Control
Control Id=DirectoryList Type=DirectoryList X=25 Y=83
Width=320 Height=110 Property=INSTALLDIR Sunken=yes
Indirect=no TabSkip=no /
Control Id=PathLabel Type=Text X=25 Y=205 Width=59
Height=10 TabSkip=no Text=amp;Folder name: /
Control Id=BannerBitmap Type=Bitmap X=0 Y=0 Width=370
Height=44 TabSkip=no Text=[BannerBitmap] /
Control Id=Description Type=Text X=25 Y=23 Width=280
Height=15 Transparent=yes NoPrefix=yes
TextBrowse to the destination folder/Text
/Control
Control Id=BottomLine Type=Line X=0 Y=234 Width=370
Height=0 /
Control Id=Title Type=Text X=15 Y=6 Width=200
[WiX-users] Trouble creating an Install Location dialog
Why are you trying to re-write this when it already exists in WiXUIExtension? First, I have to say that I'm fairly new to wix. That being said, here's my situation: I have my own custom dialog sequence. I have my own WelcomeDlg, which has its own banner bitmap. It currently goes to a custom SetupTypeDlg that has choices different than the default. And then I have other dialogs that are pretty standard (except with my own banner bitmap). I need to insert an InstallDlg into my custom sequence, without using the canned sequence. It seems that the only way to do that is to take the InstallDlg.wxs from the wix source, rename it, and then work it into my UI source. This is fine, but now that I'm linking with WixUIExtension.dll, I have to rename some of my custom dialogs and remove duplicate properties and so on. I'm doing that now. If there's an easier, or more standard option, I'd love to hear it. --- Bradford Younie -- Learn more about Chase Paymentech Solutions,LLC payment processing services at www.chasepaymentech.com. THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Trouble Inserting a dialog from WixUIExtension.dll into a custom dialog sequence
I have my own custom dialog sequence and I need to insert an InstallDirDlg into it. WixUIExtension.dll has one, but every attempt I make to fit it into my existing custom dialog sequence fails. It seems to want to force me into using their canned sequence rather than my own. Is there a series of steps to take to insert a canned dialog into a custom dialog sequence? There are plenty of tutorials online telling you how to modify a canned dialog, but that still involves using the canned sequence. --- Bradford Younie Senior Software Engineer Chase Paymentech Solutions 4 NE Blvd Salem, NH 03079-1952 Fax: 603-896-813 bradford.you...@chasepaymentech.com -- Learn more about Chase Paymentech Solutions,LLC payment processing services at www.chasepaymentech.com. THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Replacing the WelcomeDlg in the InstallUISequence
I've copied the WelcomeDlg.wxs file to my area, renamed it, modified it to replace the bitmap, and updated its InstallUISequence so that it appears as it should. The only problem I have is that the original WelcomeDlg that's in the WixUIExtension.dll displays for second or two before being replaced by my custom one. I did all the steps described on the page: http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html Which got me this far, but it didn't describe how to remove the original WelcomeDlg from the install sequence. Any ideas? --- Bradford Younie Senior Software Engineer Chase Paymentech Solutions 4 NE Blvd Salem, NH 03079-1952 Fax: 603-896-813 bradford.you...@chasepaymentech.com -- Learn more about Chase Paymentech Solutions,LLC payment processing services at www.chasepaymentech.com. THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] A question about components and their guids
This is kind of a high-level question about components that I need to understand: What would happen in this scenario: I have two installers that install the same file to their own directory tree. When I defined each installer source, I did a copy/paste of the component for that file from one source to the other and neglected to change the component's guid on the second installer. Then I build each installer kit and run them both, one at a time, on my system. Would the files be installed in their proper places for each installer, or would MSI get confused because they have the same ID and guid? I guess the direct way to word the question is: does a component's guid only need to be unique within the product or module it's defined in, or must it be unique from all components installed on the target computer? I know it would be best to give them different guids, but I really need to understand how this works. Best regards, --- Bradford Younie -- Learn more about Chase Paymentech Solutions,LLC payment processing services at www.chasepaymentech.com. THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX-users Digest, Vol 41, Issue 157
The IDs of components have a scope of the containing package. The Guids of components have a system-wide scope. As a result, you do need to fix this as soon as you safely can. Thanks! That makes things a whole lot clearer. I wanted to understand how it works so that I knew what my options were. --- Bradford Younie -- Learn more about Chase Paymentech Solutions,LLC payment processing services at www.chasepaymentech.com. THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Trouble using Fragments in merge module files
My guess is you need a ComponentRef Id='EOD.xmlxml'/ somewhere in your mymodule.wxs file to pull in the fragment in your Templates.wxs file. Okay. I'll try that. What do you mean by If I do the same thing to include them in my main installer, it works fine.? You change Module for Product and it works? Or what specifically do you do? I mean that if I don't include the fragment's file when I build my merge module, but I do specify it when I build the install, the installer installs it just fine. But that raises a point. I had to put ComponentRefs (or a ComponentGroupRef) in the main installer source to specify what Feature it goes under. So, it does make sense that adding the ComponentRefs to the merge source could do the trick. I'll try it and let you know. -- Learn more about Chase Paymentech Solutions,LLC payment processing services at www.chasepaymentech.com. THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Trouble using Fragments in merge module files
My guess is you need a ComponentRef Id='EOD.xmlxml'/ somewhere in your mymodule.wxs file to pull in the fragment in your Templates.wxs file. That did the trick! I created a ComponentGroup in the Fragment, and then added a ComponentGroupRef in the Module. Thanks for all your help! Brad -- Learn more about Chase Paymentech Solutions,LLC payment processing services at www.chasepaymentech.com. THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Trouble using Fragments in merge module files
I'm developing multiple merge modules that share some data files in common. I want to have the data files defined in a Fragment that each merge module uses. For some reason, the files in my fragment doesn't install, even though it builds with no error. If I add the fragment to the main installer, it works like a charm. Is there something I have to do differently to get fragments to work with merge modules? Here's the code snippet of my Fragment (there are really more files, but this is an example): ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Fragment DirectoryRef Id=xml Component Id='EOD.xmlxml' Guid='MY GUID HERE' File Id='EOD.xmlxml' Name='EOD.xml' Source='..\xml\EOD.xml' / /Component /DirectoryRef /Fragment /Wix Now, here's the snippet of my merge module: Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Module Id='MyMergeModule' Language='1033' Version='6.4.0.0' Package Id='[MY GUID HERE]' Description='My Module' Comments='My Module' Manufacturer='My Company' InstallerVersion='200' / Directory Id='TARGETDIR' Name='SourceDir' Directory Id='MyModuleDirectory' Name='.' Directory Id='etc' Name='etc' Component Id='linehandler.properties' Guid='[MY GUID HERE]' File Id='linehandler.properties' Name='linehandler.properties' Source='..\etc\DotNet\linehandler.properties' / /Component /Directory Directory Id='xml' Name='xml' Directory Id='templates' Name='templates'/ /Directory /Directory /Directory /Module /Wix Here's how I build: candle mymodule.wxs Templates.wxs light -out mymodule.msm mymodule.wixobj Templates.wixobj -loc WixUI_en-us.wxl If I do the same thing to include them in my main installer, it works fine. I'm using WIX 3.0. --- Bradford Younie Senior Software Engineer Chase Paymentech Solutions 4 NE Blvd Salem, NH 03079-1952 Fax: 603-896-813 bradford.you...@chasepaymentech.com -- Learn more about Chase Paymentech Solutions,LLC payment processing services at www.chasepaymentech.com. THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Accessing the install directory from within a mergemodule
Have you tried using INSTALLDIR instead of TARGETDIR? It should match the configurable directory of your application: Feature Id='Complete' Title='Example' Description='Description' Display='expand' Level='1' ConfigurableDirectory='INSTALLDIR' Because that is the property that gets sets when the user chooses a folder to install the application in. That did it! I had tried INSTALLDIR before, but it was always set to nothing. It was the ConfigurableDirectory that did the trick! Actually, I was mistaken. It worked when I access it from within the same msi, but I cannot seem to access INSTALLDIR from within my merge module. Is there something I need to do to pass INSTALLDIR's value into the merge module? I played around with ConfigurationInfo but with no luck. --- Bradford Younie Senior Software Engineer Chase Paymentech Solutions 4 NE Blvd Salem, NH 03079-1952 Fax: 603-896-813 bradford.you...@chasepaymentech.com -- Learn more about Chase Paymentech Solutions,LLC payment processing services at www.chasepaymentech.com. THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Accessing the install directory from within a merge module
In a merge module, I'm trying to create an environment variable that contains the path to where the product is being installed to. My merge module uses the code below to do it, but it's not working quite right. When the product gets installed to c:\program files\mycompany\myapp, [TARGETDIR] in the merge module only puts C:\ into the environment variable even though the product does install to the full path. Is there a different way to handle this? ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Module Id=Spectrum11MergeModule Language=1033 Version=1.0.0.0 Package Id=9b6a3ca6-caf9-49b2-8fb9-e8c1c1b354f2 Manufacturer=Spectrum11MergeModule InstallerVersion=200 / Directory Id=TARGETDIR Name=SourceDir Component Id=EnvironmentVars Guid=F50F41C2--4680-8B50-741F96C8D8D6 Environment Id=envHome Action=create Name=SPECTRUM_HOME1 System=yes Value=[TARGETDIR]/ Environment Id=envLogDir Action=create Name=SPECTRUM_LOGDIR1 System=yes Value=[TARGETDIR]\logs/ /Component /Directory /Module /Wix -- Brad Younie -- Learn more about Chase Paymentech Solutions,LLC payment processing services at www.chasepaymentech.com. THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Accessing the install directory from within a merge module
Hi, In a merge module, I'm trying to create an environment variable that contains the path to where the product is being installed to. My merge module uses the code below to do it, but it's not working quite right. When the product gets installed to c:\program files\mycompany\myapp, [TARGETDIR] in the merge module only puts C:\ into the environment variable even though the product does install to the full path. Is there a different way to handle this? Have you tried using INSTALLDIR instead of TARGETDIR? It should match the configurable directory of your application: Feature Id='Complete' Title='Example' Description='Description' Display='expand' Level='1' ConfigurableDirectory='INSTALLDIR' Because that is the property that gets sets when the user chooses a folder to install the application in. That did it! I had tried INSTALLDIR before, but it was always set to nothing. It was the ConfigurableDirectory that did the trick! Thanks --- Bradford Younie Senior Software Engineer Chase Paymentech Solutions 4 NE Blvd Salem, NH 03079-1952 Fax: 603-896-813 bradford.you...@chasepaymentech.com -- Learn more about Chase Paymentech Solutions,LLC payment processing services at www.chasepaymentech.com. THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Possible strange behavior of INSTALLDIR in WiX 3
I'm fairly new to WiX and am trying to do use merge modules for the first time (I'm fluent in InstallShield, but want to move away from it). Anyway, I'm trying to have my merge module create a couple of environment variables at install time, both of which will have [INSTALLDIR] as part of its value. I figured I ought to use the [TARGETDIR] property of the merge module. However, when I do that, all I get is C:\ when the real install location is that plus some directories (i.e., C:\Program Files\MyCompany\MyApp). The following is my Install code and my Merge Module code. My assumption is that I'm doing something wrong. How can I get the full path. BTW: I also tried referencing [INSTALLDIR], [INSTALLLOCATION], and others but to no avail. Those didn't give me any value whatsoever. Install Code: Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Directory Id=COMPANYLOCATION Name=MyCompany Directory Id=PRODUCTLOCATION Name=MyProduct Directory Id=INSTALLLOCATION Name='2.0.0' Merge Id='CoreFilesMM' Language=1033 SourceFile='..\Spectrum11MergeModule\bin\Debug\Spectrum11MergeModule.msm ' DiskId='1' / /Directory /Directory /Directory /Directory /Directory Merge Module Code: Directory Id=TARGETDIR Name=SourceDir Component Id=EnvironmentVars Guid=F50F41C2--4680-8B50-741F96C8D8D6 Environment Id=envHome Action=create Name=SPECTRUM_HOME System=yes Value=[TARGETDIR]/ Environment Id=envLogDir Action=create Name=SPECTRUM_LOGDIR System=yes Value=[TARGETDIR]\logs/ /Component ?include Config.wxi ? ?include Libraries.wxi ? ?include Converter.wxi ? ?include Templates.wxi ? /Directory --- Bradford Younie Senior Software Engineer Chase Paymentech Solutions 4 NE Blvd Salem, NH 03079-1952 Fax: 603-896-813 bradford.you...@chasepaymentech.com -- Learn more about Chase Paymentech Solutions,LLC payment processing services at www.chasepaymentech.com. THIS MESSAGE IS CONFIDENTIAL. This e-mail message and any attachments are proprietary and confidential information intended only for the use of the recipient(s) named above. If you are not the intended recipient, you may not print, distribute, or copy this message or any attachments. If you have received this communication in error, please notify the sender by return e-mail and delete this message and any attachments from your computer. -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
