Thanks Rob.  I submitted a bug for this.  I don't expect any of the Wix
toolset to work on Windows 2000.  If it does, that's great, but
obviously not a requirement.  I'd rather have all the other cool stuff
you guys do, rather than making the build tools work on Windows 2000. I
haven't seen any other issues running setupexe wrapper on that platform
and I have a couple setup's using it right now.

I made the fix on my copy of the source code for setupexe and everything
runs fine there for me.

Thanks,
Mike Ballou

-----Original Message-----
From: Rob Mensching [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, May 21, 2008 8:34 AM
To: Rob Mensching; Michael Ballou; wix-users@lists.sourceforge.net
Subject: RE: setupexe and CompareString on Windows 2000
Importance: Low

Sorry, to be clear, when I say "we don't work on Win2000", I meant we
don't have any dev or test boxes with Win2k that we're doing work with
WiX on.  That's how these bugs slip by.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rob
Mensching
Sent: Wednesday, May 21, 2008 08:32
To: Michael Ballou; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] setupexe and CompareString on Windows 2000

Bug.  We don't work on Win2000 much anymore but in general this should
work.  Honestly, I missed that comment in the documentation.  Please, do
open a bug on it so we can ensure it gets fixed... and maybe I should
start looking around for a Win2k VHD.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Michael
Ballou
Sent: Tuesday, May 20, 2008 11:33
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] setupexe and CompareString on Windows 2000

I know there were some discussions before regarding the proper use of
CompareString() in the Wix sources, but I can't seem to find them.  I
found a problem running the setupexe.exe in Wix on Windows 2000.  The
command line parsing which uses CompareString is failing because of the
LOCALE_INVARIANT which apparently is only available on Windows XP and
higher.

According to MSDN it should be like this:

On Windows XP and later:
        CompareString(LOCALE_INVARIANT, NORM_IGNORECASE, mystr, -1,
_T("InLap"), -1);
For earlier operating systems:
        DWORD lcid = MAKELCID(MAKELANGID(LANG_ENGLISH,
SUBLANG_ENGLISH_US), SORT_DEFAULT);
            CompareString(lcid, NORM_IGNORECASE, mystr, -1, _T("InLap"),
-1);

Is this a bug in Wix, or was it designed this way?

Thanks,
Mike Ballou

------------------------------------------------------------------------
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to