Project argument should be optional to nuget why

[ericstj]

NuGet Product(s) Affected

dotnet.exe

Current Behavior

When running nuget why I always need to specify a project file. Other dotnet commands like build, 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

[jaredpar]

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 . and the command will use the project file in the current directory:

> dotnet why . System.Formats.Asn1

[ericstj]

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 nuget already has the project locator heuristic so it's simply allowing the "current working directory" to be the default value.

[baronfel]

I expect this to be fixed in RC2 by NuGet/NuGet.Client#5969

[nkolev92]

Should be a duplicate of #13553.

I'm guessing RC1 has the fix.