[WiX-users] localized installer
Hello, I know that a MSI file can handle only one locale. So I need a bootstrapper to select a MSI file on customer's choise. Where can I find information, how this can be done with WiX? I assume this can be a frequently asked question. Thanks, Helge -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] validating integer input
In my following code it is always doing an ascii comparison. How can I do an integer comparision? I tried specifying Interger="Yes" for the Control Id but light gave a warning "warning LGHT1076 : ICE45: .." and later at run time installer failed with an error. Any pointers? Thank you. -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Wizard activates even though I installed the drivers via WIX Installer.
Hi to all, I am currently Installing drivers via WIX for Windows XP 32 bit. The installer runs fine. My question is... once I connect my device. Windows XP runs a wizard... and tries to install the drivers for the device. It shouldn't do that. It should just recognized the device and say is ready to go... avoiding to run a wizard. Probably I am doing something wrong If I run the same installer for windows 7, I don't get the wizard problem. It just detects the device and works. Does anyone know why this happens? I am adding the code here, maybe I am doing something wrong for Windows XP 32 bit. --- http://schemas.microsoft.com/wix/2006/wi"; xmlns:difx="http://schemas.microsoft.com/wix/DifxAppExtension";> --- -- ing. Javier Orlando Ramírez Martínez http://linux.mty.itesm.mx/~oramirez http://picasaweb.google.com/javier.ramirez http://twitter.com/oramirez1 http://flickr.com/photos/orlando1 -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VC++ redistributable questions
Assumption based on personal experience as we ran at least the last 4 years the VCRedist during InstallUI. We nerver got customer issues regarding a missing VC runtime. This would be expected when they run unattended as there is (was) no abort criteria during InstallExecute when no VCRedist installed. 2011/4/28 Jeremy Farrell : >> From: Tobias S [mailto:tobias.s1...@gmail.com] >> >> ... >> >> - Most installs run in UI mode > > Interesting, where did you get that information from? What's the ratio > between UI-mode runs and silent, and how accurate is the estimate believed to > be? > -- > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] how to validate a user-defined path that isn't for the Install directory?
Another Wix noob question: As part of my installation, I need to ask the user to enter the value for JAVA_HOME (which I default by picking it up from the environment). If they change the path, I'd like to validate that the value they provide actually exists, but I've been unable to find how to do that. I see DirectorySearch, but it appears (at least in the WiX book) to take a constant, and I'm assuming it runs before the user sees anything anyway. I see validation references to the CustomAction WixUIValidatePath, but that is only for WIXUI_INSTALLDIR, and Common.wxs defines that as calling a DLLEntry 'ValidatePath'. How does one validate a path the user has entered that isn't for the install directory? Note that I'm not trying to install anything in this directory, I just need to record the fact that it is present and valid, and what its value is. Any help would be appreciated! Dave -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VC++ redistributable questions
I use InstallShield as my container so a good functioning bootstrapper isn't a problem for me. I think the source of the confusion here is that the MSI team sent out a pretty clear issue about avoiding the use of third party merge modules and concurrent installs and to use chained micro packages instead. Now all of a sudden another group within MSFT comes out and says "trust our merge modules" and well frankly, I have a hard time doing that. --- 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 Thu, 4/28/11, Wilson, Phil wrote: From: Wilson, Phil Subject: Re: [WiX-users] VC++ redistributable questions To: "General discussion for Windows Installer XML toolset." Date: Thursday, April 28, 2011, 12:14 PM As has been pointed out, it is a fact that the InstallUISequence is not run during a silent install. Therefore your custom action in the UI sequence cannot be running. Beware that you may have a faith-based install instead of one that relies on Windows known behavior. Also, you can't run an MSI-based install from the execute sequence, that's been mentioned too, so be glad that you didn't think of it because it won't work anyway. Recursive MSI installs don't work. Prepare for error 1618. I'm going to repeat what's been said: 1. Use the merge modules. 2. If you have a bootstrapper and a reason to get the VC++ on the system for the duration of the install, then run the vcredist exe. I'll also add something Bob A mentioned in case it matters. The UI sequence is not elevated unless the entire MSI is launched elevated, so there may be situations where installing the redist from the UI sequence will fail because of insufficient privilege. Phil Wilson -Original Message- From: Tobias S [mailto:tobias.s1...@gmail.com] Sent: Thursday, April 28, 2011 9:36 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VC++ redistributable questions Thanks for your feedback. I used the InstallUI sequence to install the VCRedist.exe and did nothing in InstallExecute sequence. So actually my implementation can lead to an installed product without installed VCRedist when user runs in /qn. When writing >> - Most installs run in UI mode, otherwise also for InstallExecute a >> condition could be integrated. Same scenario must be considered when >> designing an installer with a bootstrapper I thought of Not Installed And Not VC2010REDIST_X86 I didn't think of installing another MSI in InstallExecute sequence. Sorry for the misunderstanding. Right now I also mentioned that properties are not re-evaluated when FindRelatedProducts is called in InstallUISequence and InstallExecuteSequence. So a set property CA must be implemented... 2011/4/28 Bob Arnson : > On 28-Apr-11 09:52, Tobias S wrote: >> - With this implementation the VCRedist installer runs at a point >> where the user can run the installation unattended (for bootstrapper >> normally waiting until completion necessary - not considering Burn >> here as it is in beta) >> - Most installs run in UI mode, otherwise also for InstallExecute a >> condition could be integrated. Same scenario must be considered when >> designing an installer with a bootstrapper > > Neither of these is the case: Unattended installs skip the UI sequence > so anything done only in the UI sequence is also skipped. And you cannot > run another installer from the execute sequence; that requires a chainer. > >> PS: I know this approach is somehow quick-and-dirty and not MSDN >> compliant ... but it does a good job ... > > There's nothing wrong with quick, but dirty and unsupported are bad news. > > -- > sig://boB > http://joyofsetup.com/ > > > -- > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to w
Re: [WiX-users] VC++ redistributable questions
> From: Tobias S [mailto:tobias.s1...@gmail.com] > > ... > > - Most installs run in UI mode Interesting, where did you get that information from? What's the ratio between UI-mode runs and silent, and how accurate is the estimate believed to be? -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VC++ redistributable questions
As has been pointed out, it is a fact that the InstallUISequence is not run during a silent install. Therefore your custom action in the UI sequence cannot be running. Beware that you may have a faith-based install instead of one that relies on Windows known behavior. Also, you can't run an MSI-based install from the execute sequence, that's been mentioned too, so be glad that you didn't think of it because it won't work anyway. Recursive MSI installs don't work. Prepare for error 1618. I'm going to repeat what's been said: 1. Use the merge modules. 2. If you have a bootstrapper and a reason to get the VC++ on the system for the duration of the install, then run the vcredist exe. I'll also add something Bob A mentioned in case it matters. The UI sequence is not elevated unless the entire MSI is launched elevated, so there may be situations where installing the redist from the UI sequence will fail because of insufficient privilege. Phil Wilson -Original Message- From: Tobias S [mailto:tobias.s1...@gmail.com] Sent: Thursday, April 28, 2011 9:36 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VC++ redistributable questions Thanks for your feedback. I used the InstallUI sequence to install the VCRedist.exe and did nothing in InstallExecute sequence. So actually my implementation can lead to an installed product without installed VCRedist when user runs in /qn. When writing >> - Most installs run in UI mode, otherwise also for InstallExecute a >> condition could be integrated. Same scenario must be considered when >> designing an installer with a bootstrapper I thought of Not Installed And Not VC2010REDIST_X86 I didn't think of installing another MSI in InstallExecute sequence. Sorry for the misunderstanding. Right now I also mentioned that properties are not re-evaluated when FindRelatedProducts is called in InstallUISequence and InstallExecuteSequence. So a set property CA must be implemented... 2011/4/28 Bob Arnson : > On 28-Apr-11 09:52, Tobias S wrote: >> - With this implementation the VCRedist installer runs at a point >> where the user can run the installation unattended (for bootstrapper >> normally waiting until completion necessary - not considering Burn >> here as it is in beta) >> - Most installs run in UI mode, otherwise also for InstallExecute a >> condition could be integrated. Same scenario must be considered when >> designing an installer with a bootstrapper > > Neither of these is the case: Unattended installs skip the UI sequence > so anything done only in the UI sequence is also skipped. And you cannot > run another installer from the execute sequence; that requires a chainer. > >> PS: I know this approach is somehow quick-and-dirty and not MSDN >> compliant ... but it does a good job ... > > There's nothing wrong with quick, but dirty and unsupported are bad news. > > -- > sig://boB > http://joyofsetup.com/ > > > -- > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com.
Re: [WiX-users] VC++ redistributable questions
Thanks for your feedback. I used the InstallUI sequence to install the VCRedist.exe and did nothing in InstallExecute sequence. So actually my implementation can lead to an installed product without installed VCRedist when user runs in /qn. When writing >> - Most installs run in UI mode, otherwise also for InstallExecute a >> condition could be integrated. Same scenario must be considered when >> designing an installer with a bootstrapper I thought of Not Installed And Not VC2010REDIST_X86 I didn't think of installing another MSI in InstallExecute sequence. Sorry for the misunderstanding. Right now I also mentioned that properties are not re-evaluated when FindRelatedProducts is called in InstallUISequence and InstallExecuteSequence. So a set property CA must be implemented... 2011/4/28 Bob Arnson : > On 28-Apr-11 09:52, Tobias S wrote: >> - With this implementation the VCRedist installer runs at a point >> where the user can run the installation unattended (for bootstrapper >> normally waiting until completion necessary - not considering Burn >> here as it is in beta) >> - Most installs run in UI mode, otherwise also for InstallExecute a >> condition could be integrated. Same scenario must be considered when >> designing an installer with a bootstrapper > > Neither of these is the case: Unattended installs skip the UI sequence > so anything done only in the UI sequence is also skipped. And you cannot > run another installer from the execute sequence; that requires a chainer. > >> PS: I know this approach is somehow quick-and-dirty and not MSDN >> compliant ... but it does a good job ... > > There's nothing wrong with quick, but dirty and unsupported are bad news. > > -- > sig://boB > http://joyofsetup.com/ > > > -- > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] another noob question about customizing the standarddialog sets
Ah in that case it would've been easier to start off with WIXUI_InstallDir & add the required references to InstallScopeDlg where required as that sounds like what you have now. Things are always easier with hindsight but at least you got it working. Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** 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: Dave Combs [mailto:dave.co...@kaazing.com] Sent: 28 April 2011 16:50 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] another noob question about customizing the standarddialog sets Thanks, Pally. Your point about 'the only way to fix is to copy and paste' is what I expected the answer to be. Ultimately what I ended up doing (after I noticed that AdvancedWelcomeEulaDlg also doesn't include a 'Back' button) was to switch to using the WelcomeDlg with the LicenseAgreementDlg, then having that go to the InstallScopeDlg or InstallDirDlg (as the AdvancedWelcomeEulaDlg did). So the user doesn't get an explicit 'Install' button from the EULA dialog, but that's what I was asked to do--the requirement was for something that actually made the users go through the choices (so it was my error to try to use the AdvancedWelcomeEulaDlg in the first place, but at least I learned something from you.) Thanks again, Dave On Thu, Apr 28, 2011 at 4:39 AM, Pally Sandher wrote: > The reason you see the AdvancedWelcomeEulaDlg a second time is because in > AdvancedWelcomeEulaDlg.wxs there is the following: > > >NOT > Installed > > > Hence it's showing up in the InstallUISequence. > > What happens when you click Next on the WelcomeDlg is it does what you've > set the Next button to do. By default in WixUI_Advanced.wxs it spawns > VerifyReadyDlg using the NewDialog function when Next is clicked. You must > have also modified that too if you're getting to the FeaturesDlg somehow > (I'm assuming you've made it spawn AdvancedWelcomeEulaDlg). > > The only way to fix it is to copy & paste the contents of > AdvancedWelcomeEulaDlg.wxs from the WiX source into your code, rename the > Dialog to something unique (e.g. MyAdvancedWelcomeEulaDlg), remove the above > code to stop it showing twice then update the references to point at your > new custom version & remove the references to the original. You'd also want > to change your Before="AdvancedWelcomeEulaDlg">1 to Before="ProgressDlg">1 otherwise it will probably give you problems > building or running as it'll be trying to place a dialog before a dialog > which doesn't exist. > > Palbinder Sandher > Software Deployment Engineer > T: +44 (0) 141 945 8500 > F: +44 (0) 141 945 8501 > > http://www.iesve.com > **Design, Simulate + Innovate with the ** > 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: Dave Combs [mailto:dave.co...@kaazing.com] > Sent: 27 April 2011 19:07 > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] another noob question about customizing the > standarddialog sets > > I'm trying to customize the WixUI_Advanced dialog set, and had something > fairly simple, but it doesn't seem to work the way I expected. I'd like > the > Welcome dialog to show up always (not just when doing a patch), so I copied > the WixUI_Advanced.wxs internals and changed the InstallSequence at the end > to say > >>1 > > (the condition used to be 'Installed AND PATCH'. > > Now, if I run an initial install, things look okay until I get to the end > of > the Feature dialog, at which point the AdvancedEulaDlg shows up. Looking at > the MSI in Orca, I see > the following: > > Action Condition Sequence > WelcomeDlg1 1295 > AdvancedWelcomeEulaDlg NOT Installed 1296 > MaintenanceWelcomeDlg Installed AND NOT RESUME AND NOT Preselected AND > NOT PATCH1297 > ResumeDlg Installed AND (RESUME OR Preselected) > ProgressDlg > ExecuteAction > > The conditions for AdvancedWelcomeEulaDlg and the others are baked into > their .wxs files in UIExtension. I assume what was intended is that during > InstallUISequence, each will be evaluated as an initial condition and that > particular dialog will show up (and none of the others will later evaluate > to true), and then Next and Back definitions will dictate what happens > next. That's reasonable. However, it appears I'm then unable to dictate > my > own initial dialog (WelcomeDlg always, in our case). Is there some way to
Re: [WiX-users] another noob question about customizing the standarddialog sets
Thanks, Pally. Your point about 'the only way to fix is to copy and paste' is what I expected the answer to be. Ultimately what I ended up doing (after I noticed that AdvancedWelcomeEulaDlg also doesn't include a 'Back' button) was to switch to using the WelcomeDlg with the LicenseAgreementDlg, then having that go to the InstallScopeDlg or InstallDirDlg (as the AdvancedWelcomeEulaDlg did). So the user doesn't get an explicit 'Install' button from the EULA dialog, but that's what I was asked to do--the requirement was for something that actually made the users go through the choices (so it was my error to try to use the AdvancedWelcomeEulaDlg in the first place, but at least I learned something from you.) Thanks again, Dave On Thu, Apr 28, 2011 at 4:39 AM, Pally Sandher wrote: > The reason you see the AdvancedWelcomeEulaDlg a second time is because in > AdvancedWelcomeEulaDlg.wxs there is the following: > > >NOT > Installed > > > Hence it's showing up in the InstallUISequence. > > What happens when you click Next on the WelcomeDlg is it does what you've > set the Next button to do. By default in WixUI_Advanced.wxs it spawns > VerifyReadyDlg using the NewDialog function when Next is clicked. You must > have also modified that too if you're getting to the FeaturesDlg somehow > (I'm assuming you've made it spawn AdvancedWelcomeEulaDlg). > > The only way to fix it is to copy & paste the contents of > AdvancedWelcomeEulaDlg.wxs from the WiX source into your code, rename the > Dialog to something unique (e.g. MyAdvancedWelcomeEulaDlg), remove the above > code to stop it showing twice then update the references to point at your > new custom version & remove the references to the original. You'd also want > to change your Before="AdvancedWelcomeEulaDlg">1 to Before="ProgressDlg">1 otherwise it will probably give you problems > building or running as it'll be trying to place a dialog before a dialog > which doesn't exist. > > Palbinder Sandher > Software Deployment Engineer > T: +44 (0) 141 945 8500 > F: +44 (0) 141 945 8501 > > http://www.iesve.com > **Design, Simulate + Innovate with the ** > 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: Dave Combs [mailto:dave.co...@kaazing.com] > Sent: 27 April 2011 19:07 > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] another noob question about customizing the > standarddialog sets > > I'm trying to customize the WixUI_Advanced dialog set, and had something > fairly simple, but it doesn't seem to work the way I expected. I'd like > the > Welcome dialog to show up always (not just when doing a patch), so I copied > the WixUI_Advanced.wxs internals and changed the InstallSequence at the end > to say > >>1 > > (the condition used to be 'Installed AND PATCH'. > > Now, if I run an initial install, things look okay until I get to the end > of > the Feature dialog, at which point the AdvancedEulaDlg shows up. Looking at > the MSI in Orca, I see > the following: > > Action Condition Sequence > WelcomeDlg1 1295 > AdvancedWelcomeEulaDlg NOT Installed 1296 > MaintenanceWelcomeDlg Installed AND NOT RESUME AND NOT Preselected AND > NOT PATCH1297 > ResumeDlg Installed AND (RESUME OR Preselected) > ProgressDlg > ExecuteAction > > The conditions for AdvancedWelcomeEulaDlg and the others are baked into > their .wxs files in UIExtension. I assume what was intended is that during > InstallUISequence, each will be evaluated as an initial condition and that > particular dialog will show up (and none of the others will later evaluate > to true), and then Next and Back definitions will dictate what happens > next. That's reasonable. However, it appears I'm then unable to dictate > my > own initial dialog (WelcomeDlg always, in our case). Is there some way to > remove the 'InstallSequence' items for the other dialogs without actually > copying and modifying the dialog .wxs source files? I couldn't find one, > but would love a pointer to something that explains how to do it. > > Thanks! > Dave > > -- > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > --
Re: [WiX-users] Registering a WMI interface
On 27-Apr-11 13:33, Skildum, Mathew wrote: > Does anyone have any incite as to what happens during WMI registration? Unfortunately, it requires running code, either the mofcomp.exe tool or using the IMofCompiler interface. Nobody's donated any code to WiX to support WMI registration. -- sig://boB http://joyofsetup.com/ -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VC++ redistributable questions
On 28-Apr-11 09:52, Tobias S wrote: > - With this implementation the VCRedist installer runs at a point > where the user can run the installation unattended (for bootstrapper > normally waiting until completion necessary - not considering Burn > here as it is in beta) > - Most installs run in UI mode, otherwise also for InstallExecute a > condition could be integrated. Same scenario must be considered when > designing an installer with a bootstrapper Neither of these is the case: Unattended installs skip the UI sequence so anything done only in the UI sequence is also skipped. And you cannot run another installer from the execute sequence; that requires a chainer. > PS: I know this approach is somehow quick-and-dirty and not MSDN > compliant ... but it does a good job ... There's nothing wrong with quick, but dirty and unsupported are bad news. -- sig://boB http://joyofsetup.com/ -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] CustomAction that needs to figure out the destination path
On 27-Apr-11 03:06, Rune Moberg wrote: > A little googling seems to suggest that the proper way to do this > would be by using a deferred action. If I understand this correctly, > the deferred action will be executed by the installer service and has > a good chance of running elevated. Fine, except I need the list of web > sites in the UI, so that suggests I need an immediate action... You can't get administrator privileges during the UI sequence without starting the .msi with those privileges. -- sig://boB http://joyofsetup.com/ -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: Detecting: additional Package info
On 27-Apr-11 12:13, Vadym Verba wrote: > 1) DetectPackageCompleteEventArgs contains "PackageId". Where could I > use this information? Could I somehow get access to .msi itself, described in > with detected "PackageId"? You can use it to set properties on that package or make decisions about what to show in your BA. See src\Setup\UX\InstallationViewModel.cs, for example. > 2) DetectMsiFeatureEventArgs contains "PackageId" and "FeatureId". How > can I restore Feature hierarchy of detected package? I need to show Features > TreeView but I can't find how to detect proper hierarchy structure. You can get a list of features from the BA manifest, but it doesn't record the hierarchy. -- sig://boB http://joyofsetup.com/ -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VC++ redistributable questions
I guess if there's been no issues in the past with VCRedist we can all safely assume there will never be any issues in the future. > IMHO this approach is worth mentioning it in case of the VCRedist: IMHO this approach isn't worth mentioning because: >- VCRedist.exe is an installer which never caused any trouble itself See above. >- No need doing bootstrapping for VCRedist.exe merge modules are available negating the need for bootstrapping which is what prompted this discussion in the first place. >- With this implementation the VCRedist installer runs at a point >where the user can run the installation unattended (for bootstrapper >normally waiting until completion necessary - not considering Burn >here as it is in beta) See previous. >- Most installs run in UI mode, otherwise also for InstallExecute a >condition could be integrated. Same scenario must be considered when >designing an installer with a bootstrapper Again see previous. >Cons: >- Elevation necessary to get only one UAC prompt Again see previous. >If there exists a good bootstrapper for implementing it in a "chaining >way" I think to re-implement it that way. I haven't looked at Burn yet but dotnetinstaller works pretty much flawlessly for this situation. Until our software required .NET 2.0 Framework we quite happily used the VC++ 8.0 merge modules in our MSI's. I still use them in one product as it's a plug-in for a 3rd party app which requires .NET 2.0. I only switched to bootstrapping the vcredist for our main application because I was already having to bootstrap the .NET 2.0 Framework installer so I thought I may as well leverage the functionality. Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** 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: Tobias S [mailto:tobias.s1...@gmail.com] Sent: 28 April 2011 14:53 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VC++ redistributable questions Hi, Yes I know the issues mentioned in MSDN about concurrent installers. But for the VCRedist.exe there were no issues at our customers site related to this implementation. For OpenOffice I mentioned it as it was the first package where I saw other engineers doing the same approach. I didn't want to state that this is the fact for concurrent installations to be safe. IMHO this approach is worth mentioning it in case of the VCRedist: - VCRedist.exe is an installer which never caused any trouble itself - No need doing bootstrapping for VCRedist.exe - With this implementation the VCRedist installer runs at a point where the user can run the installation unattended (for bootstrapper normally waiting until completion necessary - not considering Burn here as it is in beta) - Most installs run in UI mode, otherwise also for InstallExecute a condition could be integrated. Same scenario must be considered when designing an installer with a bootstrapper Cons: - Elevation necessary to get only one UAC prompt If there exists a good bootstrapper for implementing it in a "chaining way" I think to re-implement it that way. Regards Tobias PS: I know this approach is somehow quick-and-dirty and not MSDN compliant ... but it does a good job ... 2011/4/28 Pally Sandher : > Yeah if OpenOffice use concurrent installations it must be totally > safe http://msdn.microsoft.com/en-us/library/aa368010.aspx > > Stick with using the merge modules and/or a bootstrapper for the vcredist. If > you don't need to bootstrap any other pre-reqs the merge modules are the > easiest way to go. > > Here's how you test whether the merge modules install properly -> > http://www.joyofsetup.com/2007/09/24/test-your-setups-virtually/ > Get yourself a Virtual Machine of any operating system your software > supports. Don't install anything on it other than Windows Updates. Install > your app using the MSI with the merge modules. If it runs, they installed > properly. If you're really worried about the magic voodoo which is making > your application run, go look in the WinSXS directories & see if the runtimes > have been installed. The VC++ 8.0 merge modules put some registry values > under SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Installations so > open your MSI in InstEd!/Orca, check the registry table & look for entries > with components which don't match any you've authored to see if the v9.0 ones > do too. > > Palbinder Sandher > Software Deployment Engineer > T: +44 (0) 141 945 8500 > F: +44 (0) 141 945 8501 > > http://www.iesve.com > **Design, Simulate + Innovate with the ** > Integrated Environmental Solutions Limited. Registered in Scotland No. > SC151456 > Registered Office - Helix Building, West Of Scotland Scien
Re: [WiX-users] VC++ redistributable questions
Hi,
Yes I know the issues mentioned in MSDN about concurrent installers.
But for the VCRedist.exe there were no issues at our customers site
related to this implementation. For OpenOffice I mentioned it as it
was the first package where I saw other engineers doing the same
approach. I didn't want to state that this is the fact for concurrent
installations to be safe.
IMHO this approach is worth mentioning it in case of the VCRedist:
- VCRedist.exe is an installer which never caused any trouble itself
- No need doing bootstrapping for VCRedist.exe
- With this implementation the VCRedist installer runs at a point
where the user can run the installation unattended (for bootstrapper
normally waiting until completion necessary - not considering Burn
here as it is in beta)
- Most installs run in UI mode, otherwise also for InstallExecute a
condition could be integrated. Same scenario must be considered when
designing an installer with a bootstrapper
Cons:
- Elevation necessary to get only one UAC prompt
If there exists a good bootstrapper for implementing it in a "chaining
way" I think to re-implement it that way.
Regards
Tobias
PS: I know this approach is somehow quick-and-dirty and not MSDN
compliant ... but it does a good job ...
2011/4/28 Pally Sandher :
> Yeah if OpenOffice use concurrent installations it must be totally
> safe http://msdn.microsoft.com/en-us/library/aa368010.aspx
>
> Stick with using the merge modules and/or a bootstrapper for the vcredist. If
> you don't need to bootstrap any other pre-reqs the merge modules are the
> easiest way to go.
>
> Here's how you test whether the merge modules install properly ->
> http://www.joyofsetup.com/2007/09/24/test-your-setups-virtually/
> Get yourself a Virtual Machine of any operating system your software
> supports. Don't install anything on it other than Windows Updates. Install
> your app using the MSI with the merge modules. If it runs, they installed
> properly. If you're really worried about the magic voodoo which is making
> your application run, go look in the WinSXS directories & see if the runtimes
> have been installed. The VC++ 8.0 merge modules put some registry values
> under SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Installations so
> open your MSI in InstEd!/Orca, check the registry table & look for entries
> with components which don't match any you've authored to see if the v9.0 ones
> do too.
>
> Palbinder Sandher
> Software Deployment Engineer
> T: +44 (0) 141 945 8500
> F: +44 (0) 141 945 8501
>
> http://www.iesve.com
> **Design, Simulate + Innovate with the **
> 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: Tobias S [mailto:tobias.s1...@gmail.com]
> Sent: 28 April 2011 08:47
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] VC++ reditributable questions
>
> Maybe you should consider to use the VCRedist installer instead of the
> merge module.
>
> Actually that's not the recommended way as you e.g. have to run an
> installer in InstallUI sequence but it works (saw it also e.g. in
> OpenOffice installer). The recommended way for installing the VCRedist
> installer would be using it in a bootstrapper app.
>
> If you want to go the "unofficial" way with InstallUI maybe following
> snippets help and can be modified easily for other VCRedist.exes:
>
> 2008 SP1 x86 vcredist_x86.exe:
>
>
> Key="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{9A25302D-30C0-39D9-BD6F-21E6EC160475}"
> Name="Publisher" Type="raw" Win64="no" />
>
> Return="check" Execute="immediate" BinaryKey="vc2008SP1Redist_x86.exe"
> ExeCommand="/qb"/>
> SourceFile="$(sys.SOURCEFILEDIR)\vcredist_x86.exe"/>
>
> After="ProgressDlg">Not Installed And Not VC2008SP1REDIST_X86
>
>
> or for 2010 SP1 x86 vcredist_x86.exe as it cannot be installed anymore
> side by side as 2005 and 2008 VCRedists:
>
>
>
> OnlyDetect='yes'
> Property='VC2010SP1REDIST_X86'
> Minimum='10.0.40219'
> IncludeMinimum='yes'/>
>
> Return="check" Execute="immediate" BinaryKey="vc2010SP1Redist_x86.exe"
> ExeCommand="/passive /norestart"/>
> SourceFile="$(sys.SOURCEFILEDIR)\vcredist_x86.exe"/>
>
> After="ProgressDlg">Not Installed And Not VC2010SP1REDIST_X86
>
>
>
>
> 2011/4/27 Wilson, Phil :
>> A merge module is merged into your MSI and becomes part of it, so you'll
>> never find any evidence of VC runtime in Add/Remove Programs. If the VC++
>> files are already installed then yours won't be, perhaps subject to file
>> version replacement rules, but if it's in the WinSxS folder you may see
>> multiple version of the VC++ files.
>>
>> I'm not sure that there are any registry entries for the VC files. You could
>> install with a verbose log and see what happens to the V
[WiX-users] AUTO: Kenneth L Resler is out of the office. (returning 04/29/2011)
I am out of the office until 04/29/2011. I will be out of the office, with limited email and phone access. Note: This is an automated response to your message "Re: [WiX-users] another noob question about customizing the standarddialog sets" sent on 4/28/2011 6:39:56 AM. This is the only notification you will receive while this person is away. Disclaimer: Information in this message or an attachment may be government data and thereby subject to the Minnesota Government Data Practices Act, Minnesota Statutes, Chapter 13, may be subject to attorney-client or work product privilege, may be confidential, privileged, proprietary, or otherwise protected, and the unauthorized review, copying, retransmission, or other use or disclosure of the information is strictly prohibited. If you are not the intended recipient of this message, please immediately notify the sender of the transmission error and then promptly delete this message from your computer system. -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Run MSI with logging from Setup.exe
Hello All, I want my msi to run always with /l*v logfile command parameters from setup.exe. I am generating setup.exe from Bootstrapper Manifest Generator. setup.exe will pass the command line parameters to msi file.but I dont want to send parameters to setup.exe to send to msi. I want msi to run always with logging from setup.exe without passing any parameters. If anybody know the solution or any thoughts will be appreciated. Thanks in advance, Loknath -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Run MSI with logging from Setup.exe
Check out the MsiLogging property. Windows Installer 4.0 and above is necessary, but that will handle Vista and later. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Run-MSI-with-logging-from-Setup-exe-tp6311287p6312901.html Sent from the wix-users mailing list archive at Nabble.com. -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] another noob question about customizing the standarddialog sets
The reason you see the AdvancedWelcomeEulaDlg a second time is because in AdvancedWelcomeEulaDlg.wxs there is the following: NOT Installed Hence it's showing up in the InstallUISequence. What happens when you click Next on the WelcomeDlg is it does what you've set the Next button to do. By default in WixUI_Advanced.wxs it spawns VerifyReadyDlg using the NewDialog function when Next is clicked. You must have also modified that too if you're getting to the FeaturesDlg somehow (I'm assuming you've made it spawn AdvancedWelcomeEulaDlg). The only way to fix it is to copy & paste the contents of AdvancedWelcomeEulaDlg.wxs from the WiX source into your code, rename the Dialog to something unique (e.g. MyAdvancedWelcomeEulaDlg), remove the above code to stop it showing twice then update the references to point at your new custom version & remove the references to the original. You'd also want to change your 1 to 1 otherwise it will probably give you problems building or running as it'll be trying to place a dialog before a dialog which doesn't exist. Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** 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: Dave Combs [mailto:dave.co...@kaazing.com] Sent: 27 April 2011 19:07 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] another noob question about customizing the standarddialog sets I'm trying to customize the WixUI_Advanced dialog set, and had something fairly simple, but it doesn't seem to work the way I expected. I'd like the Welcome dialog to show up always (not just when doing a patch), so I copied the WixUI_Advanced.wxs internals and changed the InstallSequence at the end to say 1 (the condition used to be 'Installed AND PATCH'. Now, if I run an initial install, things look okay until I get to the end of the Feature dialog, at which point the AdvancedEulaDlg shows up. Looking at the MSI in Orca, I see the following: Action Condition Sequence WelcomeDlg1 1295 AdvancedWelcomeEulaDlg NOT Installed 1296 MaintenanceWelcomeDlg Installed AND NOT RESUME AND NOT Preselected AND NOT PATCH1297 ResumeDlg Installed AND (RESUME OR Preselected) ProgressDlg ExecuteAction The conditions for AdvancedWelcomeEulaDlg and the others are baked into their .wxs files in UIExtension. I assume what was intended is that during InstallUISequence, each will be evaluated as an initial condition and that particular dialog will show up (and none of the others will later evaluate to true), and then Next and Back definitions will dictate what happens next. That's reasonable. However, it appears I'm then unable to dictate my own initial dialog (WelcomeDlg always, in our case). Is there some way to remove the 'InstallSequence' items for the other dialogs without actually copying and modifying the dialog .wxs source files? I couldn't find one, but would love a pointer to something that explains how to do it. Thanks! Dave -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] VC++ redistributable questions
Yeah if OpenOffice use concurrent installations it must be totally safe http://msdn.microsoft.com/en-us/library/aa368010.aspx Stick with using the merge modules and/or a bootstrapper for the vcredist. If you don't need to bootstrap any other pre-reqs the merge modules are the easiest way to go. Here's how you test whether the merge modules install properly -> http://www.joyofsetup.com/2007/09/24/test-your-setups-virtually/ Get yourself a Virtual Machine of any operating system your software supports. Don't install anything on it other than Windows Updates. Install your app using the MSI with the merge modules. If it runs, they installed properly. If you're really worried about the magic voodoo which is making your application run, go look in the WinSXS directories & see if the runtimes have been installed. The VC++ 8.0 merge modules put some registry values under SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Installations so open your MSI in InstEd!/Orca, check the registry table & look for entries with components which don't match any you've authored to see if the v9.0 ones do too. Palbinder Sandher Software Deployment Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** 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: Tobias S [mailto:tobias.s1...@gmail.com] Sent: 28 April 2011 08:47 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] VC++ reditributable questions Maybe you should consider to use the VCRedist installer instead of the merge module. Actually that's not the recommended way as you e.g. have to run an installer in InstallUI sequence but it works (saw it also e.g. in OpenOffice installer). The recommended way for installing the VCRedist installer would be using it in a bootstrapper app. If you want to go the "unofficial" way with InstallUI maybe following snippets help and can be modified easily for other VCRedist.exes: 2008 SP1 x86 vcredist_x86.exe: Not Installed And Not VC2008SP1REDIST_X86 or for 2010 SP1 x86 vcredist_x86.exe as it cannot be installed anymore side by side as 2005 and 2008 VCRedists: Not Installed And Not VC2010SP1REDIST_X86 2011/4/27 Wilson, Phil : > A merge module is merged into your MSI and becomes part of it, so you'll > never find any evidence of VC runtime in Add/Remove Programs. If the VC++ > files are already installed then yours won't be, perhaps subject to file > version replacement rules, but if it's in the WinSxS folder you may see > multiple version of the VC++ files. > > I'm not sure that there are any registry entries for the VC files. You could > install with a verbose log and see what happens to the VC++ files, and look > in Windows\WinSxS for new files. And is that feature really being installed? > I also don't think the files will actually go into TARGETDIR from meerge > modules, just in case you were looking there. > > Phil Wilson > > -Original Message- > From: Francisco Gabriel Malbrán [mailto:fgmalb...@gmail.com] > Sent: Wednesday, April 27, 2011 10:48 AM > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] VC++ reditributable questions > > Hello. > > First: the context: WiX v3.5, Windows 7 Enterprise > > I'm intending to install the VC++ 9.0 redistributable from it's msm as > described in WiX's official documentation page [0] > Yet, even when my msi size augments in the same size as the msm and I can > see with Orca entrances related to the msm, I think it does not get > installed. > > What I've done in my code is: > > > SourceFile="$(var.DependencesDir)Microsoft_VC90_CRT_x86.msm" DiskId="1" > Language="0"/> > > > Display="hidden" Level="1"> > > > > The code compiles and throws some warnings as expected and detailed in the > documentation. It does however, throw some other errors[1] but I've searched > the web and found that these are also expected from using mergemod.dll[2] > > Whenever installing, however, I can't find any evidence that the VC++ > redistributable package has been installed. I don't find it in Add/Remove > programs. I don't find registry keys associated with it. Etc. > 1. Is this the correct way to check? > 2. What can I do if in fact, the package is not being installed? (I need > some hint on where to look now) > > Thanks in advance. > > [0] > http://wix.sourceforge.net/manual-wix3/install_vcredist.htm > > [1] > light.exe(0,0): warning LGHT1076: ICE82: This action > SystemFolder.21022.08.Microsoft_VC90_CRT_x86.RTM.0138F525_6C8A_333F_A105_14AE030B9A54 > has duplicate sequence number 2 in the table InstallUISequence > 1>light.exe(0,0): warning LGHT1076: ICE82: This action > SystemFolder.21022.08.Microsoft_V
Re: [WiX-users] VC++ reditributable questions
Maybe you should consider to use the VCRedist installer instead of the merge module. Actually that's not the recommended way as you e.g. have to run an installer in InstallUI sequence but it works (saw it also e.g. in OpenOffice installer). The recommended way for installing the VCRedist installer would be using it in a bootstrapper app. If you want to go the "unofficial" way with InstallUI maybe following snippets help and can be modified easily for other VCRedist.exes: 2008 SP1 x86 vcredist_x86.exe: Not Installed And Not VC2008SP1REDIST_X86 or for 2010 SP1 x86 vcredist_x86.exe as it cannot be installed anymore side by side as 2005 and 2008 VCRedists: Not Installed And Not VC2010SP1REDIST_X86 2011/4/27 Wilson, Phil : > A merge module is merged into your MSI and becomes part of it, so you'll > never find any evidence of VC runtime in Add/Remove Programs. If the VC++ > files are already installed then yours won't be, perhaps subject to file > version replacement rules, but if it's in the WinSxS folder you may see > multiple version of the VC++ files. > > I'm not sure that there are any registry entries for the VC files. You could > install with a verbose log and see what happens to the VC++ files, and look > in Windows\WinSxS for new files. And is that feature really being installed? > I also don't think the files will actually go into TARGETDIR from meerge > modules, just in case you were looking there. > > Phil Wilson > > -Original Message- > From: Francisco Gabriel Malbrán [mailto:fgmalb...@gmail.com] > Sent: Wednesday, April 27, 2011 10:48 AM > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] VC++ reditributable questions > > Hello. > > First: the context: WiX v3.5, Windows 7 Enterprise > > I'm intending to install the VC++ 9.0 redistributable from it's msm as > described in WiX's official documentation page [0] > Yet, even when my msi size augments in the same size as the msm and I can > see with Orca entrances related to the msm, I think it does not get > installed. > > What I've done in my code is: > > > SourceFile="$(var.DependencesDir)Microsoft_VC90_CRT_x86.msm" DiskId="1" > Language="0"/> > > > Display="hidden" Level="1"> > > > > The code compiles and throws some warnings as expected and detailed in the > documentation. It does however, throw some other errors[1] but I've searched > the web and found that these are also expected from using mergemod.dll[2] > > Whenever installing, however, I can't find any evidence that the VC++ > redistributable package has been installed. I don't find it in Add/Remove > programs. I don't find registry keys associated with it. Etc. > 1. Is this the correct way to check? > 2. What can I do if in fact, the package is not being installed? (I need > some hint on where to look now) > > Thanks in advance. > > [0] > http://wix.sourceforge.net/manual-wix3/install_vcredist.htm > > [1] > light.exe(0,0): warning LGHT1076: ICE82: This action > SystemFolder.21022.08.Microsoft_VC90_CRT_x86.RTM.0138F525_6C8A_333F_A105_14AE030B9A54 > has duplicate sequence number 2 in the table InstallUISequence > 1>light.exe(0,0): warning LGHT1076: ICE82: This action > SystemFolder.21022.08.Microsoft_VC90_CRT_x86.RTM.0138F525_6C8A_333F_A105_14AE030B9A54 > has duplicate sequence number 2 in the table AdminUISequence > 1>light.exe(0,0): warning LGHT1076: ICE82: This action > SystemFolder.21022.08.Microsoft_VC90_CRT_x86.RTM.0138F525_6C8A_333F_A105_14AE030B9A54 > has duplicate sequence number 2 in the table AdvtExecuteSequence > > [2] > http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/ICE82-Warnings-from-duplicate-sequence-number-created-from-lt-Directory-gt-elements-using-Merge-Modus-td687752.html > Particularly: > *Duplicate* *sequence* *numbers* are not a problem as long as you don't > need *the* > order of *the* CustomActions to be consistent. *These* type 51 > CustomActions' > order relative to each other shouldn't be important. > > Also, this is not a light.exe issue. *The* behavior you are seeing is from > mergemod.dll provided by *the* Windows *Installer* SDK. > > -- > Francisco > -- > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > *** Confidentiality Notice: This e-mail, including any associated or attached > files, is intended solely for the individual or entity to which it is > addressed. This e-mail is confidential and may well also be legally > privileged. If
Re: [WiX-users] old unanswered question regarding to Dialog Close button
Did a short test where [X] was enabled when disabling the Cancel button. So seems to be disabled only when removing [Cancel] and not on the ExitDialog... 2011/4/27 Blair : > I'm curious: what happens if you include but disable the cancel button? > > -Original Message- > From: Tobias S [mailto:tobias.s1...@gmail.com] > Sent: Wednesday, April 27, 2011 5:13 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] old unanswered question regarding to Dialog Close > button > > hmmm ... just, by accident figured out something interesting. The [X] > seems to correspond with the [Cancel] Button. So when removing the > Cancel button the "Dialog Close / [X]" gets disabled. Unfortunately > this seems not be working for the ExitDialog. > > > 2011/4/27 Tobias S : >> afaik not possible except for modal dialogs. Assume here Tramontana >> shows such one. >> >> By default this is not a possible requirement for Windows Installer. >> >> Regards, >> Tobias >> >> >> 2011/4/27 william lee : >>> Hi, >>> I searched a lot online, but did not hit a result. >>> The question is how the installer make the decision to enable or disable > the >>> dialog X(close) button on top right corner. >>> There is no dialog attribute to control it, but sometimes it just > disabled, >>> for example: >>> http://www.tramontana.co.hu/wix/lesson8.php#8.1 >>> The first sample dialog just have X button disabled. >>> >>> I have a requirement that want to disable this X button on the finish >>> install dialog, no idea how to do it. >>> Any one know some internal "undocumented" information? :) >>> >>> thanks, >>> William L. >>> > > -- >>> WhatsUp Gold - Download Free Network Management Software >>> The most intuitive, comprehensive, and cost-effective network >>> management toolset available today. Delivers lowest initial >>> acquisition cost and overall TCO of any competing solution. >>> http://p.sf.net/sfu/whatsupgold-sd >>> ___ >>> WiX-users mailing list >>> WiX-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wix-users >>> >> > > > -- > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
