-
Notifications
You must be signed in to change notification settings - Fork 10.6k
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
error MSB4062: The "Grpc.Tools.ProtoToolsPlatform" task could not be loaded from the assembly #20501
Comments
Found out that this happens when there are orphaned |
I noticed this happened to me when I had my ide open and I upgrading my version of the tools. |
Can this be closed then? |
What's the reason to close it? |
According to #20501 (comment) it doesn't look like it's a grpc issue. |
Then where does "error MSB4062" belong to? Who is supposed to fix the "error"? |
dotnet/cli#9458 This is a consequence of these optimizations. I don't think there is much you can do other than kill any dotnet processes that are hanging around. The canonical way to do this is |
For someone reach in here, I leave this comment(origin : https://youtrack.jetbrains.com/issue/RIDER-25412) Why this problem is made.
So, MsBuild One Persistent host try to load How to resolve it.All Grpc related references should be have same version (particular |
grpc/grpc-dotnet#561
What version of gRPC and what language are you using?
GRPC 2.23.0, ASP.Net Core 3.0 C#.
What operating system (Linux, Windows,...) and version?
Ubuntu 19.04
What runtime / compiler are you using (e.g. python version or version of gcc)
What did you do?
dotnet run --project src/myproject
If possible, provide a recipe for reproducing the error. Try being specific and include code snippets if helpful.
What did you expect to see?
What did you see instead?
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
See TROUBLESHOOTING.md for how to diagnose problems better.
Anything else we should know about your project / environment?
The text was updated successfully, but these errors were encountered: