Talk:Get .NET Version: Difference between revisions
From NSIS Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 18: | Line 18: | ||
/T | /T | ||
:[http://msdn.microsoft.com/library/en-us/cpgenref/html/grfungetcorversion.asp GetCORVersion] is a defined API function provided by the .NET framework. There's no reason it'll not work with .NET 2.0. Reading from the registry is the undocumented method and your specific method relies on a very specific .NET version. --[[User:Kichik|kichik]] 06:43, 19 July 2006 (PDT) | :[http://msdn.microsoft.com/library/en-us/cpgenref/html/grfungetcorversion.asp GetCORVersion] is a defined API function provided by the .NET framework. There's no reason it'll not work with .NET 2.0. Reading from the registry is the undocumented method and your specific method relies on a very specific .NET version. --[[User:Kichik|kichik]] 06:43, 19 July 2006 (PDT) | ||
I came across some info/code to detect v3 (Not sure how much has changed) and SP levels of .net, might be helpful | |||
http://blogs.msdn.com/astebner/archive/2007/03/20/updated-sample-code-to-detect-the-net-framework-3-0.aspx | |||
Revision as of 01:19, 22 March 2007
I would say that this isn't the optimal way to do it. Since V2.0 isn't always backwards compatible with V1.1.
I now made an installer for an ASP .NET V1.1 solution. And I needed to be sure that V1.1 was installed. This is my solution for this problem:
Function CheckDotNet
StrCpy $0
ClearErrors
ReadRegStr $R0 HKLM 'SOFTWARE\Microsoft\ASP.NET\1.1.4322.0' 'Path'
IfErrors 0 +2
StrCpy $0 'not found'
Push $0
Exch $0
FunctionEnd
/T
- GetCORVersion is a defined API function provided by the .NET framework. There's no reason it'll not work with .NET 2.0. Reading from the registry is the undocumented method and your specific method relies on a very specific .NET version. --kichik 06:43, 19 July 2006 (PDT)
I came across some info/code to detect v3 (Not sure how much has changed) and SP levels of .net, might be helpful
