MSBuild Project Tools language service v0.2.35

Changes

• Display help and documentation links for well-known MSBuild XML elements (#5).
• Log cleaner stack-traces using Demystifier.

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

More information

See the README for more information.

MSBuild Project Tools language service v0.2.34

Changes

• Display help and documentation links for well-known MSBuild XML elements (#5).

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

More information

See the README for more information.

MSBuild Project Tools language service v0.2.33

Changes

• Expression support is no longer experimental!
• Ensure package Ids and versions appear before other completion types in PackageReference elements / attributes.
• Correctly handle parsing of MSBuild expressions where the root expression is an unquoted string (i.e. composite expression including one or more string-literal text sequences).

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

More information

See the README for more information.

MSBuild Project Tools language service v0.2.31

Changes

• When expression completions are enabled, ensure that package Ids and versions appear before other completion types in PackageReference elements / attributes.

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

More information

See the README for more information.

MSBuild Project Tools language service v0.2.29

Changes

• Bug-fix: Language server process fails to terminate correctly on Linux (tintoy/msbuild-project-tools-vscode#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).

More information

See the README for more information.

MSBuild Project Tools language service v0.2.28

Changes

• Add completion for LangVersion property.
• Improve metadata completions for Content items.
• Wait for Exit notification before terminating server process (tintoy/msbuild-project-tools-vscode#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).

More information

See the README for more information.

MSBuild Project Tools language service v0.2.27

Changes

• LSP library's logging now uses configured logging level.

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

More information

See the README for more information.

MSBuild Project Tools language service v0.2.25

Changes

• 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).

More information

See the README for more information.

MSBuild Project Tools language service v0.2.24

Changes

• Make ASP.NET core snippets version-specific by @doggy8088 (tintoy/msbuild-project-tools-vscode#32).
• Implement default value(s) for well-known property completions (tintoy/msbuild-project-tools-vscode#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).

More information

See the README for more information.

MSBuild Project Tools language service v0.2.23

Changes

• Use latest version of OmniSharp LSP libraries (improves stability and diagnostic capabilities).

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

More information

See the README for more information.