There is a bug in the Silverlight 5 runtime that may trigger AccessViolationException, hosing the whole app when PropertyChanged event is fired.
This occurs even if you compile the application for Silverlight 4 and the client had upgraded to Silverlight 5. Since PropertyChanged is literally everywhere, it is a matter of time before it occurs on *your* application. (It happened to mine, and costed a whole day working around it for a single screen) Could you please vote this issue up? https://connect.microsoft.com/VisualStudio/feedback/details/719572 Thanks. Chui
_______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
