Add comparison for nvm and dotnetup #361
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In this PR, I add onto the proposal from @baronfel to include a direct comparison, showing some of what I researched about `nvm` and how we thought about it when designing `dotnetup`. Some of this is pretty specific into technical detail and I want to avoid this document becoming huge and unreviewable. @baronfel's document also is a larger picture sell rather than a dive into the specifics, however I thought it would be helpful to have this information here. We can close these changes if we disagree and move it elsewhere. I tried to briefly touch on the topics without duplicating what will go into `dotnet/sdk/documentation/dotnetup` - the `hive` defaults and `path` handling alone will be their own documents. It can take several pages to explain.
…etup-to-baronfel-spec
More of this is generated text, but I've modified it and done some fact checking.
jkotas
reviewed
Jan 22, 2026
Co-authored-by: Jan Kotas <jkotas@microsoft.com>
marcpopMSFT
reviewed
Jan 23, 2026
marcpopMSFT
reviewed
Jan 23, 2026
marcpopMSFT
approved these changes
Jan 23, 2026
nagilson
commented
Jan 23, 2026
nagilson
commented
Jan 23, 2026
nagilson
deleted the
nagilson-add-comparison-nvm-dotnetup-to-baronfel-spec
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this PR, I add onto the proposal from @baronfel (#353) to include a direct comparison, showing some of what I researched about
nvmand how we thought about it when designingdotnetup.Some of this is pretty specific into technical detail and I want to avoid this document becoming huge and unreviewable. @baronfel's document also is a larger picture sell rather than a dive into the specifics, however I thought it would be helpful to have this information here. We can close these changes if we disagree and move it elsewhere.
I tried to briefly touch on the topics without duplicating what will go into
dotnet/sdk/documentation/dotnetup- thehivedefaults andpathhandling alone will be their own documents. It can take several pages to explain.