Just for the record, I mean write it in a C# class and load that one class
so you can handle everything in C# itself - much more robust.
On Tue, 13 Feb 2018 at 19:04, R Zaghi wrote:
> If this is actually a problem with a library like mono then it sounds like
> a caching
If this is actually a problem with a library like mono then it sounds like
a caching problem. If you build mono from source then it's easier to look
into this...
Compare your code with this example. In the example, the .dll assembly is
re-loaded in a loop. You can see the clean up portion and the