Tom Longhurst

When a test run finishes, it's stores it's passed/failed/skipped somewhere via that interface. And when ran again, it does the same and also compares against the previous X records

I think it'd be very useful for a lot of people. Just the question around auto registration since it's need user input (the interface)

Well for instance you currently can install the TRX extension and invoke it via the cli.. you couldn't do that for a flaky test extension if you needed to supply...

Yeah building an extension that can compare data across runs. Like @nohwnd said, you could store it next to the executable, but for thinks like GitHub pipelines, you'd need to...

@copilot also upgrade the pipeline and the project to build for .NET 9

I understand the zero dependency thing, I'm assuming because if your test platform has a dependency, that your system-under-test also has, then you might run into conflicts. It might upgrade...

> If we place Microsoft.Extensions.* dlls under `lib`, NuGet will be considering them to be copied to output directory. So I think this will still have the same issue. Damn!...

You can load two different versions of the same assembly though if they're publicly signed can't you?

I've never used this, but NuGet supports a `/ref` location which isn't copied to the output directory, but IS used by the compiler? https://github.com/NuGet/Home/discussions/11097#discussioncomment-1082474

I understand not wanting to do dynamic assembly loading. But sounds like that could potentially solve this in the cleanest way, by isolating one specific version of a dependency into...