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 os...@live.com: I'm curious: what happens if you include but disable the cancel button? -Original Message- From:

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

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

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: InstallUISequence Show Dialog=AdvancedWelcomeEulaDlg Before=ProgressDlgNOT Installed/Show /InstallUISequence Hence it's showing up in the

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] 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

[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

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

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

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 Chain with detected PackageId? You can use it to set properties on that package or make decisions about

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

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,

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. --

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,

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

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,

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

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?

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

[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

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

[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

[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.