Frage

I am currently stuck with the following problem and running desperately out of ideas, any clues are welcome!

We are using a custom built framework that loads what we call "pages" on demand for the UI, each of these "pages" is a self contained Silverlight XAML that is loaded on demand via:

XamlReader.Load(somePageXamlFile)

It may happen that a part inside this xaml is outdated, so a try / catch block ensures that a XAMLParseException is caught and the respective error handled.

Our current error handling is heavily based on the message of the exception, e.g. we expect a message like this:

"The type 'someType' could not be found. [Line: x Position: y]"

-> we parse the message string and replace the essential xaml parts with custom logic to make it valid again and display info for administrators.

The problem: Some test machines throw the same exception, but with a different message! Errormessage there:

"Error 2502 An error has occured."

This breaks our "safety net" logic for this case and currently we can not figure out any reason for this.

Solutions or proposals are very welcome, thanks in advance!

-Steve

War es hilfreich?

Lösung

After long and hard search we came down to the following: The clients and the development machines seem to have different versions of the Microsoft agcore.dll (development machines have 2 different version in different paths). As this is the core of the exception we suppose this is the reason for the different error message - we were unable to fix this issue however (we cannot be sure what dll our clients get during SL5 download...) therefore we decided to rewrite the whole code segment to not make use of the exception message text at all. Lesson learned.

Thanks for the feedback. -Steve

Lizenziert unter: CC-BY-SA mit Zuschreibung
Nicht verbunden mit StackOverflow
scroll top