-
Notifications
You must be signed in to change notification settings - Fork 1.3k
dotnetup: classify PATH dotnet by managed hive; fix env config doc #55349
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.
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
Changes from 3 commits
0fbc96c
83503e1
3134f0e
4d8f61a
d4dad88
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -446,9 +446,10 @@ internal static List<string> FormatMigrationDisplayItems(List<MigrationWorkflow. | |
| return []; | ||
| } | ||
|
|
||
| // Find the system install path for display purposes | ||
| // Find the system install path for display purposes. Whether the dotnet winning on PATH is | ||
| // a dotnetup hive is irrelevant here; we want its location only when it is a system install. | ||
| var currentInstall = dotnetEnvironment.GetCurrentPathConfiguration(); | ||
| string systemPath = currentInstall?.InstallType == InstallType.System | ||
| string systemPath = currentInstall is not null && InstallPathClassifier.IsAdminInstallPath(currentInstall.Path) | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think this should be using a method to check
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. After the init, you can use
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nit: It'd be nice to have a regression test - e.g. mock the registry reading behavior to point to a non expected system install besides dotnetup and see if it uses the correct dotnet executable or not (one could be an exe that fails, the other returns 0)
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not following. This code just controls what is printed when its asking whether you want to migrate existing installs. Can you clarify?
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I meant for this comment to be in the
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. OK, in that case I think we probably have the coverage you were looking for (copilot thought we did at least). |
||
| ? currentInstall.Path | ||
| : DotnetEnvironmentManager.GetSystemDotnetPaths().FirstOrDefault() ?? "the system .NET location"; | ||
|
|
||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -283,7 +283,7 @@ Or open a new terminal.</value> | |
| <value>Open a new terminal for the change to take effect.</value> | ||
| </data> | ||
| <data name="EnvOpenNewTerminalForOtherSurfaces" xml:space="preserve"> | ||
| <value>Open a new terminal for the change to take effect in other terminals and applications.</value> | ||
| <value>Other open terminals and applications will pick up this change after they're restarted.</value> | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think it's better to start with an action verb. Why was this changed? I'm on board with trying to make it clear this applies to apps & terminals earlier in the message.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
This seems incorrect to me. To me it's telling you that opening a new terminal will cause existing terminals and applications to get the update.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Great point, I hadn't considered that. I lean slightly towards starting with a verb but good to move forward with this! |
||
| </data> | ||
| <data name="EnvShellRequiredForProfile" xml:space="preserve"> | ||
| <value>Could not detect the current shell, which is required to update the dotnetup profile entry. Re-run with --shell <{0}> to specify it explicitly.</value> | ||
|
|
||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Uh oh!
There was an error while loading. Please reload this page.