Comments (29)
Sure no problem - will let you know as soon as I have something to test 🙂
from msbuild-project-tools-vscode.
Sorry, it's been a long day - I meant to upload the package as an attachment to that comment 😂
msbuild-project-tools-0.4.6-dev.zip
You may need to explicitly uninstall the extension version from the marketplace before you install from the VSIX package (Extensions -> Install from VSIX) and, afterwards, you can do the reverse to go back to automatic updates.
from msbuild-project-tools-vscode.
Great - thanks for testing! I’ll make sure nothing else is broken and then publish a new version of the extension to the gallery.
from msbuild-project-tools-vscode.
All good, I'm just relieved that it's working for you 🙂
I'll try to improve the error message though.
from msbuild-project-tools-vscode.
Published v0.4.4 of MSBuild Project Tools extension to the gallery.
@geniuskamo - here is the Codespace-enabled repository I've been testing with: https://github.com/tintoy/msbuild-project-tools-codespace-demo
from msbuild-project-tools-vscode.
Thank you @tintoy
from msbuild-project-tools-vscode.
Published v0.4.4 of MSBuild Project Tools extension to the gallery.
@geniuskamo - here is the Codespace-enabled repository I've been testing with: https://github.com/tintoy/msbuild-project-tools-codespace-demo
How do I use this ?
from msbuild-project-tools-vscode.
I'm also trying to run this, I'm using v0.4.5 inside a Dev Container. The language server doesn't appear to be working for me
from msbuild-project-tools-vscode.
This is what I see inside the dev tools
from msbuild-project-tools-vscode.
Are you on the latest version of the extension?
There is a setting to turn up the log level for MSBuild Project Tools - can you try setting that to “Verbose” and trying again?
from msbuild-project-tools-vscode.
msbuild-project-tools-vscode/package.json
Line 53 in ea103ed
from msbuild-project-tools-vscode.
I tried setting the logging level to verbose for the devcontainer.json and also the .vscode settings.json. It did not give any additional output other than what I screenshotted above. I am connecting to the dev container using VSCode's built in ssh client if that matters
from msbuild-project-tools-vscode.
from msbuild-project-tools-vscode.
Hmm - I can’t say I’ve seen that one before. I’ll have a look tonight after work and see if I can reproduce the problem.
Just out of curiosity, what is the output of dotnet --info
when run in that container?
from msbuild-project-tools-vscode.
The extension is executing within the container. My VSCode instance on the laptop is connecting to that container.
From Container
.NET SDK (reflecting any global.json):
Version: 6.0.301
Commit: 43f9b18481
Runtime Environment:
OS Name: debian
OS Version: 11
OS Platform: Linux
RID: debian.11-x64
Base Path: /usr/share/dotnet/sdk/6.0.301/
Host (useful for support):
Version: 6.0.6
Commit: 7cca709db2
.NET SDKs installed:
6.0.301 [/usr/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.6 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.6 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET runtimes or SDKs:
https://aka.ms/dotnet-download
From Container Host
.NET SDK (reflecting any global.json):
Version: 6.0.106
Commit: 4f1e0330de
Runtime Environment:
OS Name: arch
OS Version:
OS Platform: Linux
RID: arch-x64
Base Path: /usr/share/dotnet/sdk/6.0.106/
Host (useful for support):
Version: 6.0.6
Commit: 7cca709db2
.NET SDKs installed:
6.0.106 [/usr/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.6 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.6 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET runtimes or SDKs:
https://aka.ms/dotnet-download
From Host (my laptop)
.NET SDK (reflecting any global.json):
Version: 6.0.107
Commit: f6ec7508e3
Runtime Environment:
OS Name: arch
OS Version:
OS Platform: Linux
RID: arch-x64
Base Path: /usr/share/dotnet/sdk/6.0.107/
global.json file:
Not found
Host:
Version: 6.0.7
Architecture: x64
Commit: 0ec02c8c96
.NET SDKs installed:
6.0.107 [/usr/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.NETCore.App 6.0.7 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
Download .NET:
https://aka.ms/dotnet-download
Learn about .NET Runtimes and SDKs:
https://aka.ms/dotnet/runtimes-sdk-info
from msbuild-project-tools-vscode.
Sorry, one last question - what version of the extension is VSCode showing (both local and remote)?
from msbuild-project-tools-vscode.
Both local and remote have v0.4.5 installed
from msbuild-project-tools-vscode.
Ok - it looks like it’s failing because there is no global.json
section in the output (because the section names are localised, we have to count them in order to find the one we want). Interestingly, the output from your local machine does include this section but the container does not.
If you add a global.json
file to the solution directory you’re accessing in the container, does the output then include that section?
I’m trying to work out whether we have to somehow guess if that section is present or not…
from msbuild-project-tools-vscode.
Ok, it looks like they finally added support for directly listing SDKs and runtime versions:
I’ll have a go at switching over to using this instead of parsing the output of dotnet --info
(previously, this was the only way to discover SDK versions and their containing directories)…
from msbuild-project-tools-vscode.
If you create a pre-release I could test your change in my container
from msbuild-project-tools-vscode.
Sorry, am still working on this - work has been a little hectic this week 🙂
Should be ready soon.
from msbuild-project-tools-vscode.
@loligans - can you try this build? I think the extension should now have a better chance at handling various forms of output from the dotnet
command-line tool, but the .NET-side code in the language server itself may still have issues.
from msbuild-project-tools-vscode.
Yes, how can I install it into my container? I don't see a new version when I choose "Install Another Version" in the extension settings
from msbuild-project-tools-vscode.
I tried going back to v0.4.4 and the language server works again. I will still try your build when it becomes available :)
from msbuild-project-tools-vscode.
Haha no problem! I just tested your fix and its working!
from msbuild-project-tools-vscode.
Published v0.4.6 of the extension to the gallery (the .NET-side language server implementation is also more robust now).
from msbuild-project-tools-vscode.
Latest version running in the container gives me this exception:
Starting MSBuild language service...
Failed to start the MSBuild language server.
Error: Command failed: "/usr/bin/dotnet" "/home/loligans/.vscode-server/extensions/tintoy.msbuild-project-tools-0.4.6/out/language-server/MSBuildProjectTools.LanguageServer.Host.dll" --probe
System.ArgumentException: '' is not a valid version string. (Parameter 'value')
at NuGet.Versioning.SemanticVersion.Parse(String value)
at MSBuildProjectTools.LanguageServer.Utilities.DotNetRuntimeInfo.ParseDotNetVersionOutput(TextReader dotnetVersionOutput) in D:\Development\github\tintoy\msbuild-project-tools-vscode\lib\server\src\LanguageServer.Common\Utilities\DotNetRuntimeInfo.cs:line 140
at MSBuildProjectTools.LanguageServer.Utilities.DotNetRuntimeInfo.GetCurrent(String baseDirectory, ILogger logger) in D:\Development\github\tintoy\msbuild-project-tools-vscode\lib\server\src\LanguageServer.Common\Utilities\DotNetRuntimeInfo.cs:line 69
at MSBuildProjectTools.LanguageServer.Utilities.MSBuildHelper.DiscoverMSBuildEngine(String baseDirectory, ILogger logger) in D:\Development\github\tintoy\msbuild-project-tools-vscode\lib\server\src\LanguageServer.Common\Utilities\MSBuildHelper.cs:line 96
at MSBuildProjectTools.LanguageServer.Program.Main() in D:\Development\github\tintoy\msbuild-project-tools-vscode\lib\server\src\LanguageServer\Program.cs:line 39
System.ArgumentException: '' is not a valid version string. (Parameter 'value')
at NuGet.Versioning.SemanticVersion.Parse(String value)
at MSBuildProjectTools.LanguageServer.Utilities.DotNetRuntimeInfo.ParseDotNetVersionOutput(TextReader dotnetVersionOutput) in D:\Development\github\tintoy\msbuild-project-tools-vscode\lib\server\src\LanguageServer.Common\Utilities\DotNetRuntimeInfo.cs:line 140
at MSBuildProjectTools.LanguageServer.Utilities.DotNetRuntimeInfo.GetCurrent(String baseDirectory, ILogger logger) in D:\Development\github\tintoy\msbuild-project-tools-vscode\lib\server\src\LanguageServer.Common\Utilities\DotNetRuntimeInfo.cs:line 69
at MSBuildProjectTools.LanguageServer.Utilities.MSBuildHelper.DiscoverMSBuildEngine(String baseDirectory, ILogger logger) in D:\Development\github\tintoy\msbuild-project-tools-vscode\lib\server\src\LanguageServer.Common\Utilities\MSBuildHelper.cs:line 96
at MSBuildProjectTools.LanguageServer.Program.Main() in D:\Development\github\tintoy\msbuild-project-tools-vscode\lib\server\src\LanguageServer\Program.cs:line 39
from msbuild-project-tools-vscode.
I think I spoke too soon, sorry. I simply rebuilt the container and it started working again. I appreciate your awesome work by supporting this extension! If you had a sponsor link for the project where I could donate to support, I would definitely like to do that
from msbuild-project-tools-vscode.
What do you get when you run dotnet --version
in the container?
from msbuild-project-tools-vscode.
Related Issues (20)
- Support for Microsoft.Build.CentralPackageVersions HOT 4
- Support for PackageReference elements with Update attribute instead of Include
- Language server unable to start - `dotnet --version` failure HOT 20
- Also provide features as extension to `redhat.vscode-xml` HOT 4
- C# Dev Kit Breaks HOT 5
- In current release version of the extension language server is built in debug mode HOT 3
- Autocomplete/Intellisense Only Works After The Last Grouped Entry When Initiated By `<`. HOT 1
- Failed to start the MSBuild language server after updating to v0.5.0 HOT 19
- Probing language server might not be needed HOT 12
- Initializing MSBuild project tools runs forever HOT 14
- Support using versions of MSBuild shipped with SDK Previews HOT 20
- Release Process HOT 7
- Failed to start the MSBuild language server. (after .NET 6 upgrade) HOT 11
- Version autocomplete no longer works for .netstandard2.1 (Linux, .NET 6) HOT 8
- Azure DevOps packages are ignored for version auto-complete HOT 7
- Using `ItemGroup`, `PropertyGroup` (etc) suggestions from the extension results in incorrect indentation HOT 3
- [Question] Using extension with .NET5 HOT 2
- "Unable to start MSBuild language server" HOT 9
- Unable to parse output from `dotnet --info` and activate the extension HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from msbuild-project-tools-vscode.