‘ Another possible fix for the serialization/remoting issue.
‘ Has NOT been tested extensively, but appears to work so far.
‘ Place this method in all your custom classes that inherit
‘ from MarshalByRefObject that you intend to serialize.

<Runtime.Serialization.OnSerializing()> _
Private Sub OnSerializing(ByVal context As _
StreamingContext)
Dim MethodInfo As System.Reflection.MethodInfo

‘ Use reflection to access internal
‘ MarshalByRefObject method __ResetServerIdentity.
MethodInfo = Me.GetType.GetMethod _
(”__ResetServerIdentity”, BindingFlags.Instance _
Or BindingFlags.NonPublic)
If MethodInfo IsNot Nothing Then
Try
‘ Calling the __ResetServerIdentity method
‘ will set the remoting identity to Nothing.
MethodInfo.Invoke(Me, Nothing)
Catch ex As Exception
Debug.WriteLine(”ResetServerIdentity failure. ” _
& ex.Message)
End Try
End If

End Sub

I’m not familiar with IMessageFormatter, also if you are not getting the “ServerIdentity not serializable” error than it might not be the same problem, the solution above assumes you are performing your own serialization (i.e. creating the Serializer).
You should pass your ISerializationSurrogate when creating the serializer. Read about ISerializationSurrogate to see how.

Guy.

i’ve come across the serialization & remoting problem when trying to use remoting to send a Message (with a very simple object in the body) to a MessageQueue. The remoting object is published in a windows service as well as the MessageQueue.

The problem arises when trying to send the Message to the MessageQueue using the BinaryMessageFormatter. With the XmlMessageFormatter the windows service just crashes :) (although no exception is generated )

After reading this article my only problem is in the first 3 steps. I can’t figure how to do it.
I’ve created a class that implements IMessageFormatter but i don’t know how to “Set the surrogate in your serialization mechanism to override ServerIdentity’s serialization.”?

Any help will be very much appreciated.
Thank you