Geek asks and answers

How to break an incorrect cross-stream error

We recently upgraded from VS2005 to VS2010. I noticed that unlike VS2005, when the debug code and ID2 VS2010 encounters the operation "Invalid cross-thread", the IDE simply terminates the application without "breaking" in the line of code that causes the problem.

I looked at Debug> Exceptions in the IDE, but I did not find Invalid Cross Thread Operation as a valid parameter in the System.Threading namespace. I lost a little how to make the VS2010 IDE behave like the VS2005 IDE, where it will break the code and select a line causing an invalid cross-flow operation.

Can anyone help me here?

+3
source share
3 answers

I found that if you include all System.Threading exceptions (although Cross-Thread is not specified), the IDE now aborts Cross-Thread errors. I have no clue that the “what” namespace for Threading Exception contains this particular parameter, but now I have my IDE working as VS2005.

0
source

Change all options in Debug> Exceptions in "Thrown" How the old VS behaved.

0
source

Try System.UnauthorizedAccessException. It catches my cross thread errors

0
source

More articles:


All Articles