|
Our application has been deployed to the field for about 3 years and ran very well. In the last month we have suddenly started having interactions with what appears to be changes to the default printer.They are extremely intermittent and appear to have only an association with the change of a printer. The application users print documents in a few places and we have checked each to assure that the print document and any related classes are disposed. The application is in VB.NET. Some users seem much more affected than others and despite have a dozen test platforms in the lab we can only reproduce the error less than 1% of the time. We have tested with Spy++ and we can see the system change message but nothing seems to react except in these random events however when the event occurs we get no error messages despite an abundance of try catch traps throughout the app. The application simply freezes as though there is an open error message dialog (there isn't) and you can only stop the application via the task manager. Occasionally we will find a app hang error message in the event log but there appears to be no useful information. Does anyone have any ideas that could help. We have searched in all the online areas we can think of and this seems to be a core issue with the framework that we simply cannot isolate. Thanks,
Terry | 
index > Common Language Runtime > Winforms system interaction