[RESOLVED] String Comparison problem

[robbcorp]

I'm writing an application that will do a lot of string comparisons and noticed a little quirk.

A little background: The application reads data, serializes, then writes to an XML file. Later in time, the application will read in another set of data, serialize and store to an XML file. My application is to compare these two XML files, looking for changes. So, I deserialize into my class and do my comparison method. Everything works except when it hits the string:

"Logitech® Camera Driver"

Both classes contain this string but the code will never find them to be equal. Does something happen when this string gets serialized then deserialized to cause this comparison to return false? Might you guys know a work around?

[torrud]

Maybe you should post your compare method and the serialize/deserialize block?

I think you are running into charset problems during serialize/deserialize.

[robbcorp]

Maybe you should post your compare method and the serialize/deserialize block?

I think you are running into charset problems during serialize/deserialize.

The entire compare method is quite messy in this early stage but you can imagine that it looks at each element of the new deserialized class and searches for that same text in the old deserialized class. The actual comparison is something like:

if(XMLnewAtt.AttValue == XMLoldAtt.AttValue)
{
   //We have a match!
}

What do you mean, exactly by serialize/deserialize block? I just use the XmlSerializer provided with .NET...

I'm betting there's something wrong with the deserialize method because the serialized XML files contain that string, exactly. As a side note, the data does get serialized with a special namespace.

[poochi]

I wrote a small program to compare two strings containing "Logitech® Camera Driver" value. The double equal operator returns true. So, it is not the problem of == operator.

Now we narrow down the problem to the deserializer (since you say the value in serialized xml is correct). Run the debugger and check the value in XMLnewAtt.AttValue & XMLoldAtt.AttValue. As torrud suggested, it might be a problem with char.set (charactor encoding). For Xml serializer class, you need to provide a stream when you serialize and deserialze. Check how the stream is constructed in case of serialization and deserialization.

[robbcorp]

Ok, I'll look into what you had said. I did check when the values actually get compared and it turns out that the new XML file, XMLnewAtt.AttValue, contained the string: "Logitech® Camera Driver" while the old XML file, XMLoldAtt.AttValue contained the string : "Logitech Camera Driver".

So something isn't correct in the deserialization. This confuses me as the same exact methods are used. I know the serialized streams are correct because they are written to file and those two values appear as "Logitech® Camera Driver". I will look at the stream as it gets deserialized and hopefully find something

[robbcorp]

Got it guys. My old XML file did NOT contain this line:

<?xml version="1.0" encoding="utf-8"?>

which must've been causing the encoding issues you guys suggested. I added it and it works just fine now. It wasn't in there because the data gets sent to a SQL stored procedure. I hope I didn't waste anybodys time for to long