On Thu, Jun 16, 2011 at 7:17 PM, Ian Thomas <[email protected]> wrote:
> Thanks for suggestions. > > It's probably as simple to check the framework folders installed on the > machine (and to test that each has some valid files and is not empty), as to > try to interpret the registry subkeys. I can't find a good explanation (eg, > the CDF subkey - what's that?). > > The stackoverflow article is a bit cross-purpose (and I had investigated > that way anyway). > > The system.environment.version() of course gives the CLR version under > which the test assembly was compiled (and will fail, perhaps ? - need to > test this - if the running machine doesn’t have CLR 4 installed). > > I guess the safe way is to check via the Windows Installer and my > installation, but I haven’t checked recently whether a custom action is > available to test for installed CLR or .NET Frameworks up to 4.0 (I did see > some post about the NSIS installer being way out of date with its > detection). > > clrver.exe is very nice - it gives the PID, assembly name, and CLR version > for each currently running assembly on the machine. But it’s not a > redistributable. > > > http://www.devfish.net/articles/clrver/article_CLRVer.htm Someone deconstructed it. -- Meski http://courteous.ly/aAOZcv "Going to Starbucks for coffee is like going to prison for sex. Sure, you'll get it, but it's going to be rough" - Adam Hills
