-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add workload restore command #18910
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
Merged
Merged
Add workload restore command #18910
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
// Copyright (c) .NET Foundation and contributors. All rights reserved. | ||
// Licensed under the MIT license. See LICENSE file in the project root for full license information. | ||
|
||
using System; | ||
using Microsoft.DotNet.Tools; | ||
using System.CommandLine; | ||
using System.IO; | ||
using Microsoft.Build.Framework; | ||
using Microsoft.DotNet.Tools.Common; | ||
|
||
namespace Microsoft.DotNet.Cli | ||
{ | ||
internal static class CommonOptionsExtension | ||
{ | ||
public static LoggerVerbosity ToLoggerVerbosity(this VerbosityOptions verbosityOptions) | ||
{ | ||
LoggerVerbosity verbosity = Build.Framework.LoggerVerbosity.Normal; | ||
switch (verbosityOptions) | ||
{ | ||
case VerbosityOptions.d: | ||
case VerbosityOptions.detailed: | ||
verbosity = Build.Framework.LoggerVerbosity.Detailed; | ||
break; | ||
case VerbosityOptions.diag: | ||
case VerbosityOptions.diagnostic: | ||
verbosity = Build.Framework.LoggerVerbosity.Diagnostic; | ||
break; | ||
case VerbosityOptions.m: | ||
case VerbosityOptions.minimal: | ||
verbosity = Build.Framework.LoggerVerbosity.Minimal; | ||
break; | ||
case VerbosityOptions.n: | ||
case VerbosityOptions.normal: | ||
verbosity = Build.Framework.LoggerVerbosity.Normal; | ||
break; | ||
case VerbosityOptions.q: | ||
case VerbosityOptions.quiet: | ||
verbosity = Build.Framework.LoggerVerbosity.Quiet; | ||
break; | ||
} | ||
|
||
|
||
return verbosity; | ||
} | ||
} | ||
} |
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we should discover all projects here. We should do the same thing as MSBuild, which is more or less to expect that there is a single project or solution file in the directory, and error out if not. The actual logic is in
ProcessProjectSwitch
: https://github.com/dotnet/msbuild/blob/1d845f30213e9ba4f36d4d5a366c0cc8285eed6e/src/MSBuild/XMake.cs#L2763Ideally we wouldn't have to duplicate the logic. It looks like
RunCommand
has a simple form of it (FindSingleProjectInDirectory
) which only looks for project files, not solution files.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought about the same thing, but why make it difficult. I started with refactoring RunCommand. But when there are 2 projects in the folder what the user should do? It is valid, and workload restore can handle it (unlike runcommand), why fail and ask the user to input one by one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All other MSBuild and dotnet commands require you to specify the project if there is more than one in the folder. It seems weird to make
dotnet workload restore
the one exception.