search

shanselman / SmallestDotNet

SmallestDotNet - SmallestDotNet.com is a single page site that does one thing. It tells you the smallest, easiest download you'd need to get the .NET Framework on your system.
MIT License
130 stars 64 forks source link

How about full, update and revision numbers. 4.6.1.69 etc. #56

Open codeSasquatch opened 8 years ago

codeSasquatch commented 8 years ago

How about full, update and revision numbers. 4.6.1.69 etc.

marcosnz commented 8 years ago

@codeSasquatch do you know a way of reliably obtaining this?

codeSasquatch commented 8 years ago

The only way I know of is to look inside windows at specific binaries e.g.C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll image

marcosnz commented 8 years ago

Yeah, me to, but (in the past, at least) this hasn't been terribly reliable:

Below is a list with the approximate build range for each version:

.NET Version Clr.dll Build 4.0.30319.Build
.NET 4.0 4.0.30319.0 to 4.0.30319.17000
.NET 4.5 4.0.30319.17001 to 4.0.3019.18400
.NET 4.5.1 4.0.30319.18401 to 4.0.30319.34000
.NET 4.5.2 From 4.0.30319.34000

I think it may confuse some people to say "Your version is 4.5.2, your CLR version is 4.0.30319.34000". What do you think?

codeSasquatch commented 8 years ago

@marcosnz I think that Microsoft should provide a registry key with the latest "Product Version" with the revision and build numbers, so that engineers who do installation and also the few who even care about the version of .Net can find it easily. In a seperate key provide the "CLR" version It seems like an oversight to me that could easily be fixed. While its easy enough to go digging through the file structure to find a binary to look at it is not so clear for the beginning engineer or someone who has never been tasked to find the version to find it. Thoughts?

binki commented 7 years ago

@codeSasquatch How do you get 4.6.1.69 from 4.6.96.0? Also, on my system, clr.dll fileversion is 4.6.2006.0. What version of .net would that mean I have?