CharliePoole

@manfred-brands I duplicated it from TestCentric/TestCentric.Extensibility#71 using GitHub "Duplicate issue" and then edited it, which took me a while. You may not have seen the updated text, which mentions the...

The background that gave rise to this issue has changed, I think for the better, since TestCentric no longer maintains it's own `TestCentric.Extensibility` package but uses `NUnit.Extensibility`. However, for the...

Further thoughts... Since I mentioned `NUnitLite` above, I started thinking about how that would work. It seems to me that the proposal I have made works for any extension that...

@manfred-brands We're dropping `EngineVersion` so I'm guessing you mean `HostVersion`. It's a good question. I'd say for two reasons... 1. In the past, we have allowed for methods to be...

@manfred-brands Up to now, the host has only called the engine although I envisioned having the engine call the host for some services if it were needed. It could be...

@MaYoT27 It's interesting that it works under the VS adapter, which uses the engine. How do you actually trigger the unpacking? I.E. does the test call something, is an attribute...

@MaYoT27 Can you test using the latest from our myget feed, which is version 3.21.0-alpha.2?

I think that allowing extensions that provide new resolution strategies is a reasonable idea. However, it's probably a bit more than we want to do in the remaining life of...

@MaYoT27 Am I understanding correctly that the "Costura folder" is the same folder that holds your test assemblies and that the dependencies are therefore in the same directory as the...

@MaYoT27 The fact that it passes under the Visual Studio is likely due to one of two factors: 1. Visual Studio already has created a process and loaded all assemblies...