Chris Maddock

Unfortunately this isn't possible yet - the current .NET Standard engine can only run tests in process - so couldn't load a .NET Framework test suite if it was being...

@clydeigc This is probably the best source right now: https://github.com/orgs/nunit/teams/engine-team/discussions/4 I'm going to label this issue up and keep it open, as it's a feature request that isn't tracked anywhere...

Sorry - I thought that page was public. I plan to create the relevant github issues soon, which I guess will serve as a better 'definitive source'. In the meanwhile...

Where is your console coming from at the moment? If you install both console and addins by NuGet, the engine _should_ find the addins automatically already.

Hey @nvborisenko - you've raised a good point. I agree that in your situation there should be an easier way to install extensions. I'm less convinced that searching the test...

> I've always felt this way about referencing the VSTest adapter from a csproj. :D Yes - same! ---- > --extensions-dir maybe? I like the concept and I agree that...

Great! @nvborisenko - does the command line option still work for you, and are you still interested in implementing it? I suggest `--load-extensions` can take an extension assembly, a directory,...

> Would it ever be beneficial to disable the default loading search logic? I can't think of a reason. Me neither. Let's cross that bridge when we come it it....

> You haven't specified what a directory means. I suggest that it should mean the same thing as if you added the directory path to the addins file. That is:...

Ooh, glad to see people interested in this issue - it's something I've wanted to look at for a while! My thoughts: the engine itself provides a simple interface to...