Two powershell scripts currently hardcode the TFM value:
|
$output = dotnet.exe "$currentLocation/artifacts/bin/dotnet-format/Release/net7.0/dotnet-format.dll" $solution --no-restore -v diag --verify-no-changes | Out-String |
|
Invoke-Expression 'dotnet run -c Release -f net7.0 --runtimes net7.0 --project dotnet-format.Performance.csproj -- --memory --join --filter Microsoft.CodeAnalysis.Tools.Perf.Micro*' |
While that wasn't a problem in the past, with now floating TFM versions defined by Arcade ($(NetCurrent)), the goal is to upgrade repositories to the next version of .NET more easily.
Ideally the two scripts would be replaced by simple msbuild projects (using the Microsoft.Build.NoTargets SDK) that achieve the exact same result (potentially with even less code). MSBuild has access to the entire repo infrastructure, including the NetCurrent proprerty and hence those hardcoded entries would go away.
Two powershell scripts currently hardcode the TFM value:
format/eng/format-verifier.ps1
Line 76 in 0b96805
format/eng/perf.ps1
Line 48 in 0b96805
While that wasn't a problem in the past, with now floating TFM versions defined by Arcade (
$(NetCurrent)), the goal is to upgrade repositories to the next version of .NET more easily.Ideally the two scripts would be replaced by simple msbuild projects (using the
Microsoft.Build.NoTargetsSDK) that achieve the exact same result (potentially with even less code). MSBuild has access to the entire repo infrastructure, including theNetCurrentproprerty and hence those hardcoded entries would go away.