MSBuild Project Tools for VS Code v0.2.29

Changes

• Bug-fix: Language server process fails to terminate correctly on Linux (#36).

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.2.28

Changes

• Add completion for LangVersion property.
• Improve metadata completions for Content items.
• Wait for Exit notification before terminating server process (#36).
• LSP library's logging now uses configured logging level.
• Implement completion for XML comments.
• Implement completion for top-level <Import> element.

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.2.24

Changes

• Make ASP.NET core snippets version-specific by @doggy8088 (#32).
• Implement default value(s) for well-known property completions (#31).

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.2.22

Changes

• Improve MSBuild snippets by @doggy8088 (#30).
  Note: MSBuild snippets are visible when the file's language is set to MSBuild, not XML (see the README section on file extensions for details).

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.2.21

Changes

• Add MSBuild snippets by @doggy8088 (#28).
• Bug-fix: language server fails to shut down cleanly (OmniSharp/csharp-language-server-protocol#60).

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.2.20

Changes

• Log errors encountered while warming up NuGet client as Verbose instead of Error (tintoy/msbuild-project-tools-server#2).

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.2.19

Changes

• Bug-fix: Completions don't always work correctly in .props files (#27).
• Use latest OmniSharp LSP packages.

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.2.18

Changes

• Fix "invalid static method invocation syntax" error by using v15.5.x of MSBuild packages (tintoy/msbuild-project-tools-server#1).

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.2.17

Changes

• Add completions for item elements.
• Split out language server from VS Code extension.
• Bug-fix: output window being auto-focused due to incorrect LSP tracing configuration (#25).

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.2.16

Changes

• Bug-fix: language server does not correctly report server capabilities when first initialised (#22).

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.