Validating XML InnerText values

[ACTCMS]

Is there an elegant way to determine what data type(s) an XML node InnerText value can be converted to? Or is it a matter of trying the conversion and trapping any errors?

[bgowland]

In some ways, the exceptions thrown when attempting to do anything (converting data, file handling etc.) are actually the most elegant way of doing things even though it seems like a 'safety net' way of handling things.

Checking that the inner text of what should be a boolean XML node, for example, is 'true' or 'false' rather than 'ture' or 'flase' would be reinventing the wheel. Simply trying a conversion to a boolean will mean the .NET framework will perform those checks for you and throw an exception if it doesn't know how to interpret things.

If you set defaults for variables and ignore any exceptions that are caught, the code will simply act in a default manner.

That's my tuppence worth anyway.

Cheers,
Brian

[psycik]

XML in it's "Pure" form should include namespaces and the datatype of the node.

For for most practical applications you don't have access to this so everything comes off as a string and you'll have to test what you can set it to.

But if you're making your own XML file, then you could put the datatype in.....

[ACTCMS]

If you set defaults for variables and ignore any exceptions that are caught, the code will simply act in a default manner.

That was certainly Plan B. I suppose after 35 years of doing my own error checking I should be dragging myself into the 21st century...

Alex

[ACTCMS]

XML in it's "Pure" form should include namespaces and the datatype of the node.

For for most practical applications you don't have access to this so everything comes off as a string and you'll have to test what you can set it to.

But if you're making your own XML file, then you could put the datatype in.....

It's a simple config XML file which will be edited by notepad for the moment - but, if I ever get around to building a config app, that's something I'll look at...

[psycik]

This is where serialisation help, since it takes away with you having to worry about reading and writing the attributes.

[bgowland]

It's a simple config XML file which will be edited by notepad for the moment - but, if I ever get around to building a config app, that's something I'll look at...

Didn't I send you the code that I use for the config app. in dvbt radio? Fairly primitive but it does the job. Let me know if you want it.

One downside, however, is if the user decides to edit the xml file and puts typos in - you'd still need exception handling (or your own wheel ).

The only sure way of doing it would be to have a UI which does all the data validation and encrypt the XML file so it can't be edited by hand. Just because a file isn't editable with a text editor doesn't mean it can't have XML content.

Cheers,
Brian

[ACTCMS]

This is where serialisation help, since it takes away with you having to worry about reading and writing the attributes.

Now, you are starting to confuse me:p Actually, I've come across the term "serialisation" but I haven't put it into context yet - something else I'll get around to

[ACTCMS]

Didn't I send you the code that I use for the config app. in dvbt radio? Fairly primitive but it does the job. Let me know if you want it.

You did send that code, thanks - I'm just not sure if I need a config app, since most of the settings can be changed in the plugin and the xml file is simply storing the current values.

Alex

[whurlston]

This is where serialisation help, since it takes away with you having to worry about reading and writing the attributes.

Agreed. It's also much, much faster when reading/writing large xml files.