CA-148233: Uncaught exception in XenCenter on "Disconnect All"
CA-148332: Right click on a Windows VM brought up the PV linux copy/paste context menu

Signed-off-by: Gabor Apati-Nagy <gabor.apati-nagy@citrix.com>
CA-148245: Fix the error where XenCenter did not refresh immediately after disconnecting a server

Added a RequestRefreshTreeView on ClearingCache event.

Signed-off-by: Mihaela Stoica <mihaela.stoica@citrix.com>
CA-148374: Progress action disappears in Events on Dismiss all
-Added a where clause to filter out non-completed actions in this case

Signed-off-by: Gabor Apati-Nagy <gabor.apati-nagy@citrix.com>
CA-148374: Progress action disappears in Events on Dismiss all
-Also fixed the Dismiss Selected button

Signed-off-by: Gabor Apati-Nagy <gabor.apati-nagy@citrix.com>
CA-147941: Fixed the RPU wizard hang in "Reconnecting Storage" and connecting action stuck in progress state

In some cases calling Control.Invoke() from a background thread causes that thread to go in a "sleep, wait, or join" mode, while waiting for Invoke to happen, although the UI thread is running normally.
If the Control is the MainWindow, it works as expected, but we've seen it happening while connecting or disconnecting from a large pool, on calling Invoke on controls like NavigationView, AlertSummaryPage, HistoryPage, etc.
To fix this, we call the Invoke on the MainWindow in all the places where we've seen the issue.

With this changes, the previous fix for CA-148245 (call RequestRefreshTreeView on CacheClearing event) is not needed anymore, so I removed that call.

Signed-off-by: Mihaela Stoica <mihaela.stoica@citrix.com>
CP-10072: Update XenCenter with latest C# bindings

Signed-off-by: Mihaela Stoica <mihaela.stoica@citrix.com>
CP-10072: Update XenCenter with latest C# bindings, including the missing FriendlyErrorNames

Signed-off-by: Mihaela Stoica <mihaela.stoica@citrix.com>
CA-149811: End the connection to each slave after that host has joined the pool to prevent XenCenter showing connection lost alerts

This fixes the following issue: event.from fails with "The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.".
It happens because we end the connections to the slave hosts only after all hosts have joined the pool and in the meantime event.from on a slave fails.

We fix this by ending the connection to each host immediately after the host has joined the pool.

Signed-off-by: Mihaela Stoica <mihaela.stoica@citrix.com>
CP-9928: Link licensing alerts to the Licensing page in XenCenter help

Signed-off-by: Mihaela Stoica <mihaela.stoica@citrix.com>
updated git ignore