Hi,
we recently face some user complaints that one application with WPF GUI (.net 3.5.1) raises a message box "application stops responding".
This happens when the application is busy and someone klicks it with the mouse at any place. Then it turns opaque, a second klick causes immediately that message box coming up.
"application name" is not responding. Windows can check online for a solution. If you close the program you might lose information.
- check for a solution and close the program
- close the program
- wait for the program to respond.
Problem is that the first two of the three options offered involve "close application" although it's work in the background isn't yet finished and the program is ABSOLUTELY NOT crashed.
It also happens with Outlook 2010 when it retrieves messages in the background...
Is there a registry key that can configure that delay?
Or are there some other settings they could influence that behavior?
We are nearly sure that this is related to dot net GUI only, so far CPU consuming dummy apps in VB or C++2010 with a GUI don't show that behavior. And so far this didn't happen for nearly 2 years and now a growing number of users complain there must have been changed something in the environment or that came out of one of the Microsoft bugfixes.
IT architect - Terminal servers, virtualizations, SQL servers, file servers, WAN networks and closely related to software devleopment (8 years + experience in VB, C++ and script langugaes), MCP for SQL server and CCAA for Xenapp 6.5