System.WIndows.Application static members are thread safe?
Posted
by Lirik
on Stack Overflow
See other posts from Stack Overflow
or by Lirik
Published on 2010-03-17T16:56:14Z
Indexed on
2010/03/17
17:11 UTC
Read the original article
Hit count: 366
The Application static members are supposed to be thread safe:
The public static (Shared in Visual Basic) members of this type are thread safe. In addition, the FindResource and TryFindResource methods and the Properties and Resources properties are thread safe.1
How much can we trust that statement in a multithreaded environment when calling static member methods of System.Windows.Application?
Update:
It's all in reference to this question: http://stackoverflow.com/questions/2463822/threading-errors-with-application-loadcomponent-key-already-exists/2463866#2463866
I never thought I'd see a real bug in the library, but this must be the day for me... that question seems to show a genuine bug. Usually it's "user error," but this doesn't seem to be the case.
© Stack Overflow or respective owner