Installware has a lot of built in support for checking for the presence of the various flavors of the .NET Framework. In it’s current incarnation, 7.5, it doesn’t have anything for checking for the presence of Service Pack 1 of the .NET Framework 1.0. It turned out to be pretty easy to add that check to my installer script.
A couple of years back Heath Stewart did a blog post about how to check for the presence of a .NET Service Pack. You just look for the the value of “SP” in the registry key for the version of the .NET runtime that you want to check. For .NET 2.0, that key would be labeled:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727
If you want to check against a language, you just check for the language id. For example, English is ID 1033. The key to check for the English version of the .NET 2.0 runtime would be.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727\1033
The SP is DWORD, so you will get back an integer result. If the .NET runtime has been installed, it will have the SP value. For the RTM release, it will be 0.
With InstallAware, I use the following syntax to check for .NET 2.0 SP1 and terminate the install if SP1 (or later) has not been installed.
Read Registry Key HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v2.0.50727\SP into CHECKSYSTEM
if Variable CHECKSYSTEM not Greater Than 0
MessageBox: $TITLE$ Setup Error, This product requires that the Microsoft .Net Framework 2.0 Service Pack 1 has been installed.$NEWLINE$$NEWLINE$Setup cannot continue.
For some reason, InstallAware does not have an “Less Than” operator, you have to do “not Greater Than”. InstallAware is a leaky abstraction of the Windows Installer experience, I just shrug at those little oddities.
[Updated on 5/27/08]
I had a typo in the line that starts with “if Variable CHECKSYSTEM” where it should have been comparing against the value of 0, not 1. My bad.