.NET Exceptions - localisation
With applications now being developed for users of many nationalities, localisation is very important.  I read on firefox's web site it is available in 70 languages.  This increases their potential market dramatically.

During a recent user acceptance testing session for my project, a bug was found.  The exception was:

> "String was not recognized as a valid
> Boolean"

As far as the bug went, we were trying to do a bool.Parse() with an empty string. An interesting note was appended that "recognized" was spelt incorrectly as well.  To give some context, users are in Australia, where "recognise" is the correct spelling.  Unfortunately this exception was not generated by us, so changing it would require re-mapping the exception!

Has anybody had any experience with similar situations?
Are there ways to localise the .net exceptions?

I have undergone Microsoft certification exams and a lot of content was related to the importance of localisation and culture, so I thought it reasonable to expect the .NET framework to consider this too.
.NET Exceptions - localisation
===

With applications now being developed for users of many nationalities, localisation is very important.  I read on firefox's web site it is available in 70 languages.  This increases their potential market dramatically.

During a recent user acceptance testing session for my project, a bug was found.  The exception was:

> "String was not recognized as a valid
> Boolean"

As far as the bug went, we were trying to do a bool.Parse() with an empty string. An interesting note was appended that "recognized" was spelt incorrectly as well.  To give some context, users are in Australia, where "recognise" is the correct spelling.  Unfortunately this exception was not generated by us, so changing it would require re-mapping the exception!

Has anybody had any experience with similar situations?
Are there ways to localise the .net exceptions?

I have undergone Microsoft certification exams and a lot of content was related to the importance of localisation and culture, so I thought it reasonable to expect the .NET framework to consider this too.