Skip to content
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

Unable to install NUnit.ConsoleRunner.NetCore 3.18.0 due to not found settings file 'DotnetToolSettings.xml' #1446

Closed
MichalMucek opened this issue Jul 17, 2024 · 5 comments · Fixed by #1451
Assignees
Labels
Bug Critical Critical Priority, i.e. requires an immediate hot fix.
Milestone

Comments

@MichalMucek
Copy link

MichalMucek commented Jul 17, 2024

When trying to install NUnit.ConsoleRunner.NetCore (.NET Tool) 3.18.0, there's an error:

Tool 'nunit.consolerunner.netcore' failed to update due to the following: The settings file in the tool's NuGet package is invalid: Settings file 'DotnetToolSettings.xml' was not found in the package. Tool 'nunit.consolerunner.netcore' failed to install. Contact the tool author for assistance.

Also, instructions for installing the .NET tool (the .NET CLI tabs) are missing from the nuget.org page for version 3.18.0, while they are present for 3.17.0 and earlier.

@CharliePoole
Copy link
Member

CharliePoole commented Jul 17, 2024

@MichalMucek Could you provide the exact command you are entering to install the tool?

I'm able to see that the file is included in the package

@MichalMucek
Copy link
Author

@CharliePoole
dotnet tool install --global NUnit.ConsoleRunner.NetCore --version 3.18.0
dotnet tool install --local NUnit.ConsoleRunner.NetCore --version 3.18.0

@CharliePoole CharliePoole self-assigned this Jul 17, 2024
@CharliePoole CharliePoole added Bug Critical Critical Priority, i.e. requires an immediate hot fix. labels Jul 17, 2024
@CharliePoole
Copy link
Member

Confirming this bug. It looks as if the structure of the package may be incorrect, i.e. the file is there but not in the right place.

@CharliePoole
Copy link
Member

In addition to fixing this, we should add a test. We do test the runner but we do not execute it via the dotnet command, so that needs to be added.

Workaround: Use NuGet to install it to a known location and then run the executable directly.

@CharliePoole
Copy link
Member

This issue has been resolved in version 3.18.1

The release is available on:
GitHub.
NuGet packages are also available NuGet.org and
Chocolatey Packages may be found at Chocolatey.org

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Critical Critical Priority, i.e. requires an immediate hot fix.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants