src/modules/cmdpal/ext/Common.ExtDependencies.props

<?xml version="1.0" encoding="utf-8"?>
<Project>

  <!--
  Common external dependencies for all CmdPal extensions:
  - Microsoft.WindowsAppSDK
  - Microsoft.Web.WebView2
  - Microsoft.CommandPalette.Extensions.Toolkit (via project reference)

  We need the WASDK reference because without it, our image assets won't get
  placed into our final package correctly.

-->

  <ItemGroup>
    <PackageReference Include="Microsoft.WindowsAppSDK" />
    <PackageReference Include="Microsoft.Web.WebView2"  />
  </ItemGroup>
  <ItemGroup>
    <ProjectReference Include="..\..\extensionsdk\Microsoft.CommandPalette.Extensions.Toolkit\Microsoft.CommandPalette.Extensions.Toolkit.csproj" />
  </ItemGroup>
</Project>
CmdPal: fix missing builtin icons (#41298) It would seem that the way we absorb the icons for built-in extension into our package relies on the _extension_ package including WASDK. I don't fully understand why. This PR adds a common `.props` file we can use for all extensions, to make sure they include it. regressed in #41261 Closes #41279 2025-08-24 20:50:32 -05:00			`<?xml version="1.0" encoding="utf-8"?>`
			`<Project>`

CmdPal: Configure .editorconfig to format MSBuild files (#45739) ## Summary of the Pull Request This PR configures the Command Palette's .editorconfig to format MSBuild project and props files, and reformats the files accordingly. No functional changes. 2026-02-24 21:50:17 +01:00			`<!--`
CmdPal: fix missing builtin icons (#41298) It would seem that the way we absorb the icons for built-in extension into our package relies on the _extension_ package including WASDK. I don't fully understand why. This PR adds a common `.props` file we can use for all extensions, to make sure they include it. regressed in #41261 Closes #41279 2025-08-24 20:50:32 -05:00			`Common external dependencies for all CmdPal extensions:`
			`- Microsoft.WindowsAppSDK`
			`- Microsoft.Web.WebView2`
			`- Microsoft.CommandPalette.Extensions.Toolkit (via project reference)`

			`We need the WASDK reference because without it, our image assets won't get`
CmdPal: Configure .editorconfig to format MSBuild files (#45739) ## Summary of the Pull Request This PR configures the Command Palette's .editorconfig to format MSBuild project and props files, and reformats the files accordingly. No functional changes. 2026-02-24 21:50:17 +01:00			`placed into our final package correctly.`
CmdPal: fix missing builtin icons (#41298) It would seem that the way we absorb the icons for built-in extension into our package relies on the _extension_ package including WASDK. I don't fully understand why. This PR adds a common `.props` file we can use for all extensions, to make sure they include it. regressed in #41261 Closes #41279 2025-08-24 20:50:32 -05:00
			`-->`
CmdPal: Configure .editorconfig to format MSBuild files (#45739) ## Summary of the Pull Request This PR configures the Command Palette's .editorconfig to format MSBuild project and props files, and reformats the files accordingly. No functional changes. 2026-02-24 21:50:17 +01:00
CmdPal: fix missing builtin icons (#41298) It would seem that the way we absorb the icons for built-in extension into our package relies on the _extension_ package including WASDK. I don't fully understand why. This PR adds a common `.props` file we can use for all extensions, to make sure they include it. regressed in #41261 Closes #41279 2025-08-24 20:50:32 -05:00			`<ItemGroup>`
			`<PackageReference Include="Microsoft.WindowsAppSDK" />`
			`<PackageReference Include="Microsoft.Web.WebView2" />`
			`</ItemGroup>`
			`<ItemGroup>`
			`<ProjectReference Include="..\..\extensionsdk\Microsoft.CommandPalette.Extensions.Toolkit\Microsoft.CommandPalette.Extensions.Toolkit.csproj" />`
			`</ItemGroup>`
			`</Project>`