-
Notifications
You must be signed in to change notification settings - Fork 17
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
Failed to start the MSBuild language server. #74
Comments
What happens if you run |
Woah, thx for the fast reply :-)
|
Ah. Ok, I wasn't aware that the SDK version was using SemVer. Thanks, that will be relatively easy to fix. If you need to get going right away, you can use |
Good to know, but it's ok right now. I'll just wait to use/edit MSBuild projects until it's fixed and just use VS2019 if absolutely needed. And thanks a bunch for this extension. 🥇 |
msbuild-project-tools-0.3.14.vsix.zip When you have time, can you try uninstalling the extension and installing it from this VISX package? I think this should fix the problem but I don't any preview versions of the SDK installed at the moment to test with :) |
I'll give it a go and report back. |
MSBuild Project Tools output after install of
👍 👍 👍 Edit: Sorry, I don't have time right now to do a more extensive test but I'll load som msbuild projects up later and test them out. |
Thanks - will publish the new version soon :) |
I wondered a bit about the preview of dotnet sdk but of course I'm on the preview channel of VS 2019:
I'll soon update to VS2019 16.9.0 Preview 4.0 and report back (though I'll guess it'll work just fine). |
Updated to VS2019 16.9.0 Preview 4.0 with load succes.
... but loading a csproj did give me this in MSBuild Project Tools:
Don't know if it was also present in VS2019 16.9.0 Preview 2.0, but it seems to be unrelated and did successfully load the project according to the log. |
Ouch that seems like a silly bug (NREs usually are 🙂). Can you leave this one open and I’ll take a look later this morning? Thanks for the detailed report! |
I'll leave it open. |
Published v0.3.15 🙂 |
Thanks @tintoy |
Glad to hear it! 😃 I’ve generally found MSBuild to be a fast-moving target in the .NET Core world, so it’s good to hear that the solution we’ve chosen seems to be working 👍 |
I think it was after upgrading to vscode 1.53.2 this started, but honestly I'm not certain.
System info:
MSBuild Project Tools output:
The text was updated successfully, but these errors were encountered: