-
Notifications
You must be signed in to change notification settings - Fork 675
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
OmniSharp fails to load project when adding reference to other project #2286
Comments
Hi! Could you provide your full OmniSharp Log after loading this project? You can find this by selecting View->Output from the VS Code menu and then selecting "OmniSharp Log" from the dropdown at the top-right corner of the Output pane. |
|
Could you try updating your VS 2017 Build Tools to the latest (15.7.1)? |
Will do and report back asap. |
FWIW, the log's look identical. It doesn't appear that the VS 2017 build tools were actually updated. They have the same version numbers: |
My bad, it's updating a second time now, this time for 15.7.1, sorry! |
Okay, updated, version numbers match what you said, tried again, same procedure, same result. dotnet new console
PS: Updated original post with extra info |
Thanks for the update and sorry it didn't work. 😞 Out of curiosity, do you actually have the .NET Core workload installed into the VS 2017 build tools? |
No, the .NET Core workload in the build tools only installs 1.0.0 from what I remember (maybe they changed it by now) I installed the latest SDK manually. Install path and everything should be the same so I don't think it'd make a difference either way |
I believe the .NET Core workload installs newer than 1.0.0 now. I would expect it to be the same tools installed with VS 2017 15.7. @AndyGerlicher / @rainersigwald, is that the case? So, the problem seems to be that OmniSharp is trying to use the instance of MSBuild from the VS 2017 Build Tools, but the .NET Core workload is not installed. |
Should I try installing the .NET Core workload from the VS Build Tools installer then? |
I believe the 15.7 build tools installer .NET Core workload installs the .NET Core SDK version 2.1.200. |
(and also some other things, so I would expect it to be worth trying) |
Alright, will try |
Excellent! I'll look into adding an option for OmniSharp to allow you to choose which MSBuild instance will be picked. OmniSharp's standalone MSBuild bits would have almost certainly worked in this case. |
I've created OmniSharp/omnisharp-roslyn#1186 to track adding some options. |
I'm having the same problem, even in the current version still happening :( dotnet --info
OmniSharp log
VsCode
|
@yuridiniz : Could you file a new issue? The underlying problem reported here was discovered. I suspect you're experience a different problem that may look similar. |
Environment data
VS Code version: 1.23.1
C# Extension version: 1.15.0
Steps to reproduce
Expected behavior
OmniSharp should load the project as normal and enable intellisense for classes inside mylib
Actual behavior
dotnet build / dotnet run work as expected, however:
OmniSharp fails to load the project console project, doesn't load mylib.csproj at all, and intellisense is not working. OmniSharp log:
Known workarounds
None, removing the reference to mylib.csproj from test.csproj and reloading the window causes omnisharp to load both projects correctly.
The text was updated successfully, but these errors were encountered: