-
Notifications
You must be signed in to change notification settings - Fork 172
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
Could not load file or assembly 'System.Configuration.ConfigurationManager, Version=6.0.0.0' #1658
Comments
I get a similar error message when using dotnet7.0.0-preview5 |
This is a known issue with the .NET 7 Preview 5 build. It is resolved in later builds. See known issues list and workaround at https://github.com/dotnet/core/blob/main/release-notes/7.0/known-issues.md#unhandled-exception-in-dotnet-format-app-in-net-70-preview-5 |
Thank you 👍
…On Sat, Jul 9, 2022, 19:18 Joey Robichaud ***@***.***> wrote:
Closed #1658 <#1658> as completed.
—
Reply to this email directly, view it on GitHub
<#1658 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACSMN35UNQFOGSNSDUP67ULVTGX47ANCNFSM53AWP2MA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
@JoeRobich what about .net 6? the original post has fixed 6.0.301 in their global json, as have I, and I get this error. I don't have .net 7 installed at all
|
The global tool works fine, the sdk bundled version is busted. I guess I missed that it was sdk bundled now and that
|
As far as I can tell there are significant differences between what |
The difference in reported code style diagnostics between 6.x and 7.x builds is caused by different versions of Roslyn Analyzers which are automatically added to your project by the version of the SDK that is being used by dotnet-format. 6.x builds can be installed with the following command and are intended to be used with a .NET 6 SDK.
7.x builds can be installed with the following command and are intended to be used with a .NET 7 SDK.
|
@BradBarnich Sorry, there will be a fix in the 6.0.400 version of the SDK. |
This is probably what was confusing to me, the fact that |
I'm trying to use
dotnet format --no-restore
from command line locally but it keeps failing with:I have
global.json
with:and
dotnet --info
:Solution has many projects but is for a WPF desktop app. Not ASP.NET Core.
If I run without
--no-restore
I get the following error:The text was updated successfully, but these errors were encountered: