-
Notifications
You must be signed in to change notification settings - Fork 676
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
Fail: OmniSharp.MSBuild.ProjectManager, Attemped to update project that is not loaded #2507
Comments
@bkmalkoc Thanks for filing--can you share your solution or tell me more about your project/folder topology? Eg, what project to project references do you have, are all of those projects in the same solution, etc? |
@rchande |
Also @bkmalkoc what kinds of projects are these? .NET Core, .NET Framework? |
@rchande it is .NET Core |
Hello. I have this same problem just after OmniSharp updated itself. There has been an update from VS Code and the dotnet-sdk recently too, not sure if it's related. I'm using Fedora 28. |
I am using the latest sdk release.
Output of
|
@djkiwe Please share your omnisharp log. Thanks! |
Now that I double checked, my log shows different errors from @bkmalkoc 's. Although both finish with the same statement: |
@djkiwe Yes, please. |
@bkmalkoc Is it possible for you to share just the csprojs? I can't reproduce this with the base output of "dotnet new"... |
HotelContentFetcher.csproj
FetcherTests.csproj
|
Affecting me and others as well... See OmniSharp/omnisharp-roslyn#1094 |
This same error is also affecting me, I can no longer use the Unity Debugger |
I have completely removed everything from my computer (vscode, sdk) then reinstalled and now working. weird and foolish solution but at least I get th work going. @rchande |
@bkmalkoc Glad you got it working. Could you share your |
I've set my ms-vscode.csharp package.json for the 1.32.3 version release of omnisharp and updated my extension folder with this version. It worked for me. |
@rchande I have no clue what has changed but after clean reinstallation here is my dotnet; dotnet --info
|
@bkmalkoc glad you got it working. For others still encountering issues: |
I downloaded and installed the beta version, but I still have an error. I'm not sure if I'm getting the same error as the other guys, but this is what I see
And the output of my
|
I had this problem recently, I thought I had everything installed even mono, but I didn't have mono-complete installed just a few packages it seems, it solved my problem. People could try that and see if it solves thier problems. |
@rchande I have getting the same error using both 1.16.2 and 1.17.0... The project was generated using The VS Code output log as follows:
The
|
@FranklinWhale @farzadmf - I had the same problem as you guys and the problem is that Omnisharp is choosing the MS Build instance for Visual Studio Build Tools 2017 as stated below:
As the exception says, the manifest file does exist, but if you look in it, it lists a relative path that is supposed to go to the SDK resolver. The path does not have the file listed nor some of the folders. If you check the second MS Build instance listed, you will notice that the path does resolve to the correct file. I couldn't figure out how to force Omnisharp to choose a different MS Build instance, so the fix I came up with was just to uninstall Visual Studio. |
@ErikSharp I found some workarounds that resolved the issue for me, more specifically:
Unfortunately, the issue doesn't seem to be considered serious here as none of the maintainers has commented on this. |
@FranklinWhale Can you try the workaround as suggested by @farzadmf and see if that helps |
@akshita31 After the Build Tools is uninstalled, the error no longer occurs. |
@akshita31, @rchande: Is there any update on this issue? I am unable to have VS Build Tools and VS code on the same machine now... |
昨天安装了window build tools 之后,也出现了同样的问题 |
Hi, Any update on this as I am experiencing the same issue. |
@FranklinWhale When you installed the Build Tools, did you include the .NET Core Build Tools workload? |
@rchande Probably no, because the Build Tools is for C++ only. I build .NET Core applications via |
@FranklinWhale How are you installing the build tools? |
|
+1 on this issue, and as the above has noted, uninstalling build-tools does not seem like a practical/tenable workaround. |
I also have this issue - in my case the latest Node installation (10.13.0) had an option to install ms build tools |
The solution here might be to install the .NET Core Build tools as stated in a similar issue here: OmniSharp/omnisharp-roslyn#1311 (comment) |
@owensource @mjharper84 @FranklinWhale Can you try doing the above and checking if it works ? |
@akshita31 That works and I now know via OmniSharp/omnisharp-roslyn#1311 that:
|
Same issue on MacBook Pro 15 2018, Latest Mojave. Project was created in virtual windows. |
In my case, I updated 2.1 to 2.2 and then occcured same issue. |
One more thing to say, things work well in Visual Studio(in virtual Win 10), but not in Visual Studio Code(Mojave). |
Fixed by reinstalling Omnisharp extension in VS Code. |
The suggestion to install .net core build tools by @akshita31 fixed it for me, reinstalling Omnisharp did not fix it https://user-images.githubusercontent.com/3347530/46700117-8e488e80-cbe1-11e8-851c-13cbd8587815.png |
For everyone who hits this issue, please install the ".NET Core Build Tools" workload in Visual Studio. |
@martyrzsd Please file a separate issue with the relevant environment information. It appears that we know the solution to this issue and there is more work being tracked here: OmniSharp/omnisharp-roslyn#1186, that will make the experience better. I will close this issue now. If there are any remaining concerns please let us know |
Solution for me was to update csproj to target 2.1 instead of 2.0 because I had 2.1 sdk installed. |
I realize that the origin poster was on Windows, but this problem occured for me on Linux and I couldn't find a solution in any of the top threads. I'm not sure why, but the official mono-documentations says:
At best I feel like this is highly misleading as it does not install compile-dependencies. If you're on a linux distribution, follow the instructions at this link to install the mono-devel package. At the time of writing this can be done using: |
I encountered this issue, was resolved by uninstalling the VS 2017 Build Tools I had installed. |
@Moortiii Downloading and installing Mono from your link worked for me on MacOS Mojave 10.14.5. Thanks! |
I am on Windows 10 using VS Code, WSL and Spacemacs. I had this issue as well, and found out, if i build my projects under WSL, with By deleting all my obj folders (I deleted bin folders also just to be safe) in by project, and restarted VS Code, it helped. I got intellisense back, both in VS Code and Spacemacs. If using WSL, build your projects with Hope this helps someone. |
VS code versions > 2019 doesn't yet support important libraries that are needed to run runner such as .NET, etc. Ex: dotnet/vscode-csharp#2507
resolving when installing older and stable sdk version |
I was stuck with this issue and pretty much the exact same error log and nothing I saw on forums solved it for about a week, but in the end all I had to do was install the latest mono and change the "Omnisharp: Use Global Mono" to always, and then it was fine. I had tried about 50 things to get omnisharp working, so its possible that something else i did contributed to it eventually working, but I figured I would put this here in case anyone has the same problem that I was having. |
Environment data
dotnet --info
output:.NET Core SDK (reflecting any global.json):
Version: 2.1.300
Commit: adab45bf0c
Runtime Environment:
OS Name: Windows
OS Version: 10.0.17134
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\2.1.300\
Host (useful for support):
Version: 2.1.0
Commit: caa7b7e2ba
.NET Core SDKs installed:
1.0.0 [C:\Program Files\dotnet\sdk]
2.1.300 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 1.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 1.1.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download
VS Code version: 1.27.1
C# Extension version:
Steps to reproduce
OmniSharp is updated itself
Expected behavior
Project to be working
Actual behavior
OmniSharp Log:
The text was updated successfully, but these errors were encountered: