-
Notifications
You must be signed in to change notification settings - Fork 5k
"dotnet nuget" results in "Internal CLR error" #92146
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
Comments
I did a reboot of my PC and now
Please note that I already did a reboot after yesterday's update of VS and VS Preview. |
Dupe of #92007, fixed in RC2 |
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsDescribe the bugYesterday, VS updated to .NET 8 RC1. Since then calling I've installed both Visual Studio 2022 and Visual Studio 2022 Preview. To Reproduce
Exceptions (if any)Running the above results in the error message:
Full output:
Further technical details
|
@jeffschwMSFT I don't think a "Internal CLR error" is related to infrastructure libraries. |
ha, I was going by the area of the referenced issue. |
Closing as dupe per @BrennanConroy comment above |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
Yesterday, VS updated to .NET 8 RC1. Since then calling
dotnet nuget
is broken on my Windows 11 development computer.I've installed both Visual Studio 2022 and Visual Studio 2022 Preview.
To Reproduce
dotnet nuget
and press Enter.Exceptions (if any)
Running the above results in the error message:
Full output:
Further technical details
dotnet --version
returns "8.0.100-rc.1.23455.8"dotnet --info
returns the followingThe text was updated successfully, but these errors were encountered: