Hi,
maybe something regarding VS Merge modules vs. VCRedist or in general
my dislike of merge modules:
- Bad personal (+ colleagues) experience (merge modules in general)
- Servicing
- German literature stating "Applications should not be based on
Mergemodules for the installation of components
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 install
d 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 o
> 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?
---
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.
Subje
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, otherwi
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 mo
riginal 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 fo
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
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 wa
>
>
> -Original Message-
> From: Koji Ishii [mailto:kojii...@gmail.com]
> Sent: Thursday, May 28, 2009 3:36 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] VC++ redistributable
>
> Using the bootstrapper worked for me.
installation?
Thanks,
Rahul.
-Original Message-
From: Koji Ishii [mailto:kojii...@gmail.com]
Sent: Thursday, May 28, 2009 3:36 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] VC++ redistributable
Using the bootstrapper worked for me.
http
Using the bootstrapper worked for me.
http://wix.sourceforge.net/manual-wix3/install_dotnet.htm
I use bootstrapper to install VC++ redistributable as well.
Note that, even though I mentioned to run setup.exe rather than msi in
my document, a lot of users tried to install by double-clicking msi.
Hi
> Is there any other way to install vc++ redistributable file and .net
> framework sp1 installer through our .msi installler
>
You can use the merge modules provided by MS for the vc++ redistributables.
Here is what I use for this in WiX:
http://schemas.microsoft.com/wix/2006/wi";>
14 matches
Mail list logo
