Releases: tintoy/msbuild-project-tools-vscode
MSBuild Project Tools for VS Code v0.2.15
Changes
- Add support for passing language service configuration in
InitializeParams.InitializationOptions
(#17).
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.14
Changes
- 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.
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.13
Changes
- Diagnostics indicating invalid project contents or XML now have a range covering the whole element or attribute (where possible).
- Simplify extension / language-service configuration schema.
The extension will automatically upgrade settings in the legacy format (i.e. ones without'schemaVersion': 1
), but now ignores the oldmsbuildProjectFileTools
configuration section. - Bug-fix: completions for item metadata expressions being offered when only completions for item group expressions should be offered.
- Bug-fix:
NullReferenceException
when listing completions for item group expressions. - Bug-fix: restore missing hover tooltip for SDK-style project import.
- Bug-fix: metadata names in unused item groups are always named "Identity".
- Bug-fix: attribute completions are erroneously offered when creating a new element under an
ItemGroup
element (#21).
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.12
Changes
- Diagnostics indicating invalid project contents or XML now have a range covering the whole element or attribute (where possible).
- Simplify extension / language-service configuration schema.
The extension will automatically upgrade settings in the legacy format (i.e. ones without'schemaVersion': 1
), but now ignores the oldmsbuildProjectFileTools
configuration section. - Bug-fix: completions for item metadata expressions being offered when only completions for item group expressions should be offered.
- Bug-fix:
NullReferenceException
when listing completions for item group expressions. - Bug-fix: restore missing hover tooltip for SDK-style project import.
- Bug-fix: metadata names in unused item groups are always named "Identity".
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.10
Changes
- Bug-fix: Extension won't load, after changes for #18, if no configuration was specified (restore configuration defaults).
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.9
Changes
- Add command (
NuGet: toggle pre-release
) to toggle NuGet pre-release packages and package versions on / off (#18).
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.8
Changes
- More testing on MacOS and Linux.
- Experimental: Add completions for task elements based on task types declared in the project.
- Experimental: Add completions for task attributes based on task types declared in the project.
- Experimental: Parsing of MSBuild item transform expressions.
- Experimental: Add experimental feature flag (
empty-completion-lists
) to enable returning empty completion lists rather than null
Fixes #17.
We can't do this by default because our extension depends on VSCode's behaviour when null is returned vs an empty completion list (when null is returned, no completion list is displayed; when an empty completion list is returned, purely-textual completions are displayed based on current file contents).
This behaviour is mainly to support clients other than VSCode (e.g. aCute).
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.7
Changes
- Add setting to control which types of objects from the current projects are included when offering completions.
- Experimental: Add completions for qualified and unqualified item metadata expressions (
%(XXX.YYY)
and%(YYY)
).
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.6
Changes
- Bug-fix: attribute completions should be available on elements that don't currently have any attributes.
- Bug-fix: go-to-definition should also work for regular-style project imports (not just SDK-style imports).
- Experimental: Add completions for MSBuild property and item expressions (
$()
and@()
).
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.4
Changes
- Bug-fix: missing completions for top-level elements (e.g.
<PropertyGroup>
,<ItemGroup>
,<Target>
). - Improve help for well-known items and their metadata.
- Bug-fix for #11 (should not fail on non-standard file extension).
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.