2.1 KiB
Errata
If you find any mistakes, then please raise an issue in this repository or email me at markjprice (at) gmail.com.
- Page n - Understanding the journey to one .NET and Understanding .NET support
- Page n - Running unit tests using Visual Studio Code
Page n - Understanding the journey to one .NET and Understanding .NET support
Even-numbered .NET releases like .NET 6 and .NET 8 have a support level named Long Term Support (LTS) with a duration of 3 years. Odd-numbered .NET releases like .NET 5 and .NET 7 had a support level named Current with a duration of 18 months.
On June 6, 2022, the .NET team proposed to change the support level name from Current to Short Term Support (STS) to complement the existing Long Term Support (LTS). I updated the drafts of my book to reflect that change.
On October 11, 2022, the .NET team changed the name again, to Standard Support, probably because Microsoft Marketing decided that "short term" sounded too negative. My editors and I scrambled to update the final drafts of my book to reflect that change.
On October 28, 2022, the .NET team changed the name again, to Standard Term Support (STS), probably because an initialism of SS is problematic and internal code and configuration was already using sts. Sadly, it was too late to update the PDFs that are sent to print.
Sigh. Such are the perils of trying to be up-to-date on release day.
Page n - Running unit tests using Visual Studio Code
Thanks to kwatsonkairosmgt for raising this issue on 27 October 2022.
In Step 1, the project name CalculatorLibUnitTest should be CalculatorLibUnitTests.