discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a
valid
Win32 application
I agree with dropping support for Win2k but what is a shame is that
running
the exe doesn't display a more useful error message. I don't suppose
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, May 09, 2012 05:44
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a
valid
Win32 application
To pass a security
On 09/05/2012 20:49, James Johnston wrote:
Vista too?!
No, they're just dropping support for XP/Server 2003.
--
Bruce Cran
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's
May 2012 20:49
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid
Win32 application
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, May 09, 2012 05:44
To: General
-Original Message-
From: Bruce Cran [mailto:br...@cran.org.uk]
Sent: 09 May 2012 21:23
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid
Win32 application
On 09/05/2012 20:49, James Johnston wrote:
Vista
On 09/05/2012 22:09, Neil Sleightholm wrote:
That isn't what Rob said Next version will be even more interesting since
last I checked VS11 CRT only supports Win7+ (which I believe cuts support for
WinXP SP3 and Vista before they are out of service).
A bit off topic but does anyone know
cycle!)
James
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Monday, April 30, 2012 15:57
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a
valid
Win32 application
Sadly no. CRT dies before ever loading Burn code.
On Mon, Apr 30, 2012 at 8:57 AM, Neil Sleightholm n...@x2systems.comwrote:
I agree with dropping support for Win2k but what is a shame is that
running the exe doesn't display a more useful error message. I don't
suppose there is anything that
...@accelitec.com]
Sent: Wednesday, May 02, 2012 19:28
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a
valid
Win32 application
The problem surfaced when I started bundling my MSI packages in order to
take advantage of bootstrapping
had such a long life cycle!)
James
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Monday, April 30, 2012 15:57
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a
valid
Win32
on WIN2K machine .exe is not a
valid
Win32 application
I agree with dropping support for Win2k but what is a shame is that
running
the exe doesn't display a more useful error message. I don't suppose there
is
anything that can be done to change this?
Neil
The problem surfaced when I started bundling my MSI packages in order to take
advantage of bootstrapping the perquisites like .NET Framework 2.0 SP2, C++
run time libraries. We've been careful to build all of our client adapters
in .NET 2.0/VS2008 since WIN2K is still widely used in the retail
I agree with dropping support for Win2k but what is a shame is that running the
exe doesn't display a more useful error message. I don't suppose there is
anything that can be done to change this?
Neil
--
Live Security
All,
Thanks for clearing that up. In the end not having a WIN2K bundle isn't that
big a deal; the .MSI's run flawlessly and that's what counts. So a quick
note of appreciation:
We've been using WiX for almost three years to deploy/update client API
adapters that connect 3rd party POS systems
If you vowed never to build WiX again, then it probably is not feasible.
Burn is in wix\src\burn (burn.build) and as Bob noted if you want wixstdba
then you'll need to build wix\src\ext\BalExtension\wixsdtba.
Both are in WiX so that will require breaking your vow. smile/
On Sat, Apr 28, 2012 at
NOTE: Win2k was out of support before WiX v3.6 even started development. We
obviously don't test the code there so I really have no idea how much work
it will be to make any of the native code built by WiX (Burn, and
CustomActions mainly) working on Win2k.
On Sun, Apr 29, 2012 at 12:04 AM, Rob
'Out of support' is just a marketing term. It doesn't mean it
magically stops working. People forget that often.
Alex
On 29 April 2012 08:06, Rob Mensching r...@robmensching.com wrote:
NOTE: Win2k was out of support before WiX v3.6 even started development. We
obviously don't test the code
No, we don't forget that. However, at some point you have to trim your tail
or you end up with an enormous support burden that prevents you from moving
forward.
One of the big questions for us in WiX v3.7 is how many versions of VS
should we support? It is expensive to keep VS2005 and VS2008
Is that not the wrong question? Rather than getting caught up in the
ins and outs of which version to support, why not adopt methods that
remove the decision entirely?
Have you considered using CMake, for example, which generates build
files for a vast range of build platforms (including VS 6 -
I fundamentally agree with you. However, building the code for a particular
platform is the easiest part of the problem. Keeping the code working
(since the platforms differ in subtle ways) is the real challenge.
Personally, supporting unsupported platforms is very low on my priority
list. I have
That's just stopped me in my tracks. I've been converting our
dotnetinstaller bootstrapper to use Burn but had no idea that would
kill our Win2k support. Seriously not good.
Is there a way round this? Can I easily compile the bootstrapper
application myself with VS 2005?
Thanks,
Alex
On 28
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 28 April 2012 05:06
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Bundle fails on WIN2K machine .exe is not a valid
Win32 application
No. Windows 2000 is not supported by the VS 2010 CRT
On 28-Apr-12 08:08, Alexander Lamaison wrote:
Is there a way round this? Can I easily compile the bootstrapper
application myself with VS 2005?
You'd have to do the same thing to all of Burn too.
--
sig://boB
http://joyofsetup.com/
On 28 April 2012 21:18, Bob Arnson b...@joyofsetup.com wrote:
On 28-Apr-12 08:08, Alexander Lamaison wrote:
Is there a way round this? Can I easily compile the bootstrapper
application myself with VS 2005?
You'd have to do the same thing to all of Burn too.
Is this feasible? I once tried to
It sounds like my best option is to simply compile my installers using VS
2008. Is there any reason not to take that approach?
Rich
-
Rich Dingle
Accelitec, Inc.
--
View this message in context:
Is the WiX Standard Bootstrapper Application compatible with Windows 2000? My
individual MSI packages all work fine but all my bundles fail immediately even
if I save them to a local folder: [bundleName].exe is not a valid Win32
application.
Target Machine:
Win2K Pro SP4 w/KB891861 'roll up'
No. Windows 2000 is not supported by the VS 2010 CRT. Windows XP (I think
SP1+).
On Fri, Apr 27, 2012 at 2:34 PM, Rich Dingle rdin...@accelitec.com wrote:
Is the WiX Standard Bootstrapper Application compatible with Windows 2000?
My individual MSI packages all work fine but all my bundles fail
27 matches
Mail list logo
