dotnet / dotnet/docs

Documentation on updating your SDK ahead of a VS update

Open
#37,817 2 comments 0 reactions 1 assignee Claimed by @gewarren View on GitHub
Dominant language
No language data
Stars
4.8k
Forks
6.1k
Avg merge
19h 10m
Merged PRs (30d)
268

Description

**Help us make content visible**

SDK, VS, runtime, global.json

**Describe the new article**

During internal discussions, some questions came up around SDK/runtime releases and customers who either cannot and haven't updated their Visual Studio versions. In particular, we weren't sure if we could release a VS release on the same day as a .net security release and wanted a playbook we could point to if we had to do this release.

Is there a good location for this note/playbook?

The recommendation for the customer would be to install the newer stand-alone SDK from the same feature band as their current VS. Then the customer would have to ensure their global.json doesn't pin them to an exact version.

Alternatively, customers could use RuntimeFrameworkVersion to override the implicit version but this requires updating the project (and would need to be removed later) and doesn't support multi-targeting so it's not a recommended solution.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.