v0.6.3

Change Log

v0.6.3

• Improve handling of concurrent loads for MSBuild sub-projects (fixes tintoy/msbuild-project-tools-server#100).

v0.6.0

• Extension startup time has been improved.
• The MSBuild language server now runs on .NET 8.
• Isolated runtime for the language server is back, so users no longer need to have a specific version of .NET to be installed to be able to use the extension.

v0.5.3

• Improve file-access behaviour for project.assets.json (tintoy/msbuild-project-tools-server#82).

v0.5.2

• Revert usage of the vscode-dotnet-runtime extension (#89 - isolated runtimes are problematic if you want to use global SDKs).

v0.5.1

• Temporary roll-back from v0.5.0 to v0.4.5 (#137).

v0.5.0

• The .NET runtime, required to run the language server, is now acquired using the vscode-dotnet-runtime extension as a dependency (so you don't need to have that specific version of .NET on your machine installed to use the extension)
• All completion are now shown by default
• Basic integration with redhat.vscode-xml extension is now provided, so you can use its features for msbuild language
• Language server, packed with the extension, is now built in release mode
• Extension bundle size has been significantly optimized
• Dependencies have been updaded to address known security vulnerabilities

v0.4.9

• Wait for redirected STDOUT/STDERR streams to complete when launching dotnet host process (#105, tintoy/msbuild-project-tools-server#28).
  Thanks, @tillig!

v0.4.8

• Selectively enable COREHOST_TRACE when launching dotnet executable to probe .NET SDKs (#105, tintoy/msbuild-project-tools-server#28).

v0.4.7

• Enable logging from .NET / MSBuild-engine discovery logic during language-server startup (tintoy/msbuild-project-tools-server#28).

v0.4.6

• Simplify logic for detecting .NET host version (#99).

v0.4.5

• Improve parsing of output from dotnet --info (#98).

v0.4.4

• Always roll forward to the latest (stable) installed version of the runtime (#90).
• Mark extension as a workspace extension to enable correct behaviour in remote scenarios (#99).

v0.6.0

Change Log

v0.6.0

• Extension startup time has been improved.
• The MSBuild language server now runs on .NET 8.
• Isolated runtime for the language server is back, so users no longer need to have a specific version of .NET to be installed to be able to use the extension.

v0.5.3

• Improve file-access behaviour for project.assets.json (tintoy/msbuild-project-tools-server#82).

v0.5.2

• Revert usage of the vscode-dotnet-runtime extension (#89 - isolated runtimes are problematic if you want to use global SDKs).

v0.5.1

• Temporary roll-back from v0.5.0 to v0.4.5 (#137).

v0.5.0

• The .NET runtime, required to run the language server, is now acquired using the vscode-dotnet-runtime extension as a dependency (so you don't need to have that specific version of .NET on your machine installed to use the extension)
• All completion are now shown by default
• Basic integration with redhat.vscode-xml extension is now provided, so you can use its features for msbuild language
• Language server, packed with the extension, is now built in release mode
• Extension bundle size has been significantly optimized
• Dependencies have been updaded to address known security vulnerabilities

v0.4.9

• Wait for redirected STDOUT/STDERR streams to complete when launching dotnet host process (#105, tintoy/msbuild-project-tools-server#28).
  Thanks, @tillig!

v0.4.8

• Selectively enable COREHOST_TRACE when launching dotnet executable to probe .NET SDKs (#105, tintoy/msbuild-project-tools-server#28).

v0.4.7

• Enable logging from .NET / MSBuild-engine discovery logic during language-server startup (tintoy/msbuild-project-tools-server#28).

v0.4.6

• Simplify logic for detecting .NET host version (#99).

v0.4.5

• Improve parsing of output from dotnet --info (#98).

v0.4.4

• Always roll forward to the latest (stable) installed version of the runtime (#90).
• Mark extension as a workspace extension to enable correct behaviour in remote scenarios (#99).

0.4.3

• Fix ArgumentNullException from NuGet client library when requesting package version completions (#91).

0.4.0

• Support for manually ignoring configured package sources using the msbuildProjectTools.nuget.ignorePackageSources extension setting (tintoy/msbuild-project-tools-server#24).
• Support for automatically ignoring configured package sources when the v3 service index indicates that they don't support the NuGet completion API (tintoy/msbuild-project-tools-server#24).

0.3.16

• Add support for additional wel-known metadata of ProjectReference items (tintoy/msbuild-project-tools-server#26).

0.3.15

• Improve error handling when project assets file was not found while updating NuGet package references for a project (tintoy/msbuild-project-tools-server#24).

0.3.14

• Correctly handle preview versions of the .NET SDK when discovering MSBuild instances (#74).

0.3.13

• Improve detection logic for .NET host version during extension startup (#73).

0.3.12

• Remove legacy ("classic") completion provider.
• Fix MSBuild-dependent tests that break in CI when the 5.0 SDK is also installed (tintoy/msbuild-project-tools-server#20).
• Upgrade language server to target .NET 5.0 (tintoy/msbuild-project-tools-server#22).

0.3.11

• Upgrade the language service to use the .NET Core 3.1 runtime (tintoy/msbuild-project-tools-server#20).

0.3.10

• Always use the MSBuild engine from the newest version of the .NET Core SDK (tintoy/msbuild-project-tools-server#19).

v0.3.8

• Completions now correctly replace trigger characters, if any (#67).

v0.3.7

• Explicitly watch parent process for termination (#53).

v0.3.6

• Update MSBuild engine packages to v16.5.0 (#66).

v0.3.4

• Add IntelliSense for GenerateDocumentationFile property (#60).

v0.3.3

• Use v16.4.0 of the MSBuild engine (#59).

v0.3.2

• Improved error reporting when language service cannot be started (tintoy/msbuild-project-tools-server#17).

v0.3.1

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

v0.2.55

• Improve calculation logic for MSBuild ToolsVersion (tintoy/msbuild-project-tools-server#16).

v0.2.54

• Use tab-character in completion text (tintoy/msbuild-project-tools-server#13).

v0.2.53

• Upgrade MSBuild packages to v15.9.20 (tintoy/msbuild-project-tools-server#14).

v0.2.52

• Add UserSecretsId to well-known properties (#48).

v0.2.51

• Use correct MSBuild SDK folder for .NET Core 3.0 and newer (#46).

v0.2.50

• Enable per-workspace override of MSBuildExtensionsPath and MSBuildExtensionsPath32 (#35).

v0.2.49

• Prevent "dotnet --info" hanging when its output is larger than the process STDOUT buffer (#42).

v0.2.47

• Improvements to logging during startup (#42).

v0.2.46

• Log configured package sources when initialising a project document (#44).

v0.2.45

• Handle localised output from dotnet --info (#43).

v0.2.44

• Fix bug in parsing of extension settings.

v0.2.43

• Optionally provide suggestions for packages from local (file-based) package sources (tintoy/msbuild-project-tools-server#9).

v0.2.42

• Initial support for flattened (path-based) extension settings (tintoy/msbuild-project-tools-server#7).
• Start removing file-system hyperlinks from hover tooltips, since VS Code no longer renders them correctly.

v0.2.41

• Use latest stable version of NuGet.Configuration to add support for encrypted credentials in NuGet.config (#39).

v0.2.39

• Further improvements to log output (especially for project-load failures; exceptions from invalid project XML are only logged when configured log level is Debug or Verbose).

v0.2.38

• Reduce size of VSIX package (tintoy/msbuild-project-tools-server#37).
• Improve log output (especially for project-load failures).

v0.2.37

• Support overriding of MSBuild SDKs path via environment variable (tintoy/msbuild-project-tools-server#5).

v0.2.36

• Bug-fix: ArgumentException (parameter name: itemType) when requesting completions on root Project element (tintoy/msbuild-project-tools-server#5).

v0.2.35

• Produce cleaner stack-traces using Demystifier.

v0.2.34

• Display help and documentation links for well-known MSBuild XML elements (tintoy/msbuild-project-tools-server#5).

v0.2.33

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

v0.2.32

• Expression support is no longer experimental!

v0.2.31

• Ensure package Ids and version appear before other completion types in PackageReference elements / attributes.

v0.2.30

• Add completion for IsPackable property.

v0.2.29

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

v0.2.28

• Add completion for LangVersion property.
• Improve metadata completions for Content items.
• Wait for Exit notification before terminating server process (#36).

v0.2.27

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

v0.2.26

• Implement completion for XML comments.

v0.2.25

• Implement completion for top-level <Import> element.

v0.2.24

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

v0.2.23

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

v0.2.22

• Improve MSBuild snippets by @doggy8088 (#30).

v0.2.21

• Add MSBuild snippets by @doggy8088 (#28).

v0.2.20

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

v0.2.19

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

v0.2.18

• Use v15.5.x of MSBuild packages (tintoy/msbuild-project-tools-server#1).

v0.2.17

• Add completions for item elements.
• Split out language server from VS Code extension.
• Never auto-show output window on messages from language server (#25).

v0.2.16

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

v0.2.15

• Add support for passing language service configuration in InitializeParams.InitializationOptions (#17).

v0.2.14

• Offer element completions, when appropriate, in whitespace or element text (#15).
• Improve completion behaviour.
• Improve performance of element and attribute completions for tasks in Target elements.

v0.2.13

• Bug-fix: attribute completions are erroneously offered when creating a new element under an ItemGroup element (#21).

#...

v0.4.1

Changes

• Support for .NET 6 (#88)
• Support for NuGet feeds requiring authentication (#39).

Notes

If you want to use the MSBuild language service, you must have the .NET Core 6.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.

v0.4.0

Changes

• Support for NuGet feeds requiring authentication (#39).

Notes

If you want to use the MSBuild language service, you must have the .NET Core 5.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.

v0.4.0-preview1

Initial support for .NET 6 (preview 7).

Has not been tested yet.

Note - this build requires (at a minimum) v6.0.0-preview.7.21378.6 of the .NET runtime.

MSBuild Project Tools language service v0.3.2

Changes

• Improved error reporting when language server cannot be started (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.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.