-
Notifications
You must be signed in to change notification settings - Fork 285
Closed
Labels
Area: MSTestIssues with MSTest that are not specific to more refined area (e.g. analyzers or assertions)Issues with MSTest that are not specific to more refined area (e.g. analyzers or assertions)Breaking ‼️
Milestone
Description
Both test framework and adapter set UseAssemblyVersion14
to true.
testfx/Directory.Build.targets
Lines 10 to 11 in 7b0d5d1
<AssemblyVersion>14.0.0.0</AssemblyVersion> | |
<AssemblyFileVersion>14.0.0.0</AssemblyFileVersion> |
We shouldn't do that anymore, and MSTest assemblies should be properly versioned, similar to MTP assemblies.
This means that in v4, we will have to use a lower version (4.x) instead of 14.x, which may also be problematic that a newer version of the assembly is actually using an older version number. Thus, I also think it's safest to rename the assembly altogether.
- Instead of
Microsoft.VisualStudio.TestPlatform.TestFramework
, we simply useMSTest.TestFramework
- Instead of
Microsoft.VisualStudio.TestPlatform.MSTest.TestAdapter
, we simply useMSTest.TestAdapter
.
NOTE: I'm suspecting that fixing the version to 14.0.0.0 may be causing issues on .NET Framework when dealing with GAC.
Evangelink
Metadata
Metadata
Assignees
Labels
Area: MSTestIssues with MSTest that are not specific to more refined area (e.g. analyzers or assertions)Issues with MSTest that are not specific to more refined area (e.g. analyzers or assertions)Breaking ‼️