"A first chance exception of type 'System.IO.IOException' occurred in mscorlib.dll "

Question

1.00/5 (1 vote)

See more:

VS2012

Hi, there!
I am the new guy on WCF. These days, I'am learning that.
I made a empty solution, and this solution contains 4 projects: two c# libs, and two consoles as host and client. the programs ran well, but when client started after host, it raise this info in debug output window: "A first chance exception of type: System.IO.IOException occurred in mscorlib.dll"
But, the program looks well and get the right answer, so I want to know what this problem means.
Thanks!

Posted 1-Jun-13 2:55am

freeheartxiii

Add a Solution

Comments

[no name] 1-Jun-13 9:21am

It simply means that you tried an IO operation that could not be performed and caused an exception. The inner exception would probably be more informative.

freeheartxiii 1-Jun-13 21:53pm

OK~ Thank you! I check the code now!

[no name] 1-Jun-13 19:11pm

Spam removed.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

PrissySC · Accepted Answer · 2013-06-02T02:49:00

Actually, I will almost bet that while this is the exception that was caught that it is not the problem. You could catch and handle this and ignore it, but you need to find the underlying cause. Check your output, and do a try catch on the block that you suspect. Print out the exception in a message box so that you can get a better feel for what is occuring.

I hit this type of exception sometimes only to find out that it is another result of action causing the fire.