CharliePoole

This just came up in #1333.

@rprouse I see you have made this a documentation issue. However, the missing packages could still be added to the GitHub release by building locally from the 3.16.3 tag and...

@OsirisTerje @vytasilj @Vemahk It's pretty trivial to create the zip from a nuget install. The directory structure is almost the same. It could be done on the fly by TeamCity,...

@mikkelbu Oh no... you should come and seem me! :wink:

@OsirisTerje The tasks are run on every AppVeyor build but can also be run manuallly. However, they don't always do anything because they check the name of the branch. Draft...

@OsirisTerje Version 3.1.0 of `Microsoft.Extensions.DependencyModel` was the latest one I was able to make work under .NET Core 3.1, which is the latest build used by `nunit.engine.core`. My plan was...

@manfred-brands It would be possible, of course, to stop supporting running under runtimes which have reached microsoft eol. That wasn't our policy in the past, although some have argued it...

@OsirisTerje It was added to support loading packae dependencies when using the engine under runners other than the VS adapter. The adapter, of course, has no need for that, since...

@OsirisTerje I'll jump in with my 2 cents worth here. :-) When I added the dependency model, and other code around it, I also added package tests, which failed without...

@estrizhok The int value of `Default` is 0, which results in an uninitialized `InternalTraceLevel` always being set as `Default`. The intention in doing it this way is that each runner...