Edit

Deploying the .NET Framework

  • Article

This section of the .NET Framework documentation provides information for developers who want to install the .NET Framework with their applications, and administrators who want to deploy the .NET Framework across a network. It also discusses activation and restart issues associated with deployment, and how to monitor the progress of your .NET Framework installation.

Important

.NET Framework content previously digitally signed using certificates that use the SHA1 algorithm, will be retired in order to support evolving industry standards.

The following versions of .NET Framework will reach end-of-support on April 26, 2022: 4.5.2, 4.6, and 4.6.1. After this date, security fixes, updates, and technical support for these versions will no longer be provided.

If you're using .NET Framework 4.5.2, 4.6, or 4.6.1, update your deployed runtime to a more recent version, such as .NET Framework 4.6.2, before April 26, 2022 in order to continue to receive updates and technical support.

Updated SHA2 signed installers will be available for .NET Framework 3.5 SP1, and 4.6.2 through 4.8. For more information, see the SHA1 retirement plan, the .NET 4.5.2, 4.6, and 4.6.1 lifecycle update blog post, and the FAQ.

In This Section

Deployment Guide for Developers
Explains how developers can install .NET Framework on their users' computers with their applications.

Deployment Guide for Administrators
Explains how a system administrator can deploy the .NET Framework and its system dependencies across a network by using Microsoft Endpoint Configuration Manager.

Reducing System Restarts During .NET Framework 4.5 Installations
Describes the Restart Manager, which prevents reboots whenever possible, and explains how applications that install the .NET Framework can take advantage of it.

How to: Get Progress from the .NET Framework 4.5 Installer
Describes how to silently launch and track the .NET Framework setup process while showing your own view of the setup progress.

.NET Framework Initialization Errors: Managing the User Experience
Explains what happens when a .NET Framework application requires a CLR version that's invalid or not installed on the user's computer, how to resolve these errors, and how to control the error message displayed to the user.

How to: Debug CLR Activation Issues
Explains how you can view and debug CLR activation logs to resolve issues you may encounter in getting your application to run with the correct version of the CLR.

See also