@bricelam If that change does go through, I'm not sure that there's much that we can do other than documenting that EFCore.Design should be referenced directly from every project that would be targeted by tools.

Using AssemblyLoadContext (mentioned in #18840) would be an alternative to calling dotnet exec with the project's .deps.json file. This would allow us (Edit: lol, I can't help myself; it just comes out. I mean you guys) to define where it gets loaded from.

We're reverting that PR based on feedback from several partner teams, so 200 shouldn't blow up your expectations. Apologies for the close call, but please in the future yell at us if something we do has inordinate impact on your use cases.

@baronfel Thanks, will do. We thought that we could react to it in a patch to avoid breaking the users, but I only got to it last week and found out that to be able to use AssemblyLoadContext we'd have to update our TFM.

We are still going to make this change for 10 anyway as it should make assembly loading more robust in general. And we already had a user report that presented the same symptoms.