An unhandled exception of type ?

Question

0.00/5 (No votes)

See more:

Hi everybody again,
In my wpf application, i have a button to get data from some device. When i "click" the button, i get the next exception.

"An unhandled exception of type 'JKKR.Core.Exceptions.EIncorrectDeviceId' occurred in PresentationFramework.dll"

Here is a part of my code:

VB

Private Sub Button_Click(ByVal sender As System.Object, ByVal e As System.Windows.RoutedEventArgs) Handles Button.Click
              

SpyModem.GetSatelliteMemory(Sate, "0256", 1, memory)
 TextBox1.Text = Sate

    End Sub

Details: My application is composed by many Windows (formulary). So, In some cases, I must call another window (formulary) by clicking on a button.
When i Click the Button, the program show the line where is the problem:

VB

    Public Sub Button_Acqui(ByVal sender As System.Object, ByVal e As System.Windows.RoutedEventArgs)

       
        Dim fenetreAcqui As New Acquisition()
        fenetreAcqui.Fenetre_main = Me.Fenetre_main


           fenetreAcqui.ShowDialog()
End Sub

The last methode open a new window. That window is within of ViewBox.
The problem is in the next line:

VB

fenetreAcqui.ShowDialog()

Note: I have a DLL Library.
Somebody can give some clue about this problem? is something about parent and child?

Posted 1-Aug-13 4:25am

alonetmr

Add a Solution

Comments

Pheonyx 1-Aug-13 10:35am

What is "Acquisition()" ? is that a form?
If so what code is in it's "Load" event?

alonetmr 1-Aug-13 14:40pm

hi,
In fact, "Acquisition()" is a class.

[no name] 1-Aug-13 10:47am

This should give you some idea http://www.codeproject.com/Articles/79508/Mastering-Debugging-in-Visual-Studio-2010-A-Beginn

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)

Sergey Alexandrovich Kryukov · Answer 1 · 2013-08-01T07:07:00

First of all, run it under the debugger and find out where the exception was thrown. Put a breakpoint before it happens and use the VS "Watch" window to inspect variable. Consult the device documentation on the parameters required for the call in question and other requirements. Show VS "Call stack" windows (under the "Debug" menu) to find out the stack and the path of the propagation of the exception. You will see all what happens starting from the root cause of it, from the initial UI event, for example. Fix the problem.

You need to catch all exceptions on the top stack frame of each stack. Don't catch too much, keep it to necessary minimum, where you really know what to do with exception handling. UI has a special feature to catch all exception in the top even handling loop. For WPF, this is done via the Application.DispatcherUnhandledException event:
http://msdn.microsoft.com/en-us/library/system.windows.application.dispatcherunhandledexception.aspx[^].

You should always do that. In case of some problem, you can alternatively add additional code for the research: when some exception is caught, output its stack trace:
http://msdn.microsoft.com/en-us/library/system.exception.stacktrace.aspx[^].

This is just a string, and it will show you the same exception propagation path, as with the "Call Stack" used under the debugger. In rare cases when debuggers is hard to use, you can simply log exception information (with stack trace) and still dig out the problem. For logging, please see:
http://msdn.microsoft.com/en-us/library/system.diagnostics.eventlog.aspx[^].

—SA