I have created a http://pastebin.com/FfkW7TUN WIC bootstrapper package , and
added dependencies on it to the existing .NET 4 packages using the
tag. This makes the bootstrapper engine order the
packages properly. Tested on XP SP2, XP SP3 and Windows 7.
--
View this message in c
On Wed, 8 Sep 2010 06:57:49 -0700
Rob Mensching wrote:
> The issue you are seeing is probably the managed code not launching
> for some reason. There should be a log file in %TEMP% called
> something "Wix" that hopefully will pinpoint the issue. If nt, we
> need to add more logging. :)
It seems
fice - Helix Building, West Of Scotland Science Park,
> Glasgow G20 0SP
> Email Disclaimer
>
> -Original Message-
> From: Tobias S [mailto:tobias.s1...@gmail.com]
> Sent: 09 September 2010 10:09
> To: General discussion for Windows Installer XML toolset.
> Subject:
age-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: 09 September 2010 10:09
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] .Net 4 bootstrapper with Windows Imaging
Component
Matt,
think they did it as it is not officially supported for the platform o
XML toolset.
Subject: Re: [WiX-users] .Net 4 bootstrapper with Windows Imaging
Component
Nick,
How exactly did switching to the DotNetInstaller bootstrapper help you
out with this? Did you manage to package the windows imaging component
so the bootstrapper will install it before .Net? If
tobias.s1...@gmail.com]
> Sent: Thursday, 9 September 2010 12:01 AM
> Cc: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] .Net 4 bootstrapper with Windows Imaging Component
>
> Hm... ok. Just tried to configure a bootstrapper to install the .net
>
On Wed, 8 Sep 2010 16:00:30 +0200
Tobias S wrote:
> Which OS were you running ?
I was running Windows 7 x64 checked. The problem is that .NET 4 doesn't
install c:\windows\system32\mscoree.dll if the Windows build number
is less than that of Windows 7 free RTM - and the checked build is.
The issu
as.s1...@gmail.com]
Sent: Thursday, 9 September 2010 12:01 AM
Cc: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] .Net 4 bootstrapper with Windows Imaging Component
Hm... ok. Just tried to configure a bootstrapper to install the .net
4.0 client profile and ran into the same
..@zaptechnology.com]
Sent: 08 September 2010 08:20
To: General discussion for Windows Installer XML
toolset.(wix-users@lists.sourceforge.net)
Subject: [WiX-users] .Net 4 bootstrapper with Windows Imaging Component
Hi All,
I'm trying to create a bootstrapper to install .Net 4. It works fine in
ge
Hm... ok. Just tried to configure a bootstrapper to install the .net
4.0 client profile and ran into the same issue as well :-) Was on a XP
SP2. After installing the
wic_x86_enu.exe installation of .net 4.0 sucedded. Ok. From my current
point of view it seems the following:
.Net 4.0 Supported Oper
Hmm, it should be. From wix36\src\Setup\Bundle\Netfx.wxs:
http://download.microsoft.com/download/9/5/A/95A9616B-7A37-4AF6-BC36-D6EA96C8DAAE/dotNetFx40_Full_x86_x64.exe
"
DetectCondition="Netfx4FullVersion AND (NOT
VersionNT64 OR Netfx
On Wed, 8 Sep 2010 14:21:58 +0200
Tobias S wrote:
> For the older versions of the Framework I always used the reg
> detection mechanism which was also the Microsoft recommended way
> (Sorry don't know the MSDN reference at the moment). InstallShield
> also uses the reg detection for 4.0 versions:
For the older versions of the Framework I always used the reg
detection mechanism which was also the Microsoft recommended way
(Sorry don't know the MSDN reference at the moment). InstallShield
also uses the reg detection for 4.0 versions:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\N
On Wed, 8 Sep 2010 11:17:29 +0100
"Nick Ball" wrote:
> The package that comes with Visual Studio (which I assume you are
> currently using) does the same registry check. From the product.xml
> file:
>
>
> Key="HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Full"
> Value="Version" />
C:\Program Files\Microsoft
SDKs\Windows\v7.0A\Bootstrapper\Packages\DotNetFX40
-Nick
-Original Message-
From: Bruce Cran [mailto:br...@cran.org.uk]
Sent: 08 September 2010 10:53
To: Nick Ball
Cc: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] .Net 4 bootstr
On Wed, 8 Sep 2010 10:39:24 +0100
"Nick Ball" wrote:
> Why do you need to check the version of mscoree? Isn't the registry
> key check sufficient?
It seems that WiX 3.6 doesn't use the registry key for checking the
version of .NET either; at least, after rebooting having installed 4.0
it wanted
On Wed, 8 Sep 2010 10:39:24 +0100
"Nick Ball" wrote:
> Why do you need to check the version of mscoree? Isn't the registry
> key check sufficient?
>
> http://msdn.microsoft.com/en-us/library/ee942965.aspx#detecting_net_fram
> ework
My (simple) application should continue to work on future vers
neral discussion for Windows Installer XML toolset.
Cc: Nick Ball
Subject: Re: [WiX-users] .Net 4 bootstrapper with Windows Imaging
Component
On Wed, 8 Sep 2010 09:55:43 +0100
"Nick Ball" wrote:
> We ended up switching to DotNetInstaller for bootstrapping .Net 4.0
>
> http://dotn
On Wed, 8 Sep 2010 09:55:43 +0100
"Nick Ball" wrote:
> We ended up switching to DotNetInstaller for bootstrapping .Net 4.0
>
> http://dotnetinstaller.codeplex.com/
One problem I've come across with bootstrapping .NET 4 is that if you
check the version of mscoree.dll to see if it's 4.0 or newer
0 08:20
To: General discussion for Windows Installer XML
toolset.(wix-users@lists.sourceforge.net)
Subject: [WiX-users] .Net 4 bootstrapper with Windows Imaging Component
Hi All,
I'm trying to create a bootstrapper to install .Net 4. It works fine in
general, but fails with an error code 5100 o
Hi Matt,
First of all I never developed a .Net 4. Bootstrapper. But actually I
use the InstallShield Environment with a configuration for such a
bootstrapper. So in total they use the downloaded version of the
client profile dotNetFx40_Client_x86_x64.exe
(http://download.microsoft.com/download/5/6
Hi All,
I'm trying to create a bootstrapper to install .Net 4. It works fine in
general, but fails with an error code 5100 on machines that don't have the
"Windows Imaging Component" already installed. If you run the .Net installer
separately it shows an error dialog that windows imaging is mis
22 matches
Mail list logo
