Why Custom Actions get a Windows Vista Version Lie on Windows 7

re: Why Custom Actions get a Windows Vista Version Lie on Windows 7

Chris Jackson - MSFT — Mon, 13 Jul 2009 21:36:09 GMT

@SEanS - I deal with software applicaiton compatibility, and don't have any information on the driver availability or support status of particular pieces of hardware. I am sorry I am unable to help. Have you contacted MSI?

re: Why Custom Actions get a Windows Vista Version Lie on Windows 7

SEanS — Mon, 13 Jul 2009 17:06:04 GMT

Another MSI k9a2 user with Multi MSI R4870 Cards all going to wast!

? Do I have to go back to XP-64? or can it be resolved?

Thanks in advance, SEanS.

re: Why Custom Actions get a Windows Vista Version Lie on Windows 7

Chris Jackson - MSFT — Wed, 10 Jun 2009 00:56:01 GMT

Robin - yes, you have to be running on Windows 7 to see the Windows 7 changes. Compatibility Administrator just provides a view into the database running on the local system. If you're running on Windows XP, you'll see what it has on it, which is different from what Windows 7 has on it.

Windows Installer doesn't appear for me in ACT 5.5.

Robin — Tue, 09 Jun 2009 11:32:41 GMT

I was trying to follow along and Installed ACT 5.5, but Windows Installer doesn't appear in the Applications tree. The list jumps from Windows Help to Windows Media Player 7.

Why might this be? Does it have to be installed on Vista or Windows 7 to appear (I'm running under XP).

re: Why Custom Actions get a Windows Vista Version Lie on Windows 7

Christopher Painter — Fri, 22 May 2009 18:45:07 GMT

While MSI has LaunchConditions, it lacks LaunchWarnings as I've previously implemented and described in my blog.

Basically I have on occasion put declarative logic in setup that warns users they are installing on an OS that wasn't available at the time of development and to take care in validating the application in a controlled environment prior to production release. We also suggest that they contact us to see if a newer release is available (for sale).

Windows 7 disguises as Vista to MSI Custom Actions

InstallSite Blog — Mon, 18 May 2009 11:47:45 GMT

In every new version of Windows, Microsoft includes numerous “shims” to improve compatibility with existing

re: Why Custom Actions get a Windows Vista Version Lie on Windows 7

Danl65 — Fri, 15 May 2009 22:39:24 GMT

Thanks for the warning that GetVersionEx will not report back as Vista under Windows 7.

I agree that this is the correct method for checking for the OS requirements within your installation package. However, I do disagree that this simplifies checking requirements because VersionNT values between Operating Systems can be the same. Thus you cannot rely ONLY on VersionNT values if you are trying to set conditions for installation or custom actions.

http://msdn.microsoft.com/en-us/library/aa370556(VS.85).aspx

The Operating System Properties indicates that unfortunately Vista and Server 2008 share the same VersionNT value. This means you have to additionally check to see if the MsiNTProductType = 1 (Server 2008) or 3 (Desktop a.k.a Vista).

Further, if your installation requirements include different service packs for various operating systems, then I can see the system checks being just as complex if not more complex as the OSVERSIONINFO structure example you gave Chris.

For example, we must ensure that for Windows XP that SP3 is installed, however, for Vista, we must ensure that it has SP1 installed. Different SP requirements for different operating systems.

re: Why Custom Actions get a Windows Vista Version Lie on Windows 7

Darwin — Fri, 15 May 2009 21:44:55 GMT

ping back from: http://csi-windows.com/blog/all/27-csi-news-general/106-why-custom-actions-get-a-windows-vista-version-lie-on-windows-7

Chris,

Thanks for the heads up on msiexec.exe shimming.

Your readers should also note that the conditions you mention should be placed ON the custom actions in the appropriate sequence table - they should not attempt to read these properties WITHIN the custom action. This is because deferred custom actions cannot see these properties because they are sandboxed. I have to guess this is also why some software vendors end up coding the version check into their DLL. A second reason is efficiency - if the condition is on the custom action, MSI never spins up the custom action because it leaves it out of the deferred script - installations run faster - better for everyone!

re: Why Custom Actions get a Windows Vista Version Lie on Windows 7

ABC — Thu, 07 May 2009 09:16:38 GMT

Hi,

Can you provide me the blogs or forums link where I can get a genuine information on Win 7 features and the comaptibility.( I know this blog also discuss the same but is there any other sites)

Anith » Why Custom Actions get a Windows Vista Version Lie on Windows 7

Anith » Why Custom Actions get a Windows Vista Version Lie on Windows 7 — Thu, 07 May 2009 01:19:35 GMT

PingBack from http://www.anith.com/?p=35480