ok, you are on the latest version and .net2 is probably the best build for MT.
The exception is not the most useful as it doesn’t really point to exactly where the problem is caused. That’s the joy of mono, sometimes you just get to guess
There is only really one place we use reflection in the library and that is to auto detect available serialisers and data processors. We already catch some exception cases and default to an older, less efficient method in those cases. We didn’t add a global catch all as we were interested to know what other failure modes we had not found. This may be one of them.
I have added a new catch for ‘MissingMethodException’ and uploaded a beta DLL which you can tryout from https://networkcomms.net/downloads/NetworkCommsDotNet_v2.2.1_Beta_Net2CompleteDLL.zip.
If this solves the problem I will include it with the release of 2.2.1 so let me know how you get on.
If you continue to have issues or other questions just let us know and we’ll do our best to sort them.