String starting with ' won't concatenate

[Gustaf]

Some error handling code:

catch (System.Xml.Xml Exception e)
{
Console.WriteLi ne("Error in " + e.SourceUri + ": " + e.Message);
return;
}

The output:

' is an unexpected token. The expected token is '>'. Line 17, position 50.

Everything in the string before e.Message is deleted. I suspect that this is because the Message property starts with '. Is there a workaround for this?

Gustaf

[Jon Skeet [C# MVP]]

On Jul 27, 9:46 am, Gustaf <gust...@algone t.sewrote:

Jon Skeet [C# MVP] wrote:

The problem is that the second character of the message is a carriage
return.

Thank you both. So Message strings of .NET exception classes may
contain whitespace other than SPACE?

There's nothing to prevent it, certainly.

Does it mean it's generally good
practice to normalize these strings before presenting them?

It depends on how you're presenting them. This is a pretty rare
occurrence, to be honest - but it's not a bad idea to be robust about
your presentation.

Jon

[=?ISO-8859-1?Q?G=F6ran_Andersson?=]

Gustaf wrote:

Jon Skeet [C# MVP] wrote:

>The problem is that the second character of the message is a carriage
return.

Thank you both. So Message strings of .NET exception classes may contain
whitespace other than SPACE?

As it was a carriage return that was the unexpected token, that's what's
put in the error message. In escaped form, the error message would start:

'\r' is an unexpected token.

As you have that character in the input to the method, it might end up
in the exception message.

Does it mean it's generally good practice
to normalize these strings before presenting them?

You might want to do that.

In certain situations, like if you output the message on a web page,
it's crucial for security that you don't display the message without
encoding it properly, otherwise it could be used for cross site
scripting (XSS) atacks.

--
Göran Andersson
_____
http://www.guffa.com