Merge pull request #19440 from unoplatform/dev/jela/single-startup-tfm

fix(vs): Use single TFM build feature from VS

Author: jeromelaban

build/nuget/uno.winui.single-project.targets

@@ -118,7 +118,6 @@
 		<ProjectCapability Include="XamarinStaticLaunchProfiles" Condition=" '$(VisualStudioVersion)' != '' and '$(VisualStudioVersion)' &lt; '17.0' " />
 		<!-- Otherwise define LaunchProfilesGroupByPlatformFilters by default -->
 		<ProjectCapability Include="LaunchProfilesGroupByPlatformFilters" Condition=" '$(VisualStudioVersion)' == '' or '$(VisualStudioVersion)' &gt;= '17.0' " />
-		<ProjectCapability Include="SingleTargetBuildForStartupProjects" Condition=" '$(EnableSingleTargetBuildForStartupProjects)' != 'false' " />
 
 		<ProjectCapability Include="UseMauiCore" />
 

src/Uno.Sdk/Sdk/Sdk.props.buildschema.json

@@ -131,10 +131,6 @@
 			"description": "Disables removing the Microsoft.WindowsDesktop.App from the runtime configuration file in the output layout. Uno relies on loading WPF dynamically by searching for the WPF assemblies in the .NET SDK install folder.",
 			"type": "bool"
 		},
-		"UnoDisableVSFilterTargetFrameworkWithDebuggerTarget": {
-			"description": "Disables restricting the number of active target frameworks used when building a head project.",
-			"type": "bool"
-		},
 		"DisableWinUI8857_Workaround": {
 			"description": "Disables the WinUI workaround for issue 8857.",
 			"helpUrl": "https://github.com/microsoft/microsoft-ui-xaml/issues/8857",

src/Uno.Sdk/targets/Uno.ProjectCapabilities.targets

@@ -30,6 +30,12 @@
 		<ProjectCapability Include="WindowsXamlResourceDictionary"/>
 		<ProjectCapability Include="WindowsXamlUserControl"/>
 		<ProjectCapability Include="WindowsUniversalMultiViews"/>
+
+		<!-- 
+		Allow VS to start using a single TFM, instead of building all available TFMs when starting a debugging session
+		Note that this capability must be defined on all TFMs to be effectively enabled.
+		-->
+		<ProjectCapability Include="SingleTargetBuildForStartupProjects" Condition=" '$(EnableSingleTargetBuildForStartupProjects)' != 'false' " />
 	</ItemGroup>
 
 	<ItemGroup Condition=" '$(TargetFrameworks)' != '' AND ( $(TargetFrameworks.Contains('-ios')) OR $(TargetFrameworks.Contains('-android')) OR $(TargetFrameworks.Contains('-catalyst')) )">

src/Uno.Sdk/targets/Uno.SingleProject.VS.Build.targets

@@ -1,30 +1,2 @@
 <Project>
-
-	<Target Name="_UnoFilterTargetFrameworkWithDebuggerTarget"
-			BeforeTargets="_SetBuildInnerTarget;_ComputeTargetFrameworkItems"
-			Condition="
-				'$(BuildingInsideVisualStudio)'=='true'
-				AND '$(UnoDisableVSFilterTargetFrameworkWithDebuggerTarget)' != 'true'
-				AND '$(IsImplicitlyTriggeredBuild)' == 'true'
-				AND '$(IsUnoHead)' == 'true'
-				AND '$(ExcludeRestorePackageImports)' != 'true' ">
-
-		<!-- 
-			This target is used to restrict the number of active target frameworks used when
-			building a head project. This current version uses $(_IsExecutable) in order to
-			allow for faster builds with the uno.templates `Server` project.
-
-			Filtering on `IsImplicitlyTriggeredBuild` implies that this target will be 
-			executed only when the debugger command is used. An explicit build or rebuild
-			on the project will perform a full build.
-
-			This will be enhanced in the future to support class libraries as well.
-		-->
-
-		<PropertyGroup Condition=" '$(TargetFramework)'=='' AND '$(_SelectedTargetFramework)' != '' ">
-			<TargetFramework>$(_SelectedTargetFramework)</TargetFramework>
-			<TargetFrameworks>$(_SelectedTargetFramework)</TargetFrameworks>
-		</PropertyGroup>
-	</Target>
-
 </Project>