Determine which .NET Framework versions are installed - .NET Framework (2024)

  • Article

Users can install and run multiple versions of .NET Framework on their computers. When you develop or deploy your app, you might need to know which .NET Framework versions are installed on the user's computer. The registry contains a list of the versions of .NET Framework installed on the computer.

Note

This article is specific to .NET Framework. To determine which .NET Core and .NET 5+ SDKs and runtimes are installed, see How to check that .NET is already installed.

.NET Framework consists of two main components, which are versioned separately:

  • A set of assemblies, which are collections of types and resources that provide the functionality for your apps. .NET Framework and the assemblies share the same version number. For example, .NET Framework versions include 4.5, 4.6.1, and 4.7.2.

  • The common language runtime (CLR), which manages and executes your app's code. A single CLR version typically supports multiple .NET Framework versions. For example, CLR version 4.0.30319.xxxxx where xxxxx is less than 42000, supports .NET Framework versions 4 through 4.5.2. CLR version greater than or equal to 4.0.30319.42000 supports .NET Framework versions starting with .NET Framework 4.6.

Community-maintained tools are available to help detect which .NET Framework versions are installed:

For information about detecting the installed updates for each version of .NET Framework, see How to: Determine which .NET Framework updates are installed.

Determine which .NET implementation and version an app is running on

You can use the RuntimeInformation.FrameworkDescription property to query for which .NET implementation and version your app is running on. If the app is running on .NET Framework, the output will be similar to:

.NET Framework 4.8.4250.0

By comparison, if the app is running on .NET Core or .NET 5+, the output will be similar to:

.NET Core 3.1.9.NET 5.0.0

Detect .NET Framework 4.5 and later versions

The version of .NET Framework (4.5 and later) installed on a machine is listed in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full. If the Full subkey is missing, then .NET Framework 4.5 or above isn't installed.

The Release REG_DWORD value in the registry represents the version of .NET Framework installed.

.NET Framework versionValue of Release
.NET Framework 4.5All Windows operating systems: 378389
.NET Framework 4.5.1On Windows 8.1 and Windows Server 2012 R2: 378675
On all other Windows operating systems: 378758
.NET Framework 4.5.2All Windows operating systems: 379893
.NET Framework 4.6On Windows 10: 393295
On all other Windows operating systems: 393297
.NET Framework 4.6.1On Windows 10 November Update systems: 394254
On all other Windows operating systems (including Windows 10): 394271
.NET Framework 4.6.2On Windows 10 Anniversary Update and Windows Server 2016: 394802
On all other Windows operating systems (including other Windows 10 operating systems): 394806
.NET Framework 4.7On Windows 10 Creators Update: 460798
On all other Windows operating systems (including other Windows 10 operating systems): 460805
.NET Framework 4.7.1On Windows 10 Fall Creators Update and Windows Server, version 1709: 461308
On all other Windows operating systems (including other Windows 10 operating systems): 461310
.NET Framework 4.7.2On Windows 10 April 2018 Update and Windows Server, version 1803: 461808
On all Windows operating systems other than Windows 10 April 2018 Update and Windows Server, version 1803: 461814
.NET Framework 4.8On Windows 10 May 2019 Update and Windows 10 November 2019 Update: 528040
On Windows 10 May 2020 Update, October 2020 Update, May 2021 Update, November 2021 Update, and 2022 Update: 528372
On Windows 11 and Windows Server 2022: 528449
On all other Windows operating systems (including other Windows 10 operating systems): 528049
.NET Framework 4.8.1On Windows 11 2022 Update and Windows 11 2023 Update: 533320
All other Windows operating systems: 533325

Minimum version

To determine whether a minimum version of .NET Framework is present, check for a Release REG_DWORD value that's greater than or equal to the corresponding value listed in the following table. For example, if your application runs under .NET Framework 4.8 or a later version, test for a Release REG_DWORD value that's greater than or equal to 528040.

.NET Framework versionMinimum value
.NET Framework 4.5378389
.NET Framework 4.5.1378675
.NET Framework 4.5.2379893
.NET Framework 4.6393295
.NET Framework 4.6.1394254
.NET Framework 4.6.2394802
.NET Framework 4.7460798
.NET Framework 4.7.1461308
.NET Framework 4.7.2461808
.NET Framework 4.8528040
.NET Framework 4.8.1533320

Use Registry Editor

  1. From the Start menu, choose Run, enter regedit, and then select OK.

    (You must have administrative credentials to run regedit.)

  2. In the Registry Editor, open the following subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full. If the Full subkey isn't present, then you don't have .NET Framework 4.5 or later installed.

  3. Check for a REG_DWORD entry named Release. If it exists, then you have .NET Framework 4.5 or later installed. Its value corresponds to a particular version of .NET Framework. In the following figure, for example, the value of the Release entry is 528040, which is the release key for .NET Framework 4.8.

    Determine which .NET Framework versions are installed - .NET Framework (1)

Use PowerShell to check for a minimum version

Use PowerShell commands to check the value of the Release entry of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full subkey.

The following examples check the value of the Release entry to determine whether .NET Framework 4.6.2 or later is installed. This code returns True if it's installed and False otherwise.

(Get-ItemPropertyValue -LiteralPath 'HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' -Name Release) -ge 394802

Query the registry using code

  1. Use the RegistryKey.OpenBaseKey and RegistryKey.OpenSubKey methods to access the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full subkey in the Windows registry.

    Important

    If the app you're running is 32-bit and running in 64-bit Windows, the registry paths will be different than previously listed. The 64-bit registry is available in the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ subkey. For example, the registry subkey for .NET Framework 4.5 is HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v4\Full.

  2. Check the Release REG_DWORD value to determine the installed version. To be forward-compatible, check for a value greater than or equal to the value listed in the .NET Framework version table.

The following example checks the value of the Release entry in the registry to find the versions of .NET Framework 4.5-4.8.1 that are installed.

Tip

Add the directive using Microsoft.Win32 or Imports Microsoft.Win32 at the top of your code file if you haven't already done so.

const string subkey = @"SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\";using (var ndpKey = RegistryKey.OpenBaseKey(RegistryHive.LocalMachine, RegistryView.Registry32).OpenSubKey(subkey)){ if (ndpKey != null && ndpKey.GetValue("Release") != null) { Console.WriteLine($".NET Framework Version: {CheckFor45PlusVersion((int)ndpKey.GetValue("Release"))}"); } else { Console.WriteLine(".NET Framework Version 4.5 or later is not detected."); }}// Checking the version using >= enables forward compatibility.string CheckFor45PlusVersion(int releaseKey){ if (releaseKey >= 533320) return "4.8.1 or later"; if (releaseKey >= 528040) return "4.8"; if (releaseKey >= 461808) return "4.7.2"; if (releaseKey >= 461308) return "4.7.1"; if (releaseKey >= 460798) return "4.7"; if (releaseKey >= 394802) return "4.6.2"; if (releaseKey >= 394254) return "4.6.1"; if (releaseKey >= 393295) return "4.6"; if (releaseKey >= 379893) return "4.5.2"; if (releaseKey >= 378675) return "4.5.1"; if (releaseKey >= 378389) return "4.5"; // This code should never execute. A non-null release key should mean // that 4.5 or later is installed. return "No 4.5 or later version detected";}
Private Sub Get45PlusFromRegistry() Const subkey As String = "SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\" Using ndpKey As RegistryKey = RegistryKey.OpenBaseKey(RegistryHive.LocalMachine, RegistryView.Registry32).OpenSubKey(subkey) If ndpKey IsNot Nothing AndAlso ndpKey.GetValue("Release") IsNot Nothing Then Console.WriteLine($".NET Framework Version: {CheckFor45PlusVersion(ndpKey.GetValue("Release"))}") Else Console.WriteLine(".NET Framework Version 4.5 or later is not detected.") End If End UsingEnd Sub' Checking the version using >= enables forward compatibility.Private Function CheckFor45PlusVersion(releaseKey As Integer) As String If releaseKey >= 533320 Then Return "4.8.1 or later" ElseIf releaseKey >= 528040 Then Return "4.8" ElseIf releaseKey >= 461808 Then Return "4.7.2" ElseIf releaseKey >= 461308 Then Return "4.7.1" ElseIf releaseKey >= 460798 Then Return "4.7" ElseIf releaseKey >= 394802 Then Return "4.6.2" ElseIf releaseKey >= 394254 Then Return "4.6.1" ElseIf releaseKey >= 393295 Then Return "4.6" ElseIf releaseKey >= 379893 Then Return "4.5.2" ElseIf releaseKey >= 378675 Then Return "4.5.1" ElseIf releaseKey >= 378389 Then Return "4.5" End If ' This code should never execute. A non-null release key should mean ' that 4.5 or later is installed. Return "No 4.5 or later version detected"End Function

The example displays output like the following:

.NET Framework Version: 4.6.1

Query the registry using code PowerShell

The following example uses PowerShell to check the value of the Release entry in the registry to find the versions of .NET Framework 4.5-4.8.1 that are installed:

$release = Get-ItemPropertyValue -LiteralPath 'HKLM:SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' -Name Releaseswitch ($release) { { $_ -ge 533320 } { $version = '4.8.1 or later'; break } { $_ -ge 528040 } { $version = '4.8'; break } { $_ -ge 461808 } { $version = '4.7.2'; break } { $_ -ge 461308 } { $version = '4.7.1'; break } { $_ -ge 460798 } { $version = '4.7'; break } { $_ -ge 394802 } { $version = '4.6.2'; break } { $_ -ge 394254 } { $version = '4.6.1'; break } { $_ -ge 393295 } { $version = '4.6'; break } { $_ -ge 379893 } { $version = '4.5.2'; break } { $_ -ge 378675 } { $version = '4.5.1'; break } { $_ -ge 378389 } { $version = '4.5'; break } default { $version = $null; break }}if ($version) { Write-Host -Object ".NET Framework Version: $version"} else { Write-Host -Object '.NET Framework Version 4.5 or later is not detected.'}

This example follows the recommended practice for version checking:

  • It checks whether the value of the Release entry is greater than or equal to the value of the known release keys.
  • It checks in order from most recent version to earliest version.

Detect .NET Framework 1.0 through 4.0

Each version of .NET Framework from 1.1 to 4.0 is listed as a subkey at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP. The following table lists the path to each .NET Framework version. For most versions, there's an Install REG_DWORD value of 1 to indicate this version is installed. In these subkeys, there's also a Version REG_SZ value that contains a version string.

Note

The NET Framework Setup subkey in the registry path does not begin with a period.

Framework VersionRegistry SubkeyValue
1.0HKLM\Software\Microsoft\.NETFramework\Policy\v1.0\3705Install REG_SZ equals 1
1.1HKLM\Software\Microsoft\NET Framework Setup\NDP\v1.1.4322Install REG_DWORD equals 1
2.0HKLM\Software\Microsoft\NET Framework Setup\NDP\v2.0.50727Install REG_DWORD equals 1
3.0HKLM\Software\Microsoft\NET Framework Setup\NDP\v3.0\SetupInstallSuccess REG_DWORD equals 1
3.5HKLM\Software\Microsoft\NET Framework Setup\NDP\v3.5Install REG_DWORD equals 1
4.0 Client ProfileHKLM\Software\Microsoft\NET Framework Setup\NDP\v4\ClientInstall REG_DWORD equals 1
4.0 Full ProfileHKLM\Software\Microsoft\NET Framework Setup\NDP\v4\FullInstall REG_DWORD equals 1

Important

If the app you're running is 32-bit and running in 64-bit Windows, the registry paths will be different than previously listed. The 64-bit registry is available in the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ subkey. For example, the registry subkey for .NET Framework 3.5 is HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v3.5.

Notice that the registry path to the .NET Framework 1.0 subkey is different from the others.

Use Registry Editor (older framework versions)

  1. From the Start menu, choose Run, enter regedit, and then select OK.

    You must have administrative credentials to run regedit.

  2. Open the subkey that matches the version you want to check. Use the table in the Detect .NET Framework 1.0 through 4.0 section.

    The following figure shows the subkey and its Version value for .NET Framework 3.5.

    Determine which .NET Framework versions are installed - .NET Framework (2)

Query the registry using code (older framework versions)

Use the Microsoft.Win32.RegistryKey class to access the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP subkey in the Windows registry.

Important

If the app you're running is 32-bit and running in 64-bit Windows, the registry paths will be different than previously listed. The 64-bit registry is available in the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ subkey. For example, the registry subkey for .NET Framework 3.5 is HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v3.5.

The following example finds the versions of .NET Framework 1-4 that are installed:

// Open the registry key for the .NET Framework entry.using (RegistryKey ndpKey = RegistryKey.OpenBaseKey(RegistryHive.LocalMachine, RegistryView.Registry32). OpenSubKey(@"SOFTWARE\Microsoft\NET Framework Setup\NDP\")){ foreach (var versionKeyName in ndpKey.GetSubKeyNames()) { // Skip .NET Framework 4.5 version information. if (versionKeyName == "v4") { continue; } if (versionKeyName.StartsWith("v")) { RegistryKey versionKey = ndpKey.OpenSubKey(versionKeyName); // Get the .NET Framework version value. var name = (string)versionKey.GetValue("Version", ""); // Get the service pack (SP) number. var sp = versionKey.GetValue("SP", "").ToString(); // Get the installation flag. var install = versionKey.GetValue("Install", "").ToString(); if (string.IsNullOrEmpty(install)) { // No install info; it must be in a child subkey. Console.WriteLine($"{versionKeyName} {name}"); } else if (install == "1") { // Install = 1 means the version is installed. if (!string.IsNullOrEmpty(sp)) { Console.WriteLine($"{versionKeyName} {name} SP{sp}"); } else { Console.WriteLine($"{versionKeyName} {name}"); } } if (!string.IsNullOrEmpty(name)) { continue; } // else print out info from subkeys... // Iterate through the subkeys of the version subkey. foreach (var subKeyName in versionKey.GetSubKeyNames()) { RegistryKey subKey = versionKey.OpenSubKey(subKeyName); name = (string)subKey.GetValue("Version", ""); if (!string.IsNullOrEmpty(name)) sp = subKey.GetValue("SP", "").ToString(); install = subKey.GetValue("Install", "").ToString(); if (string.IsNullOrEmpty(install)) { // No install info; it must be later. Console.WriteLine($" {versionKeyName} {name}"); } else if (install == "1") { if (!string.IsNullOrEmpty(sp)) { Console.WriteLine($" {subKeyName} {name} SP{sp}"); } else { Console.WriteLine($" {subKeyName} {name}"); } } } } }}
' Opens the registry key for the .NET Framework entry.Using ndpKey As RegistryKey = RegistryKey.OpenBaseKey(RegistryHive.LocalMachine, RegistryView.Registry32). OpenSubKey("SOFTWARE\Microsoft\NET Framework Setup\NDP\") For Each versionKeyName In ndpKey.GetSubKeyNames() ' Skip .NET Framework 4.5 and later. If versionKeyName = "v4" Then Continue For If versionKeyName.StartsWith("v") Then Dim versionKey As RegistryKey = ndpKey.OpenSubKey(versionKeyName) ' Get the .NET Framework version value. Dim name = DirectCast(versionKey.GetValue("Version", ""), String) ' Get the service pack (SP) number. Dim sp = versionKey.GetValue("SP", "").ToString() Dim install = versionKey.GetValue("Install", "").ToString() If String.IsNullOrEmpty(install) Then ' No install info; it must be in a child subkey. Console.WriteLine($"{versionKeyName} {name}") ElseIf install = "1" Then If Not String.IsNullOrEmpty(sp) Then Console.WriteLine($"{versionKeyName} {name} SP{sp}") Else Console.WriteLine($"{versionKeyName} {name}") End If End If If Not String.IsNullOrEmpty(name) Then Continue For End If For Each subKeyName In versionKey.GetSubKeyNames() Dim subKey As RegistryKey = versionKey.OpenSubKey(subKeyName) name = DirectCast(subKey.GetValue("Version", ""), String) If Not String.IsNullOrEmpty(name) Then sp = subKey.GetValue("SP", "").ToString() End If install = subKey.GetValue("Install", "").ToString() If String.IsNullOrEmpty(install) Then ' No install info; it must be later. Console.WriteLine($" {versionKeyName} {name}") ElseIf install = "1" Then If Not String.IsNullOrEmpty(sp) Then Console.WriteLine($" {subKeyName} {name} SP{sp}") Else Console.WriteLine($" {subKeyName} {name}") End If End If Next End If NextEnd Using

The example displays output similar to the following:

v2.0.50727 2.0.50727.4927 SP2v3.0 3.0.30729.4926 SP2v3.5 3.5.30729.4926 SP1v4.0 Client 4.0.0.0

Query the registry using PowerShell (older framework versions)

The following example uses PowerShell to check the value of the Release entry in the registry to find the versions of .NET Framework 1-4 that are installed:

Get-ChildItem -Path 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP' |Where-Object { ($_.PSChildName -ne "v4") -and ($_.PSChildName -like 'v*') } |ForEach-Object { $name = $_.Version $sp = $_.SP $install = $_.Install if (-not $install) { Write-Host -Object "$($_.PSChildName) $($name)" } elseif ($install -eq '1') { if (-not $sp) { Write-Host -Object "$($_.PSChildName) $($name)" } else { Write-Host -Object "$($_.PSChildName) $($name) SP$($sp)" }} if (-not $name) { $parentName = $_.PSChildName Get-ChildItem -LiteralPath $_.PSPath | Where-Object { if ($_.Property -contains 'Version') { $name = Get-ItemPropertyValue -Path $_.PSPath -Name Version } if ($name -and ($_.Property -contains 'SP')) { $sp = Get-ItemPropertyValue -Path $_.PSPath -Name SP } if ($_.Property -contains 'Install') { $install = Get-ItemPropertyValue -Path $_.PSPath -Name Install } if (-not $install) { Write-Host -Object " $($parentName) $($name)" } elseif ($install -eq '1') { if (-not $sp) { Write-Host -Object " $($_.PSChildName) $($name)" } else { Write-Host -Object " $($_.PSChildName) $($name) SP$($sp)" } } } }}

Find CLR versions

The .NET Framework CLR installed with .NET Framework is versioned separately. There are two ways to detect the version of the .NET Framework CLR:

  • The Clrver.exe tool

    Use the CLR Version tool (Clrver.exe) to determine which versions of the CLR are installed on a computer. Open Visual Studio Developer Command Prompt or Visual Studio Developer PowerShell and enter clrver.

    Sample output:

    Versions installed on the machine:v2.0.50727v4.0.30319
  • The Environment class

    Important

    For .NET Framework 4.5 and later versions, don't use the Environment.Version property to detect the version of the CLR. Instead, query the registry as described in Detect .NET Framework 4.5 and later versions.

    1. Query the Environment.Version property to retrieve a Version object.

      The returned System.Version object identifies the version of the runtime that's currently executing the code. It doesn't return assembly versions or other versions of the runtime that may have been installed on the computer.

      For .NET Framework versions 4, 4.5, 4.5.1, and 4.5.2, the string representation of the returned Version object has the form 4.0.30319.xxxxx, where xxxxx is less than 42000. For .NET Framework 4.6 and later versions, it has the form 4.0.30319.42000.

    2. After you have the Version object, query it as follows:

      • For the major release identifier (for example, 4 for version 4.0), use the Version.Major property.

      • For the minor release identifier (for example, 0 for version 4.0), use the Version.Minor property.

      • For the entire version string (for example, 4.0.30319.18010), use the Version.ToString method. This method returns a single value that reflects the version of the runtime that's executing the code. It doesn't return assembly versions or other runtime versions that may be installed on the computer.

    The following example uses the Environment.Version property to retrieve CLR version information:

    Console.WriteLine($"Version: {Environment.Version}");
    Console.WriteLine($"Version: {Environment.Version}")

    The example displays output similar to the following:

    Version: 4.0.30319.18010

See also

  • How to: Determine which .NET Framework updates are installed
  • Troubleshoot: Determine which versions and service packs of .NET Framework are installed
  • Install .NET Framework for developers
  • .NET Framework versions and dependencies
Determine which .NET Framework versions are installed - .NET Framework (2024)

FAQs

Determine which .NET Framework versions are installed - .NET Framework? ›

You can install and run multiple versions of .NET Framework on a computer. If you want to check the versions on your own computer, the easiest way is through Control Panel > Programs > Programs and Features, or in Settings under Apps > Installed apps. You can also use these community-maintained tools.

How do you determine what versions of .NET Framework are installed? ›

Search for 'regedit' on the Start menu and click on the 'Registry Editor' in the search results. From here you can follow the path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP and expand the main version key (like: v4 or v4. 0) and select Full. This will show you the version of the .

How do I know if .NET 3.5 is installed? ›

Procedure Steps
  1. Click [Start] in the bottom-left corner of the display.
  2. Highlight Administrative Tools and select Server Manager.
  3. In the Server Manager interface, click [Features] to show all the installed features in the right pane. Verify that . NET Framework 3.5. 1 is listed.
Jan 11, 2022

How do I know which .NET SDK is installed? ›

Determine what is installed

The . NET CLI has options you can use to list the versions of the SDK and runtime that are installed on your computer. Use dotnet --list-sdks to see the list of installed SDKs and dotnet --list-runtimes for the list of runtimes.

How do I specify .NET Framework version? ›

Change the target framework
  1. In Solution Explorer, open the right-click context menu for the project that you want to change, and then choose Properties.
  2. In the left column of the Properties window, choose the Application tab. ...
  3. In the Target Framework list, choose the version that you want.
Dec 12, 2023

How to check which .NET Framework is installed using CMD? ›

Type the following command to check the version of . NET installed and press Enter: Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP' -Recurse | Get-ItemProperty -Name version -EA 0 | Where { $_. PSChildName -Match '^(?! S)\p{L}'} | Select PSChildName, version.

How do you check if .NET Framework has been installed? ›

Check for .

NET by navigating to Microsoft.NET\Framework under your Windows folders. The complete path is usually 'C:\Windows\Microsoft.NET\Framework. Each of the installed . NET versions will have its own folder.

Where is .NET Framework 3.5 installed? ›

You can get the . NET Framework 3.5 payload files from Windows Update or the installation media in the \sources\sxs folder. For more information, see Installing the . NET Framework 3.5.

How to check version of .NET Framework in registry? ›

NET Framework versions by viewing the registry:
  1. On the Start menu, click Run.
  2. In the Open field, enter regedit.exe.
  3. Click OK.
  4. In the Registry Editor, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP. The installed versions are listed under the NDP subkey.

How do I know if .NET Framework 3.5 is installed PowerShell? ›

From PowerShell:
  1. Launch PowerShell as an administrator.
  2. Run the command import-module servermanager. ASP.NET 3.5: Run the command get-windowsfeature web-asp-net. ...
  3. If the version of ASP.NET you need does not show as "Installed," install using one of the following commands.

What version of .NET core is installed? ›

NET Core is installed on Windows is: Press Windows + R. Type cmd. On the command prompt, type dotnet --version.

Where is .NET SDK installed in Windows? ›

The SDK installs to a versioned folder such as C:\Program Files\dotnet\sdk\7.0. 400\ on Windows or /usr/bin/share/dotnet/sdk/7.0. 400 on Linux.

What is my .NET SDK? ›

The software development kit (SDK) includes everything you need to build and run . NET applications, using command-line tools and any editor (like Visual Studio). Runtime (Windows) The runtime includes everything you need to run .

What is the difference between .NET and .NET Framework? ›

NET framework helps you build web apps, desktop apps, and web services. It works only on the Windows operating system. On the other hand, . NET core is for creating cross-platform cloud apps that run on Windows, Mac, and Linux.

Can you have multiple versions of .NET Framework installed? ›

Multiple versions of . NET Framework can be installed on a single Windows computer without conflict. If you have multiple versions of . NET Framework on your computer, chances are it's because an application requires a specific version to function.

What is current .NET version? ›

Latest release: 8.0.4. Last updated on 2024-04-09. EOL: 2026-11-10.

What two versions of the Microsoft .NET framework must be installed? ›

NET Framework to run many apps on Windows. The best versions to install are the latest one and the . NET Framework 3.5 SP1. Those two versions should run nearly all apps.

What is the current .NET framework version? ›

NET Framework 4.8. 1 was released in August 2022.

What are the NET Framework versions? ›

Releases
VersionStart Date
.NET Framework 4.02010-04-12T00:00:00.000-08:00
.NET Framework 3.5 Service Pack 12007-11-19T00:00:00.000-08:00
.NET Framework 3.02006-11-21T00:00:00.000-08:00
.NET Framework 2.02006-02-17T00:00:00.000-08:00
11 more rows

Can I have multiple versions of NET Framework installed? ›

Multiple versions of . NET Framework can be installed on a single Windows computer without conflict. If you have multiple versions of . NET Framework on your computer, chances are it's because an application requires a specific version to function.

Top Articles
Latest Posts
Article information

Author: Moshe Kshlerin

Last Updated:

Views: 5965

Rating: 4.7 / 5 (77 voted)

Reviews: 92% of readers found this page helpful

Author information

Name: Moshe Kshlerin

Birthday: 1994-01-25

Address: Suite 609 315 Lupita Unions, Ronnieburgh, MI 62697

Phone: +2424755286529

Job: District Education Designer

Hobby: Yoga, Gunsmithing, Singing, 3D printing, Nordic skating, Soapmaking, Juggling

Introduction: My name is Moshe Kshlerin, I am a gleaming, attractive, outstanding, pleasant, delightful, outstanding, famous person who loves writing and wants to share my knowledge and understanding with you.