This is a continuation of the discussion in #56391 which is closed and therefore cannot be commented on.

@jkoritzinsky said:

This is a known limitation with C++/CLI in .NET Core and .NET 5+. If the first time managed code in a C++/CLI assembly is executed is from a native caller, the assembly will be loaded into a separate ALC.

Can we expect this limitation to be removed? This is a major migration blocker for our (native/unmanaged) C++ application that used C++/CLI to implement some of its functionality. C++/CLI dlls are called via the PE import table and LoadLibrary/GetProcAddress and it will be very, very difficult to track down & change all these code paths.

Is there a way to make this customizable via some event, or runtime config? I already "host" the runtime as described here.