Replacement for AssemblyResolution in newer .NET versions?

[fx999dev]

To answer more specifically your questions. No, there will not be any "fix" for supporting the AssemblyResolution property in netcore/net versions of MSTest. But we will update the documentation to specify this is not supported AND we will emit a warning if we detect this property in some netcore run.

@Evangelink
We have about 1500 dlls of which 30-50 dlls need to be loaded at runtime depending on the project. via the .runsettings file gave us the possibility to specify a path where all possible runtime components can be found.
Surely we can't specify "Copy Local" on each of our projects, after which around 3 gigabytes of dlls are copied to the binary folder on each build, which would not only be a huge waste of memory, but also a massive performance loss when building the projects.

We are currently still using .NET Framework, but how should we solve the problem when we move to .NET 6.0 in the future?

Originally posted by @fx999dev in #1645 (comment)

AB#1934901

[Evangelink]

Hi @fx999dev! I will need to explore some ways to provide a full answer but my first idea here if your test project requires many depenendencies that are not present at compile time, would be to moving the test assembly/assemblies to the folder with old dependencies this way at runtime all files would be present. I think (need to test it out) you could also update the net6 config file produced by the dll to point to some extra folders.

[Evangelink]

Hi @fx999dev, we will be porting this feature to MSTest v3.3