Handling ContextSwitchDeadlock when no user interaction is expected?

Asked Feb 11 '13 at 17:21

Active Feb 11 '13 at 17:21

Viewed 45 times

There are several questions about this but my situation carries a caveat, no UI. There's 2 main solutions, neither of which I like. One repeated answer says to offload the work on a background thread. My app is started with command line parameters by another program and generates a report to a specific folder. I believe there's no reason it should have an unoccupied main thread to respond to input that it's not expected to receive and going to do anything with. The window's not even visible for a user to interact with. The other solution is to turn off the warning so it goes unnoticed. This sounds too much like ignoring a fire.

Can I change the thread's ApartmentState, Culture, or Principal to avoid this error? I must admit I don't know much about any of those things.

edited May 23 '17 at 12:18

Community

asked Feb 11 '13 at 17:21

Corey Ogburn

24,072
31
113
188

Why do you create a window if the user is never going to interact with it? The warning basically implies that the window isn't going to work. So there's just no point in creating one. – Hans Passant Feb 11 '13 at 17:39
There is no window. It's a console application whose console does not appear. – Corey Ogburn Feb 11 '13 at 17:43
Ok, it's technically a Windows Form Application, but it does not actually create a window. Like this question and it's marked answer: http://stackoverflow.com/questions/3563744/how-can-i-hide-a-console-window – Corey Ogburn Feb 11 '13 at 17:47
Remove the [STAThread] attribute from the Main() method. – Hans Passant Feb 11 '13 at 17:48
@Hans Passant, There isn't one. – Corey Ogburn Feb 11 '13 at 17:49
Also, for the record, this is a VB.Net app. – Corey Ogburn Feb 11 '13 at 18:03
I'm just going to wait a day or two until you're done dribbling important details like that. – Hans Passant Feb 11 '13 at 18:07
I didn't think that the language was critical. In my understanding, this exact same app in C# or F# would have the exact same problems. No previous answer has been language specific. – Corey Ogburn Feb 11 '13 at 18:39

Handling ContextSwitchDeadlock when no user interaction is expected?

0 Answers0