Unable to specify project file to analyze

On both release version v4.0.130203 and development version v5.0.142902, it seems that attempting to use dotnet format in a folder with multiple csproj and sln files ignores the specified project file.

For example, using v5.0.142902 while Powershell is in the D:\username\Desktop directory, using this command:

dotnet format --check "D:\project-folder\project-to-analyze.csproj" -v diagnostic --fix-style warn --report "D:\project-folder\report.json"

Gives the intended result with proper analysis. However, using this same command in the D:\project-folder\ directory, I get a result of:

Specify which project file to use because this 'D:\project-folder' contains more than one project file.

The same happens using v4.0.130203 with the following command (--fix-style warn is removed as that is not present prior to v5):

dotnet format --check "D:\project-folder\project-to-analyze.csproj" -v diagnostic --report "D:\project-folder\report.json"

I’m not sure if this is a bug or if I am using the commands wrongly.

[Pycorax]

Thanks for the fix! I can verify that it works as expected.

[JoeRobich]

@Pycorax I was able to reproduce this behavior on Windows. Thanks for sharing the error message again. This message is coming from the dotnet CLI and not dotnet-format.

This command works for me locally. Notice that I use dotnet-format instead of dotnet format.

D:\project-folder\> dotnet-format --check "D:\project-folder\project-to-analyze.csproj" -v diagnostic --fix-style warn --report "D:\project-folder\report.json"

@wli3 Should dotnet tools be invokable through the dotnet CLI from within folders containing multiple project files?

Steps to reproduce:

dotnet tool install -g dotnet-format
dotnet new console -o project-folder
cd project-folder
cp project-folder.csproj project-to-analyze.csproj
dotnet format project-to-analyze.csproj