Resolve create tool manifest issue #1430 using --force #4151
+2
−2
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
Contributor
Author
|
@dotnet-policy-service agree |
Contributor
Author
|
The change to the minimunDoNetVersion was done to be able to install and run a local build of Polyglot Notebooks in VS Code to verify the fix. It's not strictly becessary for the fix to work. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #1430 Polyglot notebook stuck on installing NET interactive.
#4130
The issue is that, at least for some users, during extension activation the command "dotnet new tool-manifest" failed because this file already exists and/or could not be overwritten:
c:\Users****\AppData\Roaming\Code\User\globalStorage\ms-dotnettools.dotnet-interactive-vscode\dotnet-tools.json
By adding the '--force' argument this is resolved.
@jonsequitur