Skip to content

Clarify .NET Framework 4.x versioning in side-by-side installation docs #49868

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
+1 −1
Draft

Clarify .NET Framework 4.x versioning in side-by-side installation docs #49868

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a20e48f
Initial plan
Copilot Nov 12, 2025
9faf5dc
Clarify .NET Framework 4.x versioning with 3.5 note
Copilot Nov 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/standard/choosing-core-framework-server.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ There are two supported [.NET implementations](glossary.md#implementation-of-net

The .NET implementation supports side-by-side installations of different versions of the .NET runtime on the same machine. That capability allows multiple services on the same server, each on its own version of .NET. It also lowers risks and saves money in application upgrades and IT operations.

Side-by-side installation isn't possible with .NET Framework. It's a Windows component, and only one version can exist on a machine at a time: each version of .NET Framework replaces the previous version. If you install a new app that targets a later version of .NET Framework, you might break existing apps that run on the machine because the previous version was replaced.
Side-by-side installation isn't possible with .NET Framework 4.x. It's a Windows component, and only one version of .NET Framework 4.x can exist on a machine at a time (.NET Framework 3.5 is separate and optional): each version of .NET Framework 4.x replaces the previous version. If you install a new app that targets a later version of .NET Framework, you might break existing apps that run on the machine because the previous version was replaced.

- **Is more secure.**

Expand Down
Loading