Geek Answers Handbook

Best Practice How to Isolate Dynamic Code / Assemblies Using .net CORE

With .NET 4.5, I created an extensible web application. With execution during execution of the certified code from third parties.

For this, I use application domains and inter-process communication.

Now I saw that many of the technologies that I used for this are no longer supported in the .NET core

as:

  • Appdomains
  • Remoting
  • BinarySerzializers

For most of them, there are obvious solutions. But removing AppDomains is not an easy thing.

If I understand correctly, I must use processes. But if my application has about 100 extensions (multiple clients)? This would mean that I would have to create 100 processes (microservices), or at least group them in microservices.

But I do not feel very comfortable with any. In one case, I would get hundreds of processes. And if I group, I can still get an influence between them.

So what would be the right choice?

+5
source share
1 answer

One possible solution would be to use AssemblyLoadContext instead of AppDomains.

This is not a direct replacement for AppDomains and the isolation level that gives you, but it can be good enough for your needs - it allows you to use the equivalent of AppDomain.LoadFile and AppDomain.ResolveEvent to give you assembly load isolation.

There is currently no real documentation, but there is a problem for this: https://github.com/dotnet/coreclr/issues/5463 p>

+2
source

More articles:


All Articles