You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: