Using XmlRootAttribut e for deserialization

[Keith Patrick]

I've seen this come up before, but in my case, things are a little more
complex, and I'm having a tough time figuring out how to set an element name
that works. I have a configuration file that is my serialized object (I'm
using a customer deserializer to add some more XAML-like capabilities):
<AppConfigObjec t>
<RuntimeType:Ke rnel xmlns:RuntimeTy pe="MyNamespace .DefaultKernel, Kernel"/>
</AppConfigObject >

public class AppConfigObject {
[XmlElement]
public Kernel {...}
}

Problem I have is deserializing the child node <Kernel> because it always
throws an error about "<Kernel xmlns='MyNamesp ace.DefaultKern el, Kernel'>
was not expected.". I'm hoping that it's just something I'm missing (I've
tried several combinations of element names and defaultNamespac es) and it's
not that what I am trying is not possible.

[Christoph Schittko [MVP]]

Your XML document states that the <Kernel> element belongs to the
"MyNamespace.De faultKernel, Kernel" namespace, but your serialization
attribute does not declare the namespace.

Try:

public class AppConfigObject {
[XmlElement(Name space="MyNamesp ace.DefaultKern el, Kernel")]
public Kernel {...}
}

--
HTH
Christoph Schittko [MVP]
Software Architect, .NET Mentor

"Keith Patrick" <ri************ *******@nospamh otmail.com> wrote in message
news:uK******** ********@TK2MSF TNGP11.phx.gbl. ..

I've seen this come up before, but in my case, things are a little more
complex, and I'm having a tough time figuring out how to set an element
name
that works. I have a configuration file that is my serialized object (I'm
using a customer deserializer to add some more XAML-like capabilities):
<AppConfigObjec t>
<RuntimeType:Ke rnel xmlns:RuntimeTy pe="MyNamespace .DefaultKernel,
Kernel"/>
</AppConfigObject >

public class AppConfigObject {
[XmlElement]
public Kernel {...}
}

Problem I have is deserializing the child node <Kernel> because it always
throws an error about "<Kernel xmlns='MyNamesp ace.DefaultKern el, Kernel'>
was not expected.". I'm hoping that it's just something I'm missing (I've
tried several combinations of element names and defaultNamespac es) and
it's
not that what I am trying is not possible.

[Christoph Schittko [MVP]]

Your XML document states that the <Kernel> element belongs to the
"MyNamespace.De faultKernel, Kernel" namespace, but your serialization
attribute does not declare the namespace.

Try:

public class AppConfigObject {
[XmlElement(Name space="MyNamesp ace.DefaultKern el, Kernel")]
public Kernel {...}
}

--
HTH
Christoph Schittko [MVP]
Software Architect, .NET Mentor

"Keith Patrick" <ri************ *******@nospamh otmail.com> wrote in message
news:uK******** ********@TK2MSF TNGP11.phx.gbl. ..

I've seen this come up before, but in my case, things are a little more
complex, and I'm having a tough time figuring out how to set an element
name
that works. I have a configuration file that is my serialized object (I'm
using a customer deserializer to add some more XAML-like capabilities):
<AppConfigObjec t>
<RuntimeType:Ke rnel xmlns:RuntimeTy pe="MyNamespace .DefaultKernel,
Kernel"/>
</AppConfigObject >

public class AppConfigObject {
[XmlElement]
public Kernel {...}
}

Problem I have is deserializing the child node <Kernel> because it always
throws an error about "<Kernel xmlns='MyNamesp ace.DefaultKern el, Kernel'>
was not expected.". I'm hoping that it's just something I'm missing (I've
tried several combinations of element names and defaultNamespac es) and
it's
not that what I am trying is not possible.

[Keith Patrick]

The thing is, I can't set it like that in the class, because the Kernel
property is of type "BaseKernel ", of which "DefaultKer nel" is a subclass
(this is basically a new serializer that supports concrete implementations
of abstract properties and list items). I tried also setting
defaultNamespac e in my serializer, but the problem there is that I need to
set defautlNamespac e *and* default element name in teh XmlRootAttribut e,but
I can't set both without also having to provide some other params (the last
ctor for that attribute) that I cannot pass in as null, as it throws an
exception in XRA.

The way I think I am going to go is to declare my stuff like this:
<AppConfigObjec t>
<Kernel>
<MyNamespace.De faultKernel Name="..." Attr2="..."/>
</Kernel>
</AppConfigObject >

and just go through every assembly in the appdomain to look for
MyNamespace.Def aultKernel (it's a somewhat slow process, as it's heavy into
reflection and has to iterate through several assemblies, but this stuff is
all part of startup and not regular operation. Another downside is that I
can't have two assemblies in the appdomain with the same namespace + class,
but I can live with that limitation until I replace the config format with
XAML snippets)

"Christoph Schittko [MVP]" <ch************ ********@austin .rr.com> wrote in
message news:O9******** ******@TK2MSFTN GP11.phx.gbl...

Your XML document states that the <Kernel> element belongs to the
"MyNamespace.De faultKernel, Kernel" namespace, but your serialization
attribute does not declare the namespace.

Try:

public class AppConfigObject {
[XmlElement(Name space="MyNamesp ace.DefaultKern el, Kernel")]
public Kernel {...}
}

--
HTH
Christoph Schittko [MVP]
Software Architect, .NET Mentor

"Keith Patrick" <ri************ *******@nospamh otmail.com> wrote in message
news:uK******** ********@TK2MSF TNGP11.phx.gbl. ..

I've seen this come up before, but in my case, things are a little more
complex, and I'm having a tough time figuring out how to set an element
name
that works. I have a configuration file that is my serialized object (I'm using a customer deserializer to add some more XAML-like capabilities):
<AppConfigObjec t>
<RuntimeType:Ke rnel xmlns:RuntimeTy pe="MyNamespace .DefaultKernel,
Kernel"/>
</AppConfigObject >

public class AppConfigObject {
[XmlElement]
public Kernel {...}
}

Problem I have is deserializing the child node <Kernel> because it always throws an error about "<Kernel xmlns='MyNamesp ace.DefaultKern el, Kernel'> was not expected.". I'm hoping that it's just something I'm missing (I've tried several combinations of element names and defaultNamespac es) and
it's
not that what I am trying is not possible.

[Keith Patrick]

The thing is, I can't set it like that in the class, because the Kernel
property is of type "BaseKernel ", of which "DefaultKer nel" is a subclass
(this is basically a new serializer that supports concrete implementations
of abstract properties and list items). I tried also setting
defaultNamespac e in my serializer, but the problem there is that I need to
set defautlNamespac e *and* default element name in teh XmlRootAttribut e,but
I can't set both without also having to provide some other params (the last
ctor for that attribute) that I cannot pass in as null, as it throws an
exception in XRA.

The way I think I am going to go is to declare my stuff like this:
<AppConfigObjec t>
<Kernel>
<MyNamespace.De faultKernel Name="..." Attr2="..."/>
</Kernel>
</AppConfigObject >

and just go through every assembly in the appdomain to look for
MyNamespace.Def aultKernel (it's a somewhat slow process, as it's heavy into
reflection and has to iterate through several assemblies, but this stuff is
all part of startup and not regular operation. Another downside is that I
can't have two assemblies in the appdomain with the same namespace + class,
but I can live with that limitation until I replace the config format with
XAML snippets)

"Christoph Schittko [MVP]" <ch************ ********@austin .rr.com> wrote in
message news:O9******** ******@TK2MSFTN GP11.phx.gbl...

Your XML document states that the <Kernel> element belongs to the
"MyNamespace.De faultKernel, Kernel" namespace, but your serialization
attribute does not declare the namespace.

Try:

public class AppConfigObject {
[XmlElement(Name space="MyNamesp ace.DefaultKern el, Kernel")]
public Kernel {...}
}

--
HTH
Christoph Schittko [MVP]
Software Architect, .NET Mentor

"Keith Patrick" <ri************ *******@nospamh otmail.com> wrote in message
news:uK******** ********@TK2MSF TNGP11.phx.gbl. ..

I've seen this come up before, but in my case, things are a little more
complex, and I'm having a tough time figuring out how to set an element
name
that works. I have a configuration file that is my serialized object (I'm using a customer deserializer to add some more XAML-like capabilities):
<AppConfigObjec t>
<RuntimeType:Ke rnel xmlns:RuntimeTy pe="MyNamespace .DefaultKernel,
Kernel"/>
</AppConfigObject >

public class AppConfigObject {
[XmlElement]
public Kernel {...}
}

Problem I have is deserializing the child node <Kernel> because it always throws an error about "<Kernel xmlns='MyNamesp ace.DefaultKern el, Kernel'> was not expected.". I'm hoping that it's just something I'm missing (I've tried several combinations of element names and defaultNamespac es) and
it's
not that what I am trying is not possible.

[Keith Patrick]

I dunno what I was thinking with that ctor stuff. I can set the namespace
independently, and it works (at least without the Runtime: stuff):

<Kernel xmlns="MyNamesp ace.DefaultKern el, Kernel"/>
will deserialize just fine as long as my XmlRootAttribut e has a name of
"Kernel" and a namespace of "MyNamespace.De faultKernel, Kernel", which is
basically a non-metadata way of doing what you suggested. Thanks for
steering me in the right direction

[Keith Patrick]

I dunno what I was thinking with that ctor stuff. I can set the namespace
independently, and it works (at least without the Runtime: stuff):

<Kernel xmlns="MyNamesp ace.DefaultKern el, Kernel"/>
will deserialize just fine as long as my XmlRootAttribut e has a name of
"Kernel" and a namespace of "MyNamespace.De faultKernel, Kernel", which is
basically a non-metadata way of doing what you suggested. Thanks for
steering me in the right direction

[Christoph Schittko [MVP]]

Would attaching multiple XmlElement attributes to the property work better
for you? Something like:

public class AppConfigObject {
[XmlElement(type of(BaseKernel), Namespace="MyNa mespace.BaseKer nel,
Kernel")]
[XmlElement(type of(DefaultKerne l), Namespace="MyNa mespace.Default Kernel,
Kernel")]
public Kernel {...}
}

This avoids messing with XmlRoot attributes altogether.

--
HTH
Christoph Schittko [MVP]
Software Architect, .NET Mentor

"Keith Patrick" <ri************ *******@nospamh otmail.com> wrote in message
news:u8******** ********@tk2msf tngp13.phx.gbl. ..

I dunno what I was thinking with that ctor stuff. I can set the namespace
independently, and it works (at least without the Runtime: stuff):

<Kernel xmlns="MyNamesp ace.DefaultKern el, Kernel"/>
will deserialize just fine as long as my XmlRootAttribut e has a name of
"Kernel" and a namespace of "MyNamespace.De faultKernel, Kernel", which is
basically a non-metadata way of doing what you suggested. Thanks for
steering me in the right direction

[Christoph Schittko [MVP]]

Would attaching multiple XmlElement attributes to the property work better
for you? Something like:

public class AppConfigObject {
[XmlElement(type of(BaseKernel), Namespace="MyNa mespace.BaseKer nel,
Kernel")]
[XmlElement(type of(DefaultKerne l), Namespace="MyNa mespace.Default Kernel,
Kernel")]
public Kernel {...}
}

This avoids messing with XmlRoot attributes altogether.

--
HTH
Christoph Schittko [MVP]
Software Architect, .NET Mentor

"Keith Patrick" <ri************ *******@nospamh otmail.com> wrote in message
news:u8******** ********@tk2msf tngp13.phx.gbl. ..

I dunno what I was thinking with that ctor stuff. I can set the namespace
independently, and it works (at least without the Runtime: stuff):

<Kernel xmlns="MyNamesp ace.DefaultKern el, Kernel"/>
will deserialize just fine as long as my XmlRootAttribut e has a name of
"Kernel" and a namespace of "MyNamespace.De faultKernel, Kernel", which is
basically a non-metadata way of doing what you suggested. Thanks for
steering me in the right direction

[Keith Patrick]

I'm not able to do that because I need to allow for any subclass of
BaseKernel to be used.