Click here to Skip to main content
15,900,110 members
Please Sign up or sign in to vote.
1.00/5 (2 votes)
See more:
A screen shot of error is at http://core3s.com/error.png[^]
Posted
Updated 31-May-12 7:22am
v2
Comments
Dave Kreskowiak 31-May-12 10:24am    
You might want to tell use what you're using first. Just linking to an image isn't really a valid question.
OriginalGriff 31-May-12 12:08pm    
Even if we do look at the picture, it doesn't really tell us anything useful.
You need to give us much, much better information - all we have at the moment is "I'm using c# and it don't work".
Remember that we can't see your screen, access your HDD, or read your mind.
Use the "Improve question" widget to edit your question and provide better information.
ZurdoDev 31-May-12 13:22pm    
added link
Tim Corey 31-May-12 13:28pm    
A link to the picture is not enough. Read what OriginalGriff said and do that please. Then maybe we can help you.
ZurdoDev 31-May-12 13:43pm    
I am not the OP. I agree with what you say. I was just cleaning it up.

1 solution

If the component exception is propagated up the stack to managed code, .NET framework tries to map it to a managed exception. For example, STATUS_NO_MEMORY maps to OutOfMemoryException and STATUS_ACCESS_VIOLATION maps to NullReferenceException.

For better clarity, you catch the exception details in
C#
try {...}
catch (Exception ex) {...}


Then, share the details of the exception, code and component details. That will help us to provide the solution.
 
Share this answer
 

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



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900