fitSharp is not remotable anymore

[schmax]

Since release 1.6 fitSharp isn't remotable anymore. I use .NET-Remoting to execute tests on another machine. This is done by calling SetSystemUnderTest with a remote object in my fixture. Everything worked fine till release 1.5. In 1.6 I get this Exception: "System.Runtime.Serialization.SerializationException: Der Typ fitSharp.Machine.Model.IdentifierName in Assembly fitSharp, Version=1.6.3680.37512, Culture=neutral, PublicKeyToken=null ist nicht als serialisierbar gekennzeichnet." -> German, sorry, means something like "Type ... isn't marked as serializable."
I've tried to fix it myself, but then I got another RemotingException which I was not able to fix.

I'm happy with 1.5 and there is no need to upgrade. I want to report this as a disadvantage of the new releases. Maybe this problem could be fixed easily.

[mlsomers]

My best guess is that it has to do with .Net Core support.
Many things have been thrown overboard with .Net Core (not Fitnesse but Microsoft have thrown them overboard).
Remoting is one of those features, Application domains also are gone and CAS security was already half gone...
What I miss most with .Net Core is the great IIS integration where sessions and load balancing could be handled by Ops instead of Dev...