Yes, that would explain it then!
Thank you,
Brad

-----Original Message-----
From: David Connet [mailto:d...@agilityrecordbook.com] 
Sent: Thursday, July 25, 2013 11:12 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problem using type 1 custom action

Maybe because GetVersionEx lies for a certain class of programs
(installers). And for all programs on Win8.1 unless you specifically
manifest that you support 8.1.

http://msdn.microsoft.com/en-us/library/windows/desktop/ms724451%28v=vs.85%2
9.aspx provides some details in the user comments...

Dave
<rant version="nice">Sometimes backwards compatibility sucks</rant>




________________________________
 From: Astro Flea <astrof...@gmail.com>
To: wix-users@lists.sourceforge.net; astrof...@gmail.com 
Sent: Thursday, July 25, 2013 1:41 PM
Subject: [WiX-users] Problem using type 1 custom action
 

Hello,

I'm creating my first installation package with WiX, and there seems to be
a problem. My MSI package tries to check for and facilitate the
installation of DirectX 11 with the helper DLL and EXE files available here:

http://msdn.microsoft.com/en-us/library/windows/desktop/ee416644%28v=vs.85%2
9.aspx

I'm implementing the 3rd method indicated at the linked site, because the
example is the most thorough in that case. I've got this working, but when
I run this package on my Windows 7 development machine, a DLL function (in
D3D11InstallHelper.dll) identifies my OS as Windows Vista (The exported
function CheckDirect3D11Status uses GetVersionEx to identify the OS). I
know this because I've added debugging code to the DLL that writes to a log
file. But when I use the DLL outside of the WiX installer, it correctly
identifies my OS as Windows 7 with SP1.

Ultimately, it appears as though the consequences of this discrepancy
aren't serious, because when D3D11Install.exe is later called in a
different custom action, it does detect that DirectX 11 is already
installed and that the system is up-to-date. But clearly (I think),
something isn't working right. I've looked at all the relevant files, and
they don't seem to be set to run in any kind of Windows Vista
"compatibility mode", so why would the DLL not recognize my OS?
Thanks,
Brad

P.S. I'm using WiX Toolset 3.7
----------------------------------------------------------------------------
--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------------
--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to