Dear all,
We recently replaced the traditional file menu by a UltraToolbarsManager control in our desktop application and everything works well -- except when we found out one issue that needs to be addressed.
When we use Remote Desktop and run our desktop application, Disconnecting the remote session and THEN reconnecting will cause the desktop application close. It happens when the reconnect happens ( we have code to check and confirmed the app is still running after disconnect ).
Some clues:
Any idea how we can find out what is causing the issue? Thanks very much in advance.
-- Alex
Please check this forum post where the same issue were discussed.
Here is what happens when you disconnect from remote desktop. When using remote desktop, the OS recognize the connection and changes the OS theme to disable Aero (glass). UltratoolbarsManager listens for this change, which is broadcasted to all windows when Aero is enabled/disabled. When the Aero is enabled, we would force the form to recreate it's handle and be able to render the glass frame correctly. Unfortunately, the .NET Framework causes modal forms to close when it recreates its handle.
This is exactly what Michael described in his answer. Also, he has attached a sample with no Infragistics, where the issue is still reproducible.
As you can see there is nothing we can fix here. The issue is in .NET and not in our components and there is no way to workaround this.
Your component crashed when RDP reconnected. and you say that is not your problem. Joke ?
The fact is that when remote desktop session reconnected, application crashed.
We met the same problem. and you said you can not assist with this !!!
Regret to use your components !!!
Hi Michael.
I think "recreatingHandle()" to refresh the Ribbon menu is excessive with no matter what how Window caused it. Any plan to address this in later version of WinForm infragictic ?
Thanks
Since we do not control the theme services and this is handled by the OS there isn't much we can assist with unfortunately. There are several unknown issues revolving around OS which we cannot fix. There is a similar discussion on social.technet.microsoft.com
Let me know if you have any further questions regarding this matter.