I'm receiving this error when I start my application but I have NO idea what feature isn't implemented. It doesn't print anything to the console or tell me what isn't implemented.
Is there a way to figure this out? The only thing I have to go on is this error message that appears in a window:
Interestingly enough my application does start after I click ok, but I'd like to figure out what the problem is.
Minimize to systray is my first guess. That wasn't implemented last time I looked.
But you might be able to find a stack trace in Windows' Event Viewer -- Application Log
Related
This is related to my other question.
I used the OnStructureChanged event to detect that the 'Help' window popped up in the 3rd party application that my application is writing data to. I need my application to pause while the end user resolves the data issue in the 3rd party application, then I need my application to resume once the end user closes the 'Help' window. (Either I need to detect that the 'Help' window was closed or I need to display a message box and use the DialogResult to trigger my application to resume).
I've never encountered something like this before. I don't know if it's possible to do what I want to do. If it is possible, I don't know where to start.
Advice?
UPDATES:
I have only used Threading once before and I think it was a fairly "easy peasy" usage, I pulled it off without much effort, considering I'd never used Threading before. I'm playing around with Threading for this issue right now. There's a good chance I've implemented it incorrectly, but my app isn't functioning correctly anymore...I don't know if I'm even playing with the correct tool.
I had to just keep moving with the project - deadlines, you know...
I ended up using UI Automation to detect the "Help" window, then I showed a message box giving instructions to the end user. I check the MessageBox's DialogResult and continue processing based on that. It might not be the "best" way to skin the cat, but I'm a noob and I have a deadline, so I did what I needed to do to keep moving.
I'm looking for a little help regarding the win32 exception "error creating window handle".
From time to time our program (WinForms - C#) throws this exception and sometimes the windows even freeze, so that the users have to kick the process to be able to work again.
From the many other threads regarding this problem, I know what I should be looking for, but not extactly where as our program is quite big. So I was hoping that there might be a way to restrict the codelines I have to check... Are the any tools, which can help with this exception?
Short update: I solved the problem.
ProcDump didn't help me much, because I got pretty the same information from our logfiles. However, I was able to reproduce the error in our development environment. Thanks to debugger and displaying the user-objects count in the taskmanager I found the source of the memoryleak - an undisposed texbox which was created dynamically.
Thanks again for the tips!
If this issue happens inside the debugger, you can set the debugger (I will assume Visual Studio as you're using C#?) to break on throwing an exception. In your case you would want to set an exception breakpoint on (I think) System.ComponentModel.Win32Exception.
Again assuming Visual Studio as your IDE, on the "Debug" menu is an "Exceptions..." item. This allows you to tell the debugger to break when specific exceptions are a) thrown, or b) unhandled.
Under Common Language Runtime Exceptions, expand System.ComponentModel, and enable the checkbox in the Thrown column for System.ComponentModel.Win32Exception.
Then just carry on as normal. If during debugging the exception occurs, it should break into your program and allow you to see where it's happening.
Edit: If you can't reproduce the problem on your development machines, see if you're able to set up the target machine to produce a dump when a crash occurs. One way of doing this is to run ProcDump. Run it with the -e parameter to create a dump in the event of an exception. Then you can analyse this back at the ranch.
We recently released a desktop record keeping product that required a simple spell checker on a couple text box fields. We use DevExpress 10.1 XtraSpellChecker. It does exactly what we need but customers report that occasionally it simply stops working and shows all words as being mis-spelled.
My guess is that it cannot open the dictionary but I have no clue as to why. Typically stopping and restarting the program solves the problem.
Most instances of this error occur on computers with single users who have full modify rights on the installation folder ( location of dictionary ).
Anyone experience the same thing, have ideas of what might be causing this? Search of DevExpress forum has proven fruitless. It does happen on more than one installation but several have reported no issues.
Oh, and we are using it in Spell As You Type mode.
The check as you type mode works by checking the text in a background thread. Such a situation can occur if an exception is raised in the background thread that terminates it. Try to include a handler to all exceptions raised in your app and ask your users to send you the log when this problem occurs. To learn how to catch exceptions in all threads, please refer to the code snippet posted in the
Application.ThreadException Event MSDN article.
During Windows XP development, if my application encountered an unhandled exception it would display an error message "X has encountered and error..." and give me the option to launch the debugger. Under Windows 7, all I get is a message that says "X has stopped working, Windows is checking for a solution".
I can no longer see any details of the error message and I'm not given the option to debug.
I'm using VS2005 and JIT debugging is enabled as far as I can tell.
Is there anyway to get back to the useful error messages of WinXP?
Edit: It is just a standard WinForms desktop application, requiring no special permissions to run.
Maybe you find the WER (Windows Error Reporting) settings useful:
http://msdn.microsoft.com/en-us/library/bb513638%28VS.85%29.aspx
Also, you can use this as a landing point to get in touch with WER:
http://msdn.microsoft.com/en-us/library/bb513641%28v=VS.85%29.aspx
Unfortunately I can't directly answer your question, but perhaps this can serve as a hint for further researching.
OK, found an answer thanks to the comment from leppie.
Go to Control Panels->Action Center
Expand the Maintenance tab and select Settings under "Check for solutions to problem reports"
Change to "Never check for solutions"
Now when the error occurs there is a "Debug the program" option in the dialog.
My winform application is failing when run outside of the IDE with a dragdrop exception. The error does not occur while being run from inside the ide (VS2008). How can I trace this. I have seen mention of using JIT in the error box that is displayed post error - will this help me trace my problem?
Don't know if this will be helpful, but...awhile ago I was getting DragDropException when my WinForms app was being run on a thumb drive, not a full system. The form generating the error had no drag-and-drop feature. I never figured out the problem, but I saw that a UserControl on that form had defaulted AllowDrop=true unnecessarily. Once I turned that off, the problem went away.
If your form is intended to support drag-and-drop, I'd look into on what thread the form generating the exception is instantiated. My understanding is that Microsoft's implementation of drag-and-drop is COM-based, which must be initialized in an STA thread. Putting the [STAThread] attribute before your program's entry point will accomplish this.