MSBuild Project Tools language service v0.3.1

Changes

• Language service now targets .NET Core 3.0 (tintoy/msbuild-project-tools-server#17).

Notes

If you want to use the MSBuild language service, you must have the .NET Core 3.0 SDK or runtime 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 language service v0.2.55

Changes

• Use tab-character in completion text (tintoy/msbuild-project-tools-server#13).
• Improve calculation logic for MSBuild ToolsVersion (tintoy/msbuild-project-tools-server#16).

Notes

If you want to use the 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 language service v0.2.53

Changes

• Upgrade MSBuild packages to v15.9.20 (tintoy/msbuild-project-tools-server#14).
• Add UserSecretsId to well-known properties (#48).
• Use correct MSBuild SDK folder for .NET Core 3.0 and newer (#46).
• Enable per-workspace override of MSBuildExtensionsPath and MSBuildExtensionsPath32 (#35).
• Prevent "dotnet --info" hanging when its output is larger than the process STDOUT buffer (#42).

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 language service v0.2.42

Changes

• Initial support for flattened (path-based) extension settings (tintoy/msbuild-project-tools-server#7).
  Note that once the extension has migrated your settings to the new format, you will need to manually remove the old settings (unfortunately, VS Code doesn't really support extensions modifying settings that they haven't declared in their manifest).
• Started removing file-system hyperlinks from hover tooltips, since VS Code no longer renders them correctly.

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 language service v0.2.38

Changes

• Improve log output (especially for project-load failures).
• Support overriding of MSBuild SDKs path via environment variable (tintoy/msbuild-project-tools-server#5).
• Bug-fix: ArgumentException (parameter name: itemType) when requesting completions on root Project element (tintoy/msbuild-project-tools-server#5).
• Produce cleaner stack-traces using Demystifier.
• Generate hover content with help and documentation links for well-known MSBuild XML elements that don't directly correspond to MSBuild objects (tintoy/msbuild-project-tools-server#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).

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 language service v0.2.37

Changes

• Support overriding of MSBuild SDKs path via environment variable (tintoy/msbuild-project-tools-server#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).

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 language service v0.2.36

Changes

• Bug-fix: ArgumentException(itemType) when requesting completions on root Project element (tintoy/msbuild-project-tools-server#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).

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 language service v0.2.35

Changes

• Display help and documentation links for well-known MSBuild XML elements (tintoy/msbuild-project-tools-server#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).

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

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

Changes

• Add completion for IsPackable property.

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.