By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,106 Members | 2,686 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,106 IT Pros & Developers. It's quick & easy.

How to prevent base class (UserControl) form being serialized

P: n/a
I have a class that is a control derived from UserControl. I want to use
serialization and deserialization with this calss but I get an exception
"Cannot serialize member System.ComponentModel.Component.Site of type
System.ComponentModel.ISite because it is an interface.".

I am not interested in serializing any member from the base class only the
properties in the derived class.

How can I prevent the entire base class from being serialized?
Code snippet

public partial class UserControl1 : UserControl
{
private int item1;
private string item2;
public UserControl1()
{

}

public int Item1
{
get {return item1;}
set {item1 = value;}
}

public string Item2
{
get { return item2; }
set { item2 = value; }
}
}
public partial class Form1 : Form
{
private UserControl1 Uctrl1;
Feb 6 '06 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Well, I doubt that you can. There are attributes that will let you
determine what can and cannot be serialized, but you would have to place
them on the code for the UserControl.

Now, let's step back for a moment and talk about design. I imaging you want
to serialize your control so that you can persist it and then reload it at
some later time with a complete state. The base UserControl is part of your
derived control and it would not make sense to reinitialize only your
derived control while leaving the base class un-touched. My suggestion
would be to create a data structure that maintain a copy of all the
information in your control, for instance, if you had name, address, and
phone number, you then might have the following structure.

public struct Person{
Public Name;
Public Address;
Public PhoneNumber;
}

The design principle here is that you decouple the data from the
presentation. That way you can do what you want with the data (store it or
move it as needed) then when you need to reload your control, you simply
initialize the fields with this data. Just serialize this structure rather
than worrying about the whole control.
"EqDev" <eq***@newsgroups.nospam> wrote in message
news:89**********************************@microsof t.com...
I have a class that is a control derived from UserControl. I want to use
serialization and deserialization with this calss but I get an exception
"Cannot serialize member System.ComponentModel.Component.Site of type
System.ComponentModel.ISite because it is an interface.".

I am not interested in serializing any member from the base class only the
properties in the derived class.

How can I prevent the entire base class from being serialized?
Code snippet

public partial class UserControl1 : UserControl
{
private int item1;
private string item2;
public UserControl1()
{

}

public int Item1
{
get {return item1;}
set {item1 = value;}
}

public string Item2
{
get { return item2; }
set { item2 = value; }
}
}
public partial class Form1 : Form
{
private UserControl1 Uctrl1;
.
.
.
Uctrl1 = new UserControl1();
Uctrl1.Item1 = 3;
Uctrl1.Item2 = "This is a test";

.
.
.
// error on line below
XmlSerializer mySerializer = new XmlSerializer(typeof(UserControl1));
// To write to a file, create a StreamWriter object.
StreamWriter myWriter = new StreamWriter("myFileName.xml");
mySerializer.Serialize(myWriter, Uctrl1);
myWriter.Close();
}
Reposted with proper MSDN alias
--
EqDev

Feb 6 '06 #2

P: n/a
Thanks for the reply.

Ok I get that, but the idea is serializing all public members of an object.
My object happens to be derived from a control so I am penalizes for that.
This makes for more work for maintenance of the code for the object. If I
add public assessors now I must also maintain a struct as well. I was hoping
that there was some way via attributes to force the serializer to ignore the
base class.

--
EqDev
"Peter Rilling" wrote:
Well, I doubt that you can. There are attributes that will let you
determine what can and cannot be serialized, but you would have to place
them on the code for the UserControl.

Now, let's step back for a moment and talk about design. I imaging you want
to serialize your control so that you can persist it and then reload it at
some later time with a complete state. The base UserControl is part of your
derived control and it would not make sense to reinitialize only your
derived control while leaving the base class un-touched. My suggestion
would be to create a data structure that maintain a copy of all the
information in your control, for instance, if you had name, address, and
phone number, you then might have the following structure.

public struct Person{
Public Name;
Public Address;
Public PhoneNumber;
}

The design principle here is that you decouple the data from the
presentation. That way you can do what you want with the data (store it or
move it as needed) then when you need to reload your control, you simply
initialize the fields with this data. Just serialize this structure rather
than worrying about the whole control.
"EqDev" <eq***@newsgroups.nospam> wrote in message
news:89**********************************@microsof t.com...
I have a class that is a control derived from UserControl. I want to use
serialization and deserialization with this calss but I get an exception
"Cannot serialize member System.ComponentModel.Component.Site of type
System.ComponentModel.ISite because it is an interface.".

I am not interested in serializing any member from the base class only the
properties in the derived class.

How can I prevent the entire base class from being serialized?
Code snippet

public partial class UserControl1 : UserControl
{
private int item1;
private string item2;
public UserControl1()
{

}

public int Item1
{
get {return item1;}
set {item1 = value;}
}

public string Item2
{
get { return item2; }
set { item2 = value; }
}
}
public partial class Form1 : Form
{
private UserControl1 Uctrl1;
.
.
.
Uctrl1 = new UserControl1();
Uctrl1.Item1 = 3;
Uctrl1.Item2 = "This is a test";

.
.
.
// error on line below
XmlSerializer mySerializer = new XmlSerializer(typeof(UserControl1));
// To write to a file, create a StreamWriter object.
StreamWriter myWriter = new StreamWriter("myFileName.xml");
mySerializer.Serialize(myWriter, Uctrl1);
myWriter.Close();
}
Reposted with proper MSDN alias
--
EqDev


Feb 6 '06 #3

P: n/a
If it was possible, what happens when you de-serialize? It is also ignore
the base class so your control won't have a name, know its visibility, know
what parent container owns it, location, etc.

"EqDev" <eq***@newsgroups.nospam> wrote in message
news:13**********************************@microsof t.com...
Thanks for the reply.

Ok I get that, but the idea is serializing all public members of an
object.
My object happens to be derived from a control so I am penalizes for that.
This makes for more work for maintenance of the code for the object. If I
add public assessors now I must also maintain a struct as well. I was
hoping
that there was some way via attributes to force the serializer to ignore
the
base class.

--
EqDev
"Peter Rilling" wrote:
Well, I doubt that you can. There are attributes that will let you
determine what can and cannot be serialized, but you would have to place
them on the code for the UserControl.

Now, let's step back for a moment and talk about design. I imaging you
want
to serialize your control so that you can persist it and then reload it
at
some later time with a complete state. The base UserControl is part of
your
derived control and it would not make sense to reinitialize only your
derived control while leaving the base class un-touched. My suggestion
would be to create a data structure that maintain a copy of all the
information in your control, for instance, if you had name, address, and
phone number, you then might have the following structure.

public struct Person{
Public Name;
Public Address;
Public PhoneNumber;
}

The design principle here is that you decouple the data from the
presentation. That way you can do what you want with the data (store it
or
move it as needed) then when you need to reload your control, you simply
initialize the fields with this data. Just serialize this structure
rather
than worrying about the whole control.
"EqDev" <eq***@newsgroups.nospam> wrote in message
news:89**********************************@microsof t.com...
>I have a class that is a control derived from UserControl. I want to
>use
> serialization and deserialization with this calss but I get an
> exception
> "Cannot serialize member System.ComponentModel.Component.Site of type
> System.ComponentModel.ISite because it is an interface.".
>
> I am not interested in serializing any member from the base class only
> the
> properties in the derived class.
>
> How can I prevent the entire base class from being serialized?
>
>
> Code snippet
>
> public partial class UserControl1 : UserControl
> {
> private int item1;
> private string item2;
>
>
> public UserControl1()
> {
>
> }
>
> public int Item1
> {
> get {return item1;}
> set {item1 = value;}
> }
>
> public string Item2
> {
> get { return item2; }
> set { item2 = value; }
> }
> }
>
>
> public partial class Form1 : Form
> {
> private UserControl1 Uctrl1;
> .
> .
> .
> Uctrl1 = new UserControl1();
> Uctrl1.Item1 = 3;
> Uctrl1.Item2 = "This is a test";
>
> .
> .
> .
> // error on line below
> XmlSerializer mySerializer = new
> XmlSerializer(typeof(UserControl1));
> // To write to a file, create a StreamWriter object.
> StreamWriter myWriter = new StreamWriter("myFileName.xml");
> mySerializer.Serialize(myWriter, Uctrl1);
> myWriter.Close();
> }
>
>
> Reposted with proper MSDN alias
> --
> EqDev


Feb 6 '06 #4

P: n/a
Yes, but in the ideal situation you would have control over what is and is
not serialized.

Does anyone from MS have a suggestion on this?
Is there a way in .NET 2.0 to deal with this issue?

--
EqDev
"Peter Rilling" wrote:
If it was possible, what happens when you de-serialize? It is also ignore
the base class so your control won't have a name, know its visibility, know
what parent container owns it, location, etc.

"EqDev" <eq***@newsgroups.nospam> wrote in message
news:13**********************************@microsof t.com...
Thanks for the reply.

Ok I get that, but the idea is serializing all public members of an
object.
My object happens to be derived from a control so I am penalizes for that.
This makes for more work for maintenance of the code for the object. If I
add public assessors now I must also maintain a struct as well. I was
hoping
that there was some way via attributes to force the serializer to ignore
the
base class.

--
EqDev
"Peter Rilling" wrote:
Well, I doubt that you can. There are attributes that will let you
determine what can and cannot be serialized, but you would have to place
them on the code for the UserControl.

Now, let's step back for a moment and talk about design. I imaging you
want
to serialize your control so that you can persist it and then reload it
at
some later time with a complete state. The base UserControl is part of
your
derived control and it would not make sense to reinitialize only your
derived control while leaving the base class un-touched. My suggestion
would be to create a data structure that maintain a copy of all the
information in your control, for instance, if you had name, address, and
phone number, you then might have the following structure.

public struct Person{
Public Name;
Public Address;
Public PhoneNumber;
}

The design principle here is that you decouple the data from the
presentation. That way you can do what you want with the data (store it
or
move it as needed) then when you need to reload your control, you simply
initialize the fields with this data. Just serialize this structure
rather
than worrying about the whole control.
"EqDev" <eq***@newsgroups.nospam> wrote in message
news:89**********************************@microsof t.com...
>I have a class that is a control derived from UserControl. I want to
>use
> serialization and deserialization with this calss but I get an
> exception
> "Cannot serialize member System.ComponentModel.Component.Site of type
> System.ComponentModel.ISite because it is an interface.".
>
> I am not interested in serializing any member from the base class only
> the
> properties in the derived class.
>
> How can I prevent the entire base class from being serialized?
>
>
> Code snippet
>
> public partial class UserControl1 : UserControl
> {
> private int item1;
> private string item2;
>
>
> public UserControl1()
> {
>
> }
>
> public int Item1
> {
> get {return item1;}
> set {item1 = value;}
> }
>
> public string Item2
> {
> get { return item2; }
> set { item2 = value; }
> }
> }
>
>
> public partial class Form1 : Form
> {
> private UserControl1 Uctrl1;
> .
> .
> .
> Uctrl1 = new UserControl1();
> Uctrl1.Item1 = 3;
> Uctrl1.Item2 = "This is a test";
>
> .
> .
> .
> // error on line below
> XmlSerializer mySerializer = new
> XmlSerializer(typeof(UserControl1));
> // To write to a file, create a StreamWriter object.
> StreamWriter myWriter = new StreamWriter("myFileName.xml");
> mySerializer.Serialize(myWriter, Uctrl1);
> myWriter.Close();
> }
>
>
> Reposted with proper MSDN alias
> --
> EqDev


Feb 7 '06 #5

P: n/a
Hi EqDev,
Welcome to MSDN Newsgroup!

Based on object model, when a class derived from other class, base class's
content will be involved in child class. So there is currently no way to do
this, but I will also forward this issue to the relevant team. If there is
any information later, I will inform of you as soon as possible. Thanks for
your understanding. Have a nice day!

Best Regards,

Terry Fei [MSFT]
Microsoft Community Support
Get Secure! www.microsoft.com/security

--------------------
Thread-Topic: How to prevent base class (UserControl) form being serialized
thread-index: AcYr357YOeoId7sFR96a2R1fkmd/+g==
X-WBNR-Posting-Host: 24.249.212.34
From: "=?Utf-8?B?RXFEZXY=?=" <eq***@newsgroups.nospam>
References: <89**********************************@microsoft.co m> <um**************@TK2MSFTNGP12.phx.gbl>
<13**********************************@microsoft.co m>
<OC**************@TK2MSFTNGP15.phx.gbl>Subject: Re: How to prevent base class (UserControl) form being serialized
Date: Tue, 7 Feb 2006 04:11:27 -0800
Lines: 142
Message-ID: <52**********************************@microsoft.co m>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.general
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.dotnet.general:188179
X-Tomcat-NG: microsoft.public.dotnet.general

Yes, but in the ideal situation you would have control over what is and is
not serialized.

Does anyone from MS have a suggestion on this?
Is there a way in .NET 2.0 to deal with this issue?

--
EqDev
"Peter Rilling" wrote:
If it was possible, what happens when you de-serialize? It is also ignore the base class so your control won't have a name, know its visibility, know what parent container owns it, location, etc.

"EqDev" <eq***@newsgroups.nospam> wrote in message
news:13**********************************@microsof t.com...
> Thanks for the reply.
>
> Ok I get that, but the idea is serializing all public members of an
> object.
> My object happens to be derived from a control so I am penalizes for that. > This makes for more work for maintenance of the code for the object. If I > add public assessors now I must also maintain a struct as well. I was
> hoping
> that there was some way via attributes to force the serializer to ignore > the
> base class.
>
> --
> EqDev
>
>
> "Peter Rilling" wrote:
>
>> Well, I doubt that you can. There are attributes that will let you
>> determine what can and cannot be serialized, but you would have to place >> them on the code for the UserControl.
>>
>> Now, let's step back for a moment and talk about design. I imaging you >> want
>> to serialize your control so that you can persist it and then reload it >> at
>> some later time with a complete state. The base UserControl is part of >> your
>> derived control and it would not make sense to reinitialize only your
>> derived control while leaving the base class un-touched. My suggestion >> would be to create a data structure that maintain a copy of all the
>> information in your control, for instance, if you had name, address, and >> phone number, you then might have the following structure.
>>
>> public struct Person{
>> Public Name;
>> Public Address;
>> Public PhoneNumber;
>> }
>>
>> The design principle here is that you decouple the data from the
>> presentation. That way you can do what you want with the data (store it >> or
>> move it as needed) then when you need to reload your control, you simply >> initialize the fields with this data. Just serialize this structure
>> rather
>> than worrying about the whole control.
>>
>>
>> "EqDev" <eq***@newsgroups.nospam> wrote in message
>> news:89**********************************@microsof t.com...
>> >I have a class that is a control derived from UserControl. I want to >> >use
>> > serialization and deserialization with this calss but I get an
>> > exception
>> > "Cannot serialize member System.ComponentModel.Component.Site of type >> > System.ComponentModel.ISite because it is an interface.".
>> >
>> > I am not interested in serializing any member from the base class only >> > the
>> > properties in the derived class.
>> >
>> > How can I prevent the entire base class from being serialized?
>> >
>> >
>> > Code snippet
>> >
>> > public partial class UserControl1 : UserControl
>> > {
>> > private int item1;
>> > private string item2;
>> >
>> >
>> > public UserControl1()
>> > {
>> >
>> > }
>> >
>> > public int Item1
>> > {
>> > get {return item1;}
>> > set {item1 = value;}
>> > }
>> >
>> > public string Item2
>> > {
>> > get { return item2; }
>> > set { item2 = value; }
>> > }
>> > }
>> >
>> >
>> > public partial class Form1 : Form
>> > {
>> > private UserControl1 Uctrl1;
>> > .
>> > .
>> > .
>> > Uctrl1 = new UserControl1();
>> > Uctrl1.Item1 = 3;
>> > Uctrl1.Item2 = "This is a test";
>> >
>> > .
>> > .
>> > .
>> > // error on line below
>> > XmlSerializer mySerializer = new
>> > XmlSerializer(typeof(UserControl1));
>> > // To write to a file, create a StreamWriter object.
>> > StreamWriter myWriter = new StreamWriter("myFileName.xml");
>> > mySerializer.Serialize(myWriter, Uctrl1);
>> > myWriter.Close();
>> > }
>> >
>> >
>> > Reposted with proper MSDN alias
>> > --
>> > EqDev
>>
>>
>>



Feb 10 '06 #6

This discussion thread is closed

Replies have been disabled for this discussion.