MSBuild project tools for VS Code v0.1.0-beta2

If you want to use the new MSBuild language service, you must have .NET Core 2.0 present on the system path (but your project can target whatever platform / version it wants to). If you don't have it, then the extension will fall back to using the classic PackageReference completion provider (MSBuild-related functionality will not be available).

Changes

• The extension now uses a language service based on Microsoft's Language Server Protocol.
• Tooltips for MSBuild objects in the project file.
• Support for any configured (remote) package source.
  We're using the new NuGet client libraries so it should understand global, solution-local, and project-local package sources.
• Highly-improved handling of project files with broken or invalid XML (thanks to Microsoft.Language.Xml).
• Implemented configuration property (msbuildProjectFileTools.languageService.enable) to switch between MSBuild language engine and classic completion provider.
• Implemented go-to-definition for project-style and SDK-style imports.
• Detect .NET Core version on startup, and fall back to classic completion provider if >= 2.0.0 is not available.
• More informative tooltips on hover
• Handle multiple items originating from a single item group element in the XML.
• Improved error handling

Installing

To use this extension, either install it from the VS marketplace, or download the VSIX package and install it by choosing "Install from VSIX" from the menu on the top right of the extensions panel in VS Code.

More information

See the README for more information.

MSBuild project tools for VS Code v0.1.0

Changes

• The extension now uses a language service based on Microsoft's Language Server Protocol.
• Tooltips for MSBuild objects in the project file.
• Support for any configured (remote) package source.
  We're using the new NuGet client libraries so it should understand global, solution-local, and project-local package sources.
• Highly-improved handling of project files with broken or invalid XML (thanks to Microsoft.Language.Xml).
• Implemented configuration property (msbuildProjectFileTools.languageService.enable) to switch between MSBuild language engine and classic completion provider.
• Implemented go-to-definition for project-style and SDK-style imports.
• Detect .NET Core version on startup, and fall back to classic completion provider if >= 2.0.0 is not available.
• More informative tooltips on hover
• Handle multiple items originating from a single item group element in the XML.
• Improved error handling
• Partial fix for incorrect handling of non-windows line endings (see #4.

Notes

If you want to use the new MSBuild language service, you must have .NET Core 2.0 present on the system path (but your project can target whatever platform / version it wants to). If you don't have it, then the extension will fall back to using the classic PackageReference completion provider (MSBuild-related functionality will not be available).

Installing

To use this extension, either install it from the VS marketplace, or download the VSIX package and install it by choosing "Install from VSIX" from the menu on the top right of the extensions panel in VS Code.

More information

See the README for more information.

MSBuild project tools for VS Code v0.1.0-beta1

Note: this is an early release - it's not entirely ready for production use.

You must have .NET Core 2.0 present on the system path to use the MSBuild language service (but your project can target whatever version it wants). If you don't have it, then the extension will fall back to using the classic PackageReference completion provider (MSBuild-related functionality will not be available).

Changes

• The extension now uses a language service based on Microsoft's Language Server Protocol.
• Tooltips for MSBuild objects in the project file.
• Support for any configured (remote) package source.
  We're using the new NuGet client libraries so it should understand global, solution-local, and project-local package sources.
• Highly-improved handling of project files with broken or invalid XML (thanks to Microsoft.Language.Xml).
• Implemented configuration property (msbuildProjectFileTools.languageService.enable) to switch between MSBuild language engine and classic completion provider.
• Implemented go-to-definition for project-style and SDK-style imports.
• Detect .NET Core version on startup, and fall back to classic completion provider if >= 2.0.0 is not available.

Installing

To use this download the VSIX package and install it by choosing "Install from VSIX" from the menu on the top right of the extensions panel in VS Code.

More information

See the README for more information.

MSBuild project tools for VS Code v0.1.0-alpha1

Note: this is a highly experimental release - it won't destroy your machine, but it's definitely not ready for production use.

You must have .NET Core 2.0 installed to use the language server (but your project can target whatever version it wants).

Changes

• The extension now uses a language server based on Microsoft's Language Server Protocol.
• Tooltips for MSBuild objects in the project file.
• Support for any configured (remote) package source.
  We're using the new NuGet client libraries so it should understand global, solution-local, and project-local package sources.
• Highly-improved handling of project files with broken or invalid XML (thanks to Microsoft.Language.Xml).

Installing

To use this download the VSIX package and install it by choosing "Install from VSIX" from the menu on the top right of the extensions panel in VS Code.

More information

See the README for more information.

MSBuild project tools for VS Code v0.1.0-alpha2

Note: this is a highly experimental release - it won't destroy your machine, but it's definitely not ready for production use.

You must have .NET Core 2.0 installed to use the language server (but your project can target whatever version it wants).

Note that the new MSBuild language service is disabled by default; you can enable it by setting msbuildProjectFileTools.languageService.enable to true in your settings file.

Changes

• The extension now uses a language server based on Microsoft's Language Server Protocol.
• Tooltips for MSBuild objects in the project file.
• Support for any configured (remote) package source.
  We're using the new NuGet client libraries so it should understand global, solution-local, and project-local package sources.
• Highly-improved handling of project files with broken or invalid XML (thanks to Microsoft.Language.Xml).
• Add configuration property (msbuildProjectFileTools.languageService.enable) to switch between MSBuild language engine and classic completion provider.

Installing

To use this download the VSIX package and install it by choosing "Install from VSIX" from the menu on the top right of the extensions panel in VS Code.

More information

See the README for more information.

MSBuild project tools for VS Code v0.0.2

Changes

• Resolve the URL for the NuGet v3 AutoComplete API at extension startup.

Installing

To use this extension, either install it from the VS marketplace, or download the VSIX package and install it by choosing "Install from VSIX" from the menu on the top right of the extensions panel in VS Code.

More information

See the README for more information.

MSBuild project tools for VS Code v0.0.1

Initial release.

Installing

To install this extension, download the VSIX package and install it by choosing "Install from VSIX" from the menu on the top right of the extensions panel in VS Code.

More information

See the README for more information.