CharliePoole

Verified that the problem still exists in 3.15.

Minor thing: I'd add "or any other API assemblies we decide we need."

We've made the basic decision: only API methods are guaranteed to remain stable. It remains to make current public methods internal or otherwise inaccessible to the greatest extent possible.

Having an API assembly does a few things... 1. You can modify the implementation under that API. 2. You can allow other people to replace all or part of the...

All sorts of ifs and and buts exist and would have to be taken care of in the design. I'd say let's wait till we can actually deal with it....

Could it relate to the fact that the code that applies the transform targets .NET 2.0 and uses the 2.0 libraries?

@ChrisMaddock Have you considered just adding a second extension in the same assembly? It would only take a few lines of code and you could refactor so that the new...

@ChrisMaddock Should we treat this as a console problem or an nunit-transforms problem? If it once worked and the console changed at some point, then I'd say fix it in...

TLDR; After some review, I think the problem is the transform rather than nunit3-console -or maybe just the documentation for the html transforms. If possible, I should just fix the...

NUnit will never produce more than one test-run element, so that's not an issue unless you concatenate files. The use of match="/" was intended to deal with situations where there...