[dcrazy]

If you want the isolation features of a separate process, you can’t substitute it with a single multithreaded COM server process.

.NET tried this with app domains, which are now deprecated.

[pjmlp]

App Domains were in process, which isn't was I am talking about with outproc COM.

Also App Domains are partially back in .NET Core, isolation features aren't there, but code unloading is, via AssemblyLoadContext.

[dcrazy]

My point is that “just write a COM server” is not an answer to the problem of “I want each work item to be segregated from each other.”