I think you missed my point there. The legacy UI seems to force an update from the application cluster, which the Silverlight UI then picks up on.
I've repeated the following scenario several times.
- Start a deployment
- Wait 30+ minutes. The Silverlight UI still shows that the dpeloyment is incomplete. The Last Refresh time has not updated either. Note that I have sometimes waited up to two hours, and confirmed that the web site is in fact accessible, but it still shows
as unfinished in the Silverlight UI.
- Go to the legacy UI. It shows the deployment as completed.
- A few seconds later, on the next refresh interval, the Silverlight UI shows the deployment as completed.
It seems unlikely that the Silverlight UI, after not seeing that deployment update for 30+ minutes, would just happen to pick up those changes mere seconds after I looked at the status in the legacy UI. It seems very, very unlikely that it would happen repeatedly.
I can only conclude that looking at the deployment in the legacy portal forces an update from the application cluster, which the Silverlight UI picks up on it's next refresh
It would be really nice if the Silverlight UI would do whatever the legacy UI is doing, so that they could both show accurate data.