CharliePoole

I've done a PR for the part of this that removes the deprecated packages from our regular build process. More work is needed to change __how__ we deprecate them, but...

@nunit/engine-team This is partly done as planned and I don't intend to do any further work so I'm closing it. Let me know if you see any problem with this.

@ChrisMaddock Did you want to hang onto this one for a bit rather than transfer to vs-project-loader? That's OK with me, if so.

Ah that makes sense! I believe that the package created by the VS Project Loader extension for a solution should set SkipNonTestAssemblies because not doing so generates errors. This needs...

There's a bit of a problem in that `[NonTestAssembly]` may have evolved away from it's original intent. However, since I wrote it, here's what that intent was: 1. Having a...

@nunit/engine-team I hadn't really thought about this before, but maybe part of the problem here is that the definition of `NonTestAssemblyAttribute` is different from what is implied by the console...

@ChrisMaddock Could be... I'll take a look. @DrHardReset Can you provide a simple example that reproduces this? Also, can you check to see if the problem only occurs when running...

@Snuxx As you know, the callbacks come from the framework. The point of the existing engine code, was that the callback was occurring twice, once for the final result and...

I'm inclined to close this issue as being by design. All test-case and test-suite events received from the tests are intended to contain minimal information needed to identify the particular...

@DrHardReset @Snuxx The 3.16 release will come out sometime this month. Pending further information, I will be removing the issue from the milestone as explained in my earlier comment. For...