Update dependencies for latest versions. (#89)

Fixes #88

* This updates the version of many dependencies to eliminate vulnerabilities
    - The vulnerability reported ONLY impacts Linux according to the CVE but this package is valid there so it is updated.
* Updated tests to resolve new MSTEST* warnings about not using new methods.
* Updated for vulnerability in dependent MSBUILD package.

Author: smaillet

Directory.Build.targets

@@ -1,6 +1,6 @@
-<Project InitialTargets="VerifyProjectSettings;ShowBuildParameters">
-    <Target Name="EnsureBuildOutputPaths" Condition="!EXISTS($(PackageOutputPath))" BeforeTargets="Build;Restore">
-        <MakeDir Directories="$(PackageOutputPath)"/>
+<Project InitialTargets="VerifyProjectSettings;ShowBuildParameters;EnsureBuildOutputPaths">
+    <Target Name="EnsureBuildOutputPaths">
+        <MakeDir Condition="!EXISTS($(PackageOutputPath))" Directories="$(PackageOutputPath)"/>
     </Target>
 
     <Target Name="ShowBuildParameters">
@@ -41,6 +41,6 @@
         <Error Condition="'$(ImplicitUsings)'!='disable'" Code="REPO001" Text="$(MSBuildProjectFile) - Projects in this repository MUST NOT have ImplicitUsings enabled!"/>
 
         <!--Verify that GeneratedVersion.props exists; and produce a, hopefully, informative message on how to create it if it doesn't -->
-        <Error Condition="!Exists('$(GeneratedVersionProps)')" Code="REPO002" Text="$(GeneratedVersionProps) file does not exist, it must be created by `New-GeneratedBersionProps.ps1` BEFORE building in the IDE for consistent results"/>
+        <Error Condition="!Exists('$(GeneratedVersionProps)')" Code="REPO002" Text="$(GeneratedVersionProps) file does not exist, it must be created by `New-GeneratedVersionProps.ps1` BEFORE building in the IDE for consistent results"/>
     </Target>
 </Project>

Directory.Packages.props

@@ -15,13 +15,13 @@
    -->
   <ItemGroup>
     <PackageVersion Include="Microsoft.Bcl.HashCode" Version="6.0.0" />
-    <PackageVersion Include="Microsoft.Build.Framework" Version="17.14.8" />
-    <PackageVersion Include="Microsoft.Build.Utilities.Core" Version="17.14.8" />
-    <PackageVersion Include="MSBuild.ProjectCreation" Version="14.0.5" />
+    <PackageVersion Include="Microsoft.Build.Framework" Version="17.14.28" />
+    <PackageVersion Include="Microsoft.Build.Utilities.Core" Version="17.14.28" />
+    <PackageVersion Include="MSBuild.ProjectCreation" Version="16.1.0" />
     <!-- Tests all use the same framework versions -->
-    <PackageVersion Include="Microsoft.NET.Test.Sdk" Version="17.14.1" />
-    <PackageVersion Include="MSTest.TestAdapter" Version="3.9.3" />
-    <PackageVersion Include="MSTest.TestFramework" Version="3.9.3" />
+    <PackageVersion Include="Microsoft.NET.Test.Sdk" Version="18.0.0" />
+    <PackageVersion Include="MSTest.TestAdapter" Version="4.0.1" />
+    <PackageVersion Include="MSTest.TestFramework" Version="4.0.1" />
     <PackageVersion Include="PolySharp" Version="1.15.0" />
     <PackageVersion Include="Sprache" Version="2.3.1" />
     <PackageVersion Include="System.Text.RegularExpressions" Version="4.3.1" />

src/Ubiquity.NET.Versioning.Build.Tasks.UT/Support/AssemblyInfo.cs

@@ -8,6 +8,8 @@
 using System.Diagnostics.CodeAnalysis;
 using System.Runtime.InteropServices;
 
+using Microsoft.VisualStudio.TestTools.UnitTesting;
+
 // In SDK-style projects such as this one, several assembly attributes that were historically
 // defined in this file are now automatically added during build and populated with
 // values defined in project properties. For details of which attributes are included
@@ -25,3 +27,10 @@
 
 // Code coverage should not apply to a unit test assembly
 [assembly: ExcludeFromCodeCoverage]
+
+// parallelization causes problems with concurrent builds
+// so it must be disabled. Total test time is still ~15s
+// for the first (No JIT caching of hot path). There is
+// probably a way to resolve this and allow parallel builds
+// or tests but it doesn't currently seem worth it to investigate...
+[assembly: DoNotParallelize]