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