-
Notifications
You must be signed in to change notification settings - Fork 252
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
Project argument should be optional to nuget why
#13782
Comments
Definitely agree that the project should be optional here for consistency with other commands. One work around I've found is that you can use > dotnet why . System.Formats.Asn1 |
Thanks for sharing that. I hadn't realized that would work - I guess it's because you can specify a directory. I still think this should be the default for consistency with other commands. The fact that a directory works means |
I expect this to be fixed in RC2 by NuGet/NuGet.Client#5969 |
NuGet Product(s) Affected
dotnet.exe
Current Behavior
When running
nuget why
I always need to specify a project file. Otherdotnet
commands likebuild
,restore
,clean
,publish
do not require this.Desired Behavior
Use the same heuristic for locating a project or solution file when running
nuget why
and one is not specified.Additional Context
No response
The text was updated successfully, but these errors were encountered: