Set NetCurrent so that it doesn't roll forward automatically (#10622)

* Set NetCurrent so that it doesn't roll forward automatically The VSTest repo can't use a floating NetCurrent value as the NetCurrent TFM is actually hardcoded in a number of places => .nuspec files. Set it to net9.0 explicitly so that the build continues to work with a .NET 10 SDK and Arcade 10 SDK (which is used inside the VMR). Don't hardcode the value when building from source as in that configuration, the TFM needs to actually target the very latest. * Update Directory.Build.props --------- Co-authored-by: Jakub Jareš <[email protected]>
microsoft · Dec 10, 2024 · fc78508 · fc78508
1 parent 7d34b30
commit fc78508
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/Directory.Build.props b/Directory.Build.props
@@ -52,6 +52,8 @@
   <PropertyGroup>
     <!-- Naming is based on dotnet/runtime one -->
     <NetFrameworkMinimum>net462</NetFrameworkMinimum>
+    <!-- When not building from source, hardcode the NetCurrent TFM value as it is hardcoded in a number of places, i.e. nuspec files. -->
+    <NetCurrent Condition="'$(DotNetBuildSourceOnly)' != 'true'">net9.0</NetCurrent>
     <NetCoreAppMinimum>netcoreapp3.1</NetCoreAppMinimum>
     <!--
       Arcade is making things hard to work with. This property is unset when its value is equal to NetMinimum.