Problem in MessageQueue

[rbarzallo]

Hi, i have next class : public class abc { public string campo 1; public string campo 2; public Socket CltSckt; public NetWorkStream NS; } After of initialize the class and stored the data for each variable, I wish to send or store in a Queue : public int EscribeCola(string SrvName, string QueueName, abc Msg_Devices) { try { MessageQueue msgq = new MessageQueue(); msgq.Formatter = new XmlMessageFormatter(new Type[] {typeof(string)}); System.Messaging.Message msg = new System.Messaging.Message(); msgq.Path = (SrvName + QueueName); // // coloco el mensaje en la cola lock(this) { msgq.Send(Mensaje_Devices); } msgq.Dispose(); return 0; } catch (Exception ex) { acc_evento.ReportaEvento(PROCESO_ORIGEN,Param_Eventos.PROBLEMA_WRITE_QUEUE, QueueName + " " + ex.Message + " " + ex.InnerException.Message); return -1; } } In the moment of "send", present a runtime error : "There was an error refecting 'Msg_Devices'" "System.net.sockets.socket" "Cannot be serialized because it does not have a default constructor". May you help me? What have I do? Grettings

[Jeff Varszegi]

It's indicating that you can't serialize the Socket object, looks like to me; not only does it not have a default constructor, but it doesn't implement the ISerializable interface isn't marked with the SerializableAttribute attribute. What would be the value in serializing a socket, anyway? You can mark it with the [NonSerialized] attribute to avoid this problem. Regards, Jeff Varszegi EEEP!  An Extensible Expression Evaluation Package

[Heath Stewart]

To note, something doesn't have to implement ISerializable to be serializable - only to be attributed with the SerializableAttribute (not inheritted with the formatters provided in the FCL, as it should be). The interface is just to customize how an object is serialized. You're still right about the Socket class not being serializable, though. I mean, that's just silly! :)

Microsoft MVP, Visual C# My Articles

[Jeff Varszegi]

Whoops, right you are. My Java undies are showing-- in Java the Serializable interface is just a marker interface, with Externalizable the one you implement to provide your own serialization routine. I get mixed up sometimes because some things are so similar in Java and .NET, and I still have to use both at work. I'm getting used to rapidly switching between naming and casing conventions, but the APIs still trip me up occasionally. Thanks for the correction. Regards, Jeff Varszegi EEEP!  An Extensible Expression Evaluation Package

[rbarzallo]

I tried to put [NonSerialized] the class, but show me a compilation error. Please, may you send me an example?

[Jeff Varszegi]

Don't put it on the class, just on the fields you don't want to serialize, like so: public class abc {     public string campo 1;     public string campo 2;     [NonSerialized]     public Socket CltSckt;      public NetWorkStream NS; } Try that and get back to me. -Jeff here, bloggy bloggy