sidebar hamburger menu

.NET

Endless Lifecycle Support (ELS) for .NET from TuxCare provides security fixes for .NET that has reached its end of life. This allows you to continue running .NET applications without vulnerability concerns, even after official support has ended.

Supported Versions

Supported .NET versions: 6.0.x, 8.0.x, 10.0.x

Windows Version.NET 6.NET 8.NET 10Architectures
Nano Server 2019, 2022x64
Nano Server 2025x64
Windows 11 (24H2, 23H2, 22H2 E/Edu)x64
Windows 10 (22H2)x64
Windows Server 2025x64
Windows Server 2022, 2019, 2016, 2012-R2, 2012x64, x86
Windows Server Core 2022, 2019, 2016, 2012-R2, 2012x64, x86

SDK

The .NET SDK (Software Development Kit) is the recommended option if you plan to develop, build, test, or publish .NET applications. It includes:

  • The .NET Runtime, which is required to run .NET apps.
  • The ASP.NET Core Runtime, so you can develop and host ASP.NET Core web applications out of the box.
  • The .NET CLI and build tools for compiling and managing your .NET projects.

With the SDK, you won't need to install separate runtimes for ASP.NET Core or the Desktop environment - everything is bundled together to streamline development and deployment.

ASP.NET Core Runtime

The ASP.NET Core Runtime contains the components needed to run ASP.NET Core web applications on .NET. It includes libraries and features for building dynamic web pages, RESTful APIs, and real-time communication with SignalR.

Note: If you install the full .NET SDK, you already get the ASP.NET Core Runtime.

.NET Desktop Runtime

The .NET Desktop Runtime allows you to run Windows desktop applications built with Windows Forms or WPF (Windows Presentation Foundation). It focuses on providing a smooth experience for traditional graphical apps on Windows platforms.

.NET Runtime

The .NET Runtime is the base runtime required to run console or server-based .NET applications. It's more lightweight than the SDK, since it does not include compilers, build tools, or additional libraries for web or desktop development.

TuxCare applies security patches to .NET for the above OS versions, ensuring continued stability and security even beyond the official end-of-life date.

Installation via the .NET Installer

Prerequisites & System Requirements

  • Check the supported versions section above for operating system compatibility.
  • Refer to the official .NET documentation for system requirements.
  • Administrator rights for installation
  • Check if you have .NET already installed on your system:
    • Open Command Prompt (type cmd in the search bar) or PowerShell (type powershell in the search bar) and run the following command:

      dotnet --version
      
    • If .NET is already installed, the command will return the version number. If it’s not installed, you’ll see an error message.

    • Install the latest version of .NET before uninstalling the old one to ensure a smooth transition without breaking the dependencies.

Installation Steps

  • Obtain the required license to get access to the service.
  • Contact sales@tuxcare.com to receive the necessary steps for generating your unique access link (tokenized URL). Anonymous access is restricted.
  • Follow the provided instructions to create your secure download link.
  • Use this link to access and download .NET files.
  • Choose the appropriate runtime:
    • .NET SDK - Includes everything needed for development, including the runtime and build tools.
    • .NET Runtime - Runs .NET applications but does not include development tools.
    • .NET Runtime Desktop - Required for running desktop applications built with .NET.
    • ASP.NET Core Runtime - Needed for running web applications and services built with ASP.NET Core. For more information, refer to the official .NET documentation.
  • Download the corresponding installer based on your system type (x64 or x86). Downloading the latest version is recommended.
    • .NET SDK - Installed via an .exe installer.
    • .NET Runtime, .NET Runtime Desktop, and ASP.NET Core Runtime – Installed via .msi files.

In certain versions of some browsers (for example, Edge), you might see a warning after downloading. In this case, manually allow the download.

Note: The following steps use the .NET SDK installation as an example. If you are installing a runtime instead, follow a similar process using the corresponding .msi file.

  • Once the installer is downloaded, double-click the file to run it. You’ll see a dialog window. Follow the on-screen instructions: image

    • Accept the license agreement.
    • Click Install and wait for the process to complete. It should only take a few minutes.
    • Once the installation is finished, click Close.
  • Verify the installation. Open Command Prompt (type cmd in the search bar) or PowerShell (type powershell in the search bar) to confirm that .NET was installed successfully:

    dotnet --version
    

    Example output:

    6.0.429
    

Start Using .NET

Now that .NET is installed, you are ready to start using it. You can create and run .NET applications using the command-line tools or Visual Studio/Visual Studio Code.

If you’re new to .NET, we recommend visiting the official .NET documentation for a deeper understanding of the platform.

Create and Run a Test Project

For a quick start, follow this example to create and run a simple console application:

  • Open Command Prompt (type cmd in the search bar) or PowerShell (type powershell in the search bar).

  • Run the following command to create a new console application:

    dotnet new console -o MyTestApp
    

    Example output:

    Welcome to .NET 6.0!
    ---------------------
    SDK Version: 6.0.429
    
    ----------------------------------------------------------------------------
    The template "Console App" was created successfully.
    
    Processing post-creation actions...
    Running 'dotnet restore' on C:\Users\user\MyTestApp\MyTestApp.csproj...
      Determining projects to restore...
      Restored C:\Users\user\MyTestApp\MyTestApp.csproj (in 115 ms).
    Restore succeeded.
    
  • Navigate to the newly created folder:

    cd MyTestApp
    
  • Build and run the application:

    dotnet run
    

    When executed, you should see the following output:

    Hello, World!
    

Useful Commands

The following commands are useful for managing and troubleshooting .NET installation.

  • where.exe dotnet locates the dotnet executable on the system. The output shows the exact path where the dotnet command is installed. By default, the .NET installation is placed in the Program Files\dotnet folder, unless a different destination is chosen during setup.

    where.exe dotnet
    

    Example output:

    C:\Program Files\dotnet\dotnet.exe
    
  • dotnet --info displays information about the installed .NET SDKs, runtimes and your OS. It also verifies the .NET is correctly set up.

    dotnet --info
    

    Example output:

    .NET SDK (reflecting any global.json):
     Version:   6.0.429
     Commit:    ef6f5ce48c
    
    Runtime Environment:
     OS Name:     Windows
     OS Version:  10.0.22631
     OS Platform: Windows
     RID:         win10-x64
     Base Path:   C:\Program Files\dotnet\sdk\6.0.429\
    
    global.json file:
      Not found
    
    Host:
      Version:      6.0.36
      Architecture: x64
      Commit:       N/A
    
    .NET SDKs installed:
      6.0.429 [C:\Program Files\dotnet\sdk]
    
    .NET runtimes installed:
      Microsoft.AspNetCore.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
      Microsoft.NETCore.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
      Microsoft.WindowsDesktop.App 6.0.36 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
    
    Download .NET:
      https://aka.ms/dotnet-download
    
    Learn about .NET Runtimes and SDKs:
      https://aka.ms/dotnet/runtimes-sdk-info
    
  • dotnet --list-sdks lists all the .NET SDKs installed on your system. Uninstall the old .NET version after you install a new one.

    dotnet --list-sdks
    

    Example output:

    6.0.429 [C:\Program Files\dotnet\sdk]
    

NuGet Repository (Optional)

Developers working on .NET projects may need a NuGet repository to manage and share packages across projects. TuxCare provides a shared NuGet repository, which you can add with a simple command:

dotnet nuget add source \
  https://nexus.repo.tuxcare.com/repository/els_dotnet/index.json \
  --name TuxCare \
  --username $USERNAME \
  --password $PASSWORD

Replace $USERNAME and $PASSWORD with the credentials provided by sales@tuxcare.com.

Uninstall ELS for .NET

Uninstall via Windows Settings

  • Open SettingsAppsInstalled Apps (or Apps & Features on older versions).
  • Search for .NET SDK or .NET Runtime depending on what you’ve installed.
  • Click on each entry and select Uninstall.

    During the uninstall, a "Files in use" window can appear. Select the "Do not close applications. A reboot will be required" option and click OK to proceed.

  • A dialog window will appear. Click Uninstall. It should take a few minutes. When the process is finished, close the window.

Uninstall via Control Panel

  • Open Control PanelProgramsPrograms and Features.
  • Search for .NET SDK or .NET Runtime depending on what you’ve installed.
  • Right-click on each entry and select Uninstall.

    During the uninstall, a "Files in use" window can appear. Select the "Do not close applications. A reboot will be required" option and click OK to proceed.

  • A dialog window will appear. Click Uninstall. It should take a few minutes. When the process is finished, close the window.

Remove Remaining Files

After uninstalling .NET some files may remain in the following locations:

  • C:\Program Files\dotnet\
  • C:\Users\<user>\.dotnet\

Delete the folders manually to fully remove .NET.

Frequent Issues

How do I update .NET if a new version is released?

Currently, to update .NET, you need to manually download the latest installer and follow the installation steps described above. After installing the new version, it’s recommended to remove the previous one. In the future, an automatic update mechanism for the components will be provided.

What should I do if there are conflicts during installation?

If you encounter conflicts, try uninstalling the previous version before installing the new one. In most cases, .NET versions can coexist without issues, but removing the older version may help resolve compatibility problems.

×
Need help?
I'm a multilingual AI chatbot, trained to answer all your questions!