migrate-mstest-v1v2-to-v3
MSTest v1/v2 -> v3 Migration
Migrate a test project from MSTest v1 (assembly references) or MSTest v2 (NuGet 1.x-2.x) to MSTest v3. MSTest v3 is not binary compatible with v1/v2 -- libraries compiled against v1/v2 must be recompiled.
When to Use
- Project references
Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll(MSTest v1) - Project uses
MSTest.TestFramework/MSTest.TestAdapterNuGet 1.x or 2.x - Resolving build errors after updating MSTest packages from v1/v2 to v3
- Replacing
.testsettingswith.runsettings - Adopting MSTest.Sdk or in-assembly parallel execution
When Not to Use
- Project already uses MSTest v3 (3.x packages)
- Upgrading v3 to v4 -- use
migrate-mstest-v3-to-v4 - Migrating between frameworks (MSTest to xUnit/NUnit)
Inputs
More from managedcode/dotnet-skills
dotnet
Primary router skill for broad .NET work. Classify the repo by app model and cross-cutting concern first, then switch to the narrowest matching .NET skill instead of staying at a generic layer.
18dotnet-aspnet-core
Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET.
13dotnet-entity-framework-core
Design, tune, or review EF Core data access with proper modeling, migrations, query translation, performance, and lifetime management for modern .NET applications.
12dotnet-code-review
Review .NET changes for bugs, regressions, architectural drift, missing tests, incorrect async or disposal behavior, and platform-specific pitfalls before you approve or merge them.
11dotnet-architecture
Design or review .NET solution architecture across modular monoliths, clean architecture, vertical slices, microservices, DDD, CQRS, and cloud-native boundaries without over-engineering.
11dotnet-signalr
Implement or review SignalR hubs, streaming, reconnection, transport, and real-time delivery patterns in ASP.NET Core applications.
10