Discrepancy between .Net SDK version shown on the website and Display version shown on the Registry

Question

Discrepancy between .Net SDK version shown on the website and Display version shown on the Registry

Dhanraj D 6

Hi There,

When we install Microsoft .Net SDK 6.0.100, the display version available on the registry is "6.1.21.52711".But, the actual version that is mentioned on the website is "6.0.100".

Even the products that are included in the SDK like ".NET Desktop Runtime 6.0.0" have a different display version on the registry than what is shown on the website.

For example:- The ".NET Desktop Runtime 6.0.0", installed part of "Microsoft .Net SDK 6.0.100" installation has the display version of "48.3.31217" on the registry but the standalone version has the display version of "6.0.0.30623".

We would like to know why this contradiction between the standalone version of the products and the ones which are part of SDK.

We also want to know why there is a difference between the version mentioned on the website and the one available on the registry for SDK itself.

Please refer to the screenshots.

Answer 1

Bruce (SqlWork.com) 31,816

the registery setting are only used by the windows installer and uninstaller for dotnet

on windows there are typically three runtimes:

Microsoft.AspNetCore.App
Microsoft.NETCore.App
Microsoft.WindowsDesktop.App

each is its own folder, and contains a folder for each installed runtime.

to know what is installed its:

dotnet --list-runtimes
dotnet --list-sdks

Dhanraj D 6 Reputation points

2022-01-31T11:29:09.617+00:00

Thanks@Bruce (SqlWork.com) .

our scenario is , If we want to install "Microsoft Windows Desktop Runtime" of version "6.0.0" (The one which we get from the website), we create a script that will check for any machines which are installed with "Microsoft.NETCore.App" of version lesser than "6.0.0". Basically, the script will check for the "Display Version" of "Microsoft.NETCore.App" on the registry to see if it is lesser than "6.0.0". If yes, it will install. if not, it will not.

The script works because the version mentioned on the website and on the registry matches.

But if I try to create the same logic to install "SDK" of version "6.0.100" (The one which we get from the website) on the computers which have "Display Version" lesser than "6.0.100" on the registry, it is not working as it worked for the above, since the display version on the registry and version mentioned on the website are different. (Display version on the registry for this product is 6.1.21.52711).

Due to this inconsistency,we are not able to create a baseline for SDK that will check for the display version lesser than the version mentioned on the website.

If we still want to create a baseline to check for the lower version, then we need to install SDK on a machine manually to get to know the display version from registry manually instead of just using the version given on the website and put it in the script.
Dhanraj D 6 Reputation points

2022-01-31T11:32:05.19+00:00

Thanks@Bruce (SqlWork.com) .

our scenario is , If we want to install "Microsoft Windows Desktop Runtime" of version "6.0.0" (The one which we get from the website), we create a script that will check for any machines which are installed with "Microsoft.NETCore.App" of version lesser than "6.0.0". Basically, the script will check for the "Display Version" of "Microsoft.NETCore.App" on the registry to see if it is lesser than "6.0.0". If yes, it will install. if not, it will not.

The script works because the version mentioned on the website and on the registry matches.

But if I try to create the same logic to install "SDK" of version "6.0.100" (The one which we get from the website) on the computers which have "Display Version" lesser than "6.0.100" on the registry, it is not working as it worked for the above, since the display version on the registry and version mentioned on the website are different. (Display version on the registry for this product is 6.1.21.52711).

Due to this inconsistency,we are not able to create a baseline for SDK that will check for the display version lesser than the version mentioned on the website.

If we still want to create a baseline to check for the lower version, then we need to install SDK on a machine manually to get to know the display version from registry manually instead of just using the version given on the website and put it in the script.
Dhanraj D 6 Reputation points

2022-01-31T11:34:30.14+00:00

Thanks@Bruce (SqlWork.com) .

our scenario is , If we want to install "Microsoft Windows Desktop Runtime" of version "6.0.0" (The one which we get from the website), we create a script that will check for any machines which are installed with "Microsoft.NETCore.App" of version lesser than "6.0.0". Basically, the script will check for the "Display Version" of "Microsoft.NETCore.App" on the registry to see if it is lesser than "6.0.0". If yes, it will install. if not, it will not.

The script works because the version mentioned on the website and on the registry matches.

But if I try to create the same logic to install "SDK" of version "6.0.100" (The one which we get from the website) on the computers which have "Display Version" lesser than "6.0.100" on the registry, it is not working as it worked for the above, since the display version on the registry and version mentioned on the website are different. (Display version on the registry for this product is 6.1.21.52711).

Due to this inconsistency,we are not able to create a baseline for SDK that will check for the display version lesser than the version mentioned on the website.

If we still want to create a baseline to check for the lower version, then we need to install SDK on a machine manually to get to know the display version from registry manually instead of just using the version given on the website and put it in the script.

Answer 2

Jiachen Li-MSFT 11,881 Microsoft Vendor

Hi @Dhanraj D ,
Overview of how .NET is versioned
The .NET Runtime and the .NET SDK add new features at different frequencies. In general, the SDK is updated more frequently than the Runtime.
Options for dotnet by itself
Please use
dotnet --list-sdks to print out a list of the installed .NET SDKs.
dotnet--list-runtimes to prints out a list of the installed .NET runtimes. An x86 version of the SDK lists only x86 runtimes, and an x64 version of the SDK lists only x64 runtimes.

Best Regards.
Jiachen Li

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Dhanraj D 6 Reputation points

2022-01-31T11:28:55.267+00:00

Thanks@Jiachen Li-MSFT

our scenario is , If we want to install "Microsoft Windows Desktop Runtime" of version "6.0.0" (The one which we get from the website), we create a script that will check for any machines which are installed with "Microsoft.NETCore.App" of version lesser than "6.0.0". Basically, the script will check for the "Display Version" of "Microsoft.NETCore.App" on the registry to see if it is lesser than "6.0.0". If yes, it will install. if not, it will not.

The script works because the version mentioned on the website and on the registry matches.

But if I try to create the same logic to install "SDK" of version "6.0.100" (The one which we get from the website) on the computers which have "Display Version" lesser than "6.0.100" on the registry, it is not working as it worked for the above, since the display version on the registry and version mentioned on the website are different. (Display version on the registry for this product is 6.1.21.52711).

Due to this inconsistency,we are not able to create a baseline for SDK that will check for the display version lesser than the version mentioned on the website.

If we still want to create a baseline to check for the lower version, then we need to install SDK on a machine manually to get to know the display version from registry manually instead of just using the version given on the website and put it in the script.
Bruce (SqlWork.com) 31,816 Reputation points

2022-01-31T16:12:04.33+00:00

you can do what the dotnet tool does and query the sdk install folder.

dir "C:\Program Files\dotnet\sdk"
Jiachen Li-MSFT 11,881 Reputation points Microsoft Vendor

2022-02-01T09:27:28.04+00:00

Hi @Dhanraj D ,
Why do you need the runtime installation to be precise to the displayed version?
You can only know its display version after downloading and installing the SDK, so it is impossible to compare the locally installed display version with the downloaded version.

Answer 3

Thanks @Jiachen Li-MSFT ,

Yeah, the reason is if I want to install "Microsoft Windows Desktop Runtime" of version "6.0.0", I can simply take the version from the website itself and put it in the script to find out the machines which have lower version. In this case, I would simply check for the machines which have "Microsoft Windows Desktop Runtime" with a version lesser than "6.0.0".

But, in the case of SDK, I can not make this logic just with the version available on the website. I need to know the exact version that is getting installed for which I need to install the product manually and I need to use that version to find out the machines which have a lower version of SDK than the targetted version of SDK. It makes my life a bit difficult.

For SDK 6.0.100, I can not simply use the version given on the website. Because the actual version that is getting installed is different.

Thanks again for your time.

Regards,

D.Dhanraj

If SDK followed semantic versioning, it would have been a lot better for me.

Discrepancy between .Net SDK version shown on the website and Display version shown on the Registry

3 answers

Activity