Centralize TFM infrastructure (#4971)

Author: hoyosjs

Directory.Build.props

@@ -10,7 +10,7 @@
     <TreatWarningsAsErrors>true</TreatWarningsAsErrors>
     <SuppressNETCoreSdkPreviewMessage>true</SuppressNETCoreSdkPreviewMessage>
     <_SkipUpgradeNetAnalyzersNuGetWarning>true</_SkipUpgradeNetAnalyzersNuGetWarning>
-</PropertyGroup>
+  </PropertyGroup>
 
   <PropertyGroup>
     <PackageIconUrl>http://go.microsoft.com/fwlink/?LinkID=288859</PackageIconUrl>
@@ -19,4 +19,18 @@
     <EnableSourceControlManagerQueries>true</EnableSourceControlManagerQueries>
     <GitHubRepositoryName>diagnostics</GitHubRepositoryName>
   </PropertyGroup>
+
+  <PropertyGroup>
+    <!-- This represents the minimum supported .NET Version, so the min
+    version that the tools must be able to run against for a simple customer
+    experience.
+    When bumping this, bump __targetRid in build.sh/build-native.cmd
+    and modify the Debugger.Tests.Configs to reflect the new TFMs -->
+    <NetCoreAppMinVersion>6.0</NetCoreAppMinVersion>
+    <NetCoreAppMinTargetFramework>net$(NetCoreAppMinVersion)</NetCoreAppMinTargetFramework>
+    <!-- this is the list of TFMs we build our debuggees and tracees as. -->
+    <SupportedSubProcessTargetFrameworks>net6.0;net7.0;net8.0;net9.0</SupportedSubProcessTargetFrameworks>
+    <!-- this is the list of TFMs we build our unit tests as. -->
+    <SupportedXUnitTestTargetFrameworks>net6.0;net7.0;net8.0</SupportedXUnitTestTargetFrameworks>
+  </PropertyGroup>
 </Project>

documentation/privatebuildtesting.md

@@ -9,7 +9,7 @@ Here are some instructions on how to run the diagnostics repo's tests against a
 4. On Windows 11 (this doesn't work on Windows 10), add the following DWORD registry key: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\MiniDumpSettings\DisableAuxProviderSignatureCheck` and set it to 1. This allows the unsigned privately built DAC to be used to generate dumps.
 5. Copy the private runtime binaries over the test SDK/runtimes installed in `.dotnet-test`. This step is hard to automate because there are usually 3 versions of the runtime installed: one as part of the .NET SDK, one as part of the AspNetCore runtime and one from latest runtime DARC update.
 6. Run the diagnostics repo tests either:
-   a. `test.cmd` or `test.sh` - this runs all the diagnostics tests including SOS's. A html test report will be generated in `artifacts/TestResults/{Debug,Release}/SOS.UnitTests_net6.0_x64.html`.
+   a. `test.cmd` or `test.sh` - this runs all the diagnostics tests including SOS's. A html test report will be generated in `artifacts/TestResults/{Debug,Release}/SOS.UnitTests_net8.0_x64.html`.
    b. Use the VS Test Explorer to run all the SOS tests or a specific one.
    c. Use `eng\testsos.cmd` or `eng/testsos.sh` to run just the SOS tests. The html test report isn't generated in this case, but the SOS test logs are in artifacts/TestResults/{Debug,Release}/sos_*.