Gabor Apati-Nagy 92f0499911 CA-149867: Invoke on MainWindow instead of various controls ... We observed that some threads can reach deadlock-ish state after they have Invoked into a control's UI thread. When it happens they are all in a waiting for join or in sleep state for very long time, although there should not be any deadlock situations. It seems this has something to do with multiple parent controls and with which control we invoked on. This should not make a difference, because we have got one UI thread (for MainWindow) they should wait for, but we have seen it does. The solution that fixed this issue was to invoke on the MainWindow instead of various controls (see a4fe507adf ). This changeset is changing all our Invokes to invoke into MainWindow instead of a control itself. (MainWindow's UI thread is the only UI thread all Control is using in XenCenter) This changeset should be in place until we have found the root cause or the exact reason for the above.		2015-04-08 15:16:10 +01:00
..
NetworkList.cs	CA-149867: Invoke on MainWindow instead of various controls	2015-04-08 15:16:10 +01:00
NetworkList.Designer.cs	CP-4816: Initial commit to git repo	2013-06-24 12:41:48 +01:00
NetworkList.ja.resx	CP-4816: Initial commit to git repo	2013-06-24 12:41:48 +01:00
NetworkList.resx	CP-4816: Initial commit to git repo	2013-06-24 12:41:48 +01:00
NetworkList.zh-CN.resx	CP-4816: Initial commit to git repo	2013-06-24 12:41:48 +01:00