CheckForIllegalCrossThreadCalls = false for cross-thread control update

[12Code]

My app make cross-thread calls to many main form controls. I have disable CheckForIllegalCrossThreadCalls by set it to false, without using any Invoke method for the cross-thread control update. And the app is running fine so far. My question is: Is it okay to turn off CheckForIllegalCrossThreadCalls, for this cross-thread control update? What are the negative effects? Thanks.

Kelvin

[N a v a n e e t h]

8kelvin wrote:

What are the negative effects?

It is only for debugging and will only work when the debugger is attached. Here is what MSDN says, Note that illegal cross-thread calls will always raise an exception when an application is started outside the debugger. :)

Navaneeth How to use google | Ask smart questions

[Nagy Vilmos]

8kelvin wrote:

What are the negative effects?

:~ If you've seen Ghostbusters, I'm sure your aware what happens when you cross the threads. It is bad and kittens maybe hurt. You don't hate kittens do you? :-D

---

Panic, Chaos, Destruction. My work here is done.

[12Code]

Hi Navaneeth, thank for the prompt reply. But the app that i mentioned already installed in other pc, and it run without any problem too.

Kelvin

[Luc Pattyn]

8kelvin wrote:

Is it okay to turn off CheckForIllegalCrossThreadCalls

Not at all. Your app will not work reliably if you do. That property should never have been introduced, they created it when .NET (evolving from 1.1 to 2.0) got strict on cross-thread checking, so they thought it was wise to provide a way to continue doing things the wrong way. :)

Luc Pattyn [Forum Guidelines] [My Articles]

---

- before you ask a question here, search CodeProject, then Google - the quality and detail of your question reflects on the effectiveness of the help you are likely to get - use the code block button (PRE tags) to preserve formatting when showing multi-line code snippets

---