Prior to AspNetCore 6, MyTested was compatible with Microsoft.AspNetCore.Mvc.Versioning. This integration is via the MyTested.AspNetCore.Mvc.Versioning plugin.
However, beginning with AspNetCore 6, Microsoft.AspNetCore.Mvc.Versioning became a deprecated project, replaced by Asp.Versioning.Mvc. MyTested.AspNetCore.Mvc.Versioning has remained with the old package, stuck at v5.1, while the rest of the suite has moved forward with AspNetCore v6+ packages.
The plugin cannot be simply swapped out from Microsoft.AspNetCore.Mvc.Versioning v5.1 to Asp.Versioning.Mvc vCurrent, as Asp.Versioning.Mvc uses Endpoint middleware rather than older Action Selectors, so it may require implementation of #293 and #351 in order for this support to happen.
Currently, because Asp.Versioning.Mvc is not supported, MyTested routing and pipeline tests return the result of an exception for ambiguous matches: Multiple actions matched. The following actions matched route data and had all constraints satisfied...
Prior to AspNetCore 6, MyTested was compatible with Microsoft.AspNetCore.Mvc.Versioning. This integration is via the
MyTested.AspNetCore.Mvc.Versioningplugin.However, beginning with AspNetCore 6,
Microsoft.AspNetCore.Mvc.Versioningbecame a deprecated project, replaced by Asp.Versioning.Mvc.MyTested.AspNetCore.Mvc.Versioninghas remained with the old package, stuck at v5.1, while the rest of the suite has moved forward with AspNetCore v6+ packages.The plugin cannot be simply swapped out from
Microsoft.AspNetCore.Mvc.Versioningv5.1 toAsp.Versioning.MvcvCurrent, asAsp.Versioning.Mvcuses Endpoint middleware rather than older Action Selectors, so it may require implementation of #293 and #351 in order for this support to happen.Currently, because
Asp.Versioning.Mvcis not supported, MyTested routing and pipeline tests return the result of an exception for ambiguous matches:Multiple actions matched. The following actions matched route data and had all constraints satisfied...