Patric Forsgard

I don't remember why I was setting it to `null` in the first case, but when I upgraded the OpenAPI package it was a change in the behavior that was...

Nice, i will try to use that one. I can say directly that I got no errors :)

Maybe if the `RefAssemblyPaths="@(_ResolveAssemblyReferenceResolvedFiles)"` on the task is changed to a private variable we probably can filter out the netstandard2.0 reference from that one and the IDT001 warning can still...

+1 Why not 'simpleClassAndMethod' that will ignore all namespace parts that are same for all test cases?

@NickCraver no. That route is not so extensible that a format settings. If we look at the aspnet dev guidelines https://github.com/aspnet/Home/wiki/Engineering-guidelines#unit-test-class-naming the test-class should live in the same namespace as...