Basic class constructor and serialization

[Amadrias]

Hi all,

I am using a class to transport some data over the
network. I then added the [Serializable] attribute to the
class.

My problem is that this class is part of a framework and
that I do not want developers to call empty constructors.
But the runtime sends me an exception when I try to
serialize this class asking me to provide it with an
empty constructor such as:

public MyClass(){}

Is there a way to avoid that problem knowing that using
the ISerializable interface, it stills ask me to
implement an empty constructor?

Thanks for the help.

Amadrias

[Jay B. Harlow [MVP - Outlook]]

Amadrias,

- XML for clear object transportation over the network Are you using the SOAP Formatter (SoapFormatter) or the Xml Serializer
(XmlSerializer) directly? Or are you staying above that level and letting
the Framework do the XMl serialization (via a WebMethod for example)?
- Binary for file serialization. Binary serialization fully supports private default constructors and private
ISerializable constructors. I use private and protected ISerializable
constructors in one of my projects!

Can you post a 'complete' small example of your code that is failing?

Hope this helps
Jay

"Amadrias" <am******@wanad oo.fr> wrote in message
news:08******** *************** *****@phx.gbl.. . Thanks jay,

I am doing both serialization:
- XML for clear object transportation over the network
- Binary for file serialization.

Amadrias

<<snip>>

[Amadrias]

Thanks Jay,

I found the answer.

It seems that the private empty constructor do not work
for a reason I can not explain as I am replicating some
examples I found on the web.

But it works perfectly with the ISerializable
implementation with the associated constructor with a
SerializationIn fo and StreamingContex t parameter.

I really thank you for the time you spent with me on the
problem.

Cordially,

Amadrias

-----Original Message-----
Amadrias,

- XML for clear object transportation over the networkAre you using the SOAP Formatter (SoapFormatter) or the

Xml Serializer(XmlSerializer ) directly? Or are you staying above that level and lettingthe Framework do the XMl serialization (via a WebMethod for example)?

- Binary for file serialization.Binary serialization fully supports private default

constructors and privateISerializabl e constructors. I use private and protected ISerializableconstructors in one of my projects!

Can you post a 'complete' small example of your code that is failing?
Hope this helps
Jay

"Amadrias" <am******@wanad oo.fr> wrote in message
news:08******* *************** ******@phx.gbl. ..

Thanks jay,

I am doing both serialization:
- XML for clear object transportation over the network
- Binary for file serialization.

Amadrias

<<snip>>
.