Skip to content

Commit b88e0c8

Browse files
committed
Fix build: remove Vsix ProjectReference that breaks dotnet build on Windows
The net472+UseWPF Vsix project cannot be evaluated by the .NET 10 SDK without triggering 'target platform must be set to Windows'. Referencing it from Tests.csproj (even with Build=false) causes dotnet build to fail. Remove the reference - the Vsix tests already skip gracefully when the output directory is absent (VsixDoesNotReferenceNewerBclPolyfillsThanOldestSupportedVs now returns early like the second test). Build Vsix separately with msbuild. https://claude.ai/code/session_01AkwUvu3XuCdj3D4axoX4UX
1 parent 08b900d commit b88e0c8

File tree

1 file changed

+0
-9
lines changed

1 file changed

+0
-9
lines changed

Tests/Tests.csproj

Lines changed: 0 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -41,13 +41,4 @@
4141
<ItemGroup>
4242
<ProjectReference Include="..\CodeConv\CodeConv.csproj" />
4343
</ItemGroup>
44-
<!--
45-
The Vsix project is a net472 Windows-only project and only builds under an MSBuild that has
46-
the WindowsDesktop SDK available. We reference it so that VsixAssemblyCompatibilityTests can
47-
statically verify the Vsix output, but only in environments that can actually build it
48-
(i.e. Windows). Elsewhere the tests that depend on Vsix output will skip.
49-
-->
50-
<ItemGroup Condition="'$(OS)' == 'Windows_NT'">
51-
<ProjectReference Include="..\Vsix\Vsix.csproj" ReferenceOutputAssembly="false" SkipGetTargetFrameworkProperties="true" PrivateAssets="all" Build="false" />
52-
</ItemGroup>
5344
</Project>

0 commit comments

Comments
 (0)