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

Valid version installs for dotnet tooling. #27

Open
kekyo opened this issue Oct 26, 2022 · 0 comments
Open

Valid version installs for dotnet tooling. #27

kekyo opened this issue Oct 26, 2022 · 0 comments
Assignees

Comments

@kekyo
Copy link
Owner

kekyo commented Oct 26, 2022

Currently, when installing dotnet tooling, the version automatically selected is 3.0.1.

This was deployed in the past with an incorrect version number, which is marked as deprecated and unlisted on nuget.org, but when you follow the guide to install, 3.0.1 is selected. This can be avoided by manually specifying the version as follows:

dotnet tool uninstall -g MarkTheRipper
dotnet tool install -g MarkTheRipper --version 0.4.0

This could be a bug in dotnet tooling. However, I am also aware that this is a mistake in my deployment...

Even if dotnet tooling is fixed this problem in the future, 3.0.1 will remain in the MarkTheRipper package forever, and I can no longer correct it forever (nuget.org could not correct any version mistakes after deployed.) Therefore, I am considering changing the package name in dotnet tooling. it has been an issue for some time as to what package name to use in dotnet tooling, but another project of mine.

Until the problem is resolved, please manually download 0.4.0 package and install directly, or download net471 binary. The problem will be fixed soon.

@kekyo kekyo self-assigned this Oct 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant