-
Notifications
You must be signed in to change notification settings - Fork 173
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 'Microsoft.CodeAnalysis, Version=4.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. #1546
Comments
If you add the following to a .cs file, what version does the compiler report in the error message?
|
|
As a general comment, it may be useful for |
My apologies, I didn't realize |
Might be related to #1519 and/or #1433 You might also want to try the workaround proposed in #1433 (comment) |
Issue not fixed with #1433 (comment). |
I'm also getting the ReflectionTypeLoadException - Could not load file or assembly 'Microsoft.CodeAnalysis.CSharp' when running
|
@OoLunar Can you use the Report a Problem feature of Visual Studio to submit a new issue here? In the Additional Attachments section, the item I'm looking for is a binlog, which you can collect by executing a command line build and passing the |
Unfortunately I cannot do this as I'm on Linux and use Visual Studio Code. Are there any alternatives I can do? Edit: I failed to read. Will attach the binlog in a moment |
@OoLunar There is a fix coming in the next .NET 6 SDK release. In the meantime you can install dotnet format as a global tool to work around this issue (See #1519 (comment)). Closing this issue as duplicate of #1519 |
I am getting this issue but for 4.5.0.0 in .NET 7.0.202.
|
I got the same issue but (temporarily) resolved it by removing |
@jerohero that fixed it for me, thank you. |
This also fixed the problem for me, though I'm not sure why. I don't understand why this would be a problem. |
Just encountered the same issue with the .NET 7 SDK while running |
Same situation here. Does not work in .NET 7.0: `dotnet --info .NET SDK: Runtime Environment: Host: .NET SDKs installed: .NET runtimes installed: Other architectures found: Environment variables: global.json file: Learn more: Download .NET: |
Same situation here. Does not work in .NET 7.0: `dotnet --info Version: 7.0.5 .NET SDKs installed: |
@JoeRobich we have similar problem (just version is 4.6.0.0 instead of 4.1.0.0) on github actions with 7.0.302 version. Should this issue be reopened? |
The fix for the current SDKs will be in the next servicing release of the SDKs. Sorry the infrastructure that updated the Roslyn version fell behind. |
Same for me with .NET 7 SDK |
We have the same issue in github actions.
|
+1 for the error @konstantinkos-tr is receiving. Same version(s) |
Same problem as @konstantinkos-tr |
Same here, with the same version. |
Same problem as @konstantinkos-tr with same version |
running into the same issue as @konstantinkos-tr with same version |
For those running into this problem. The following worked for me. Use the
Invoke with For other versions of dotnet (6, 8, etc). Change the version and source:
This was sufficient for me, you may need to look for a specific version of the tool if this doesn't work for you. |
I switched to Rust and everything worked perfect since then. On the topic: just wait or use LTS versions of .NET. |
This seems to be broken again in v6.0.423. |
We start facing the same issue today after installing this NuGet Microsoft.Extensions.Telemetry.Abstractions" Version="8.0.0". We are using same version of the SDK v6.0.423. |
We encounter the same issue after installing |
Version Used:
6.0.2
Steps to Reproduce:
Clone OoLunar/Tomoe@f37434a on branch rewrite/DSP_3.0 (Apologies for the non-minimal repro, unsure on how to reproduce)
Expected Behavior:
Successfully formatted
<x>
files.Actual Behavior:
Notes:
Apologies for the non-minimal repro, as I'm not sure what's causing this in the first place. Additional apologies if this belongs in roslyn-analyzers instead of this repo. I didn't see anything related to
CAxxxx
, so I'm assuming this belongs here.The text was updated successfully, but these errors were encountered: