This repository is for active development of the Azure SDK for .NET. For consumers of the SDK we recommend visiting our public developer docs at https://learn.microsoft.com/dotnet/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-net.
MIT License
5.47k
stars
4.8k
forks
source link
Re-order TargetFrameworks so default run/test target is latest e.g. net5.0 #24255
The first TFM in <TargetFrameworks> for test projects is what gets used when running tests from the text editor using the little test chevron. If configured for F5 debugging, it also is the one used by default unless you explicitly set the TFM in some scenarios. "net461" was selected as the first because the last one, IIRC, is what gets used for code coverage, and the thought it we'll have more coverage on newer platforms/targets because we support light-up code in some places like Azure.Core and Azure.Security.KeyVault.Keys.
The first TFM also gets used for preproc conditionals, which then get limited (almost none) help from VS:
Instead, we should see if we can use an explicit target for code coverage (warning: when I tried this during the initial code coverage effort, some projects that don't support net461 generate an error and fail a build) so that we can list TFMs from newest to oldest.
heaths
commented
1 year ago
The first TFM in
<TargetFrameworks>for test projects is what gets used when running tests from the text editor using the little test chevron. If configured for F5 debugging, it also is the one used by default unless you explicitly set the TFM in some scenarios. "net461" was selected as the first because the last one, IIRC, is what gets used for code coverage, and the thought it we'll have more coverage on newer platforms/targets because we support light-up code in some places like Azure.Core and Azure.Security.KeyVault.Keys.The first TFM also gets used for preproc conditionals, which then get limited (almost none) help from VS:
Instead, we should see if we can use an explicit target for code coverage (warning: when I tried this during the initial code coverage effort, some projects that don't support net461 generate an error and fail a build) so that we can list TFMs from newest to oldest.
/cc @pakrym