Debugging VB Windows Application

[G. Schmelzer]

Hi Ng,

I've got a problem with the debugging of a Windows Application. I start the
app in Debug Mode. But when an exception appears, vs.net doesen't jump to
code line where the exception occured. I only get the standard exception
message. So I cannot trace the line, in which the exception occured. I can
set breakpoints, where the ide then stops.

Does anybody know, how I have to configure the app that it will jump to the
exception line in code?

Thanks in Advance

G. Schmelzer

[Herfried K. Wagner [MVP]]

* "G. Schmelzer" <as**@de.de> scripsit:

I've got a problem with the debugging of a Windows Application. I start the
app in Debug Mode. But when an exception appears, vs.net doesen't jump to
code line where the exception occured. I only get the standard exception
message. So I cannot trace the line, in which the exception occured. I can
set breakpoints, where the ide then stops.

Post the complete exception text (and the callstack, if possible). You
cannot browse the code if the exception occured in a component you don't
have the source code for, like "System.Windows .Forms.dll".

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[G. Schmelzer]

Hi Herfried,
thanks for your help. Here is the exception message.

Informationen über das Aufrufen von JIT-Debuggen
finden Sie am Ende dieser Meldung, anstatt in diesem Dialogfeld.

************** Ausnametext **************
System.FormatEx ception: Die Eingabezeichenf olge hat das falsche Format.
at Microsoft.Visua lBasic.Compiler Services.Double Type.Parse(Stri ng Value,
NumberFormatInf o NumberFormat)
at Microsoft.Visua lBasic.Compiler Services.Double Type.FromString (String
Value, NumberFormatInf o NumberFormat)
************** Geladene Assemblys **************
mscorlib
Assembly-Version: 1.0.5000.0
Win32-Version: 1.1.4322.573
CodeBase:
file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
ColorCalc
Assembly-Version: 0.0.0.1
Win32-Version: 0.0.0.1
CodeBase: file:///C:/Lokale%20Daten/ColorCalc.Net/ColorCalc.exe
----------------------------------------
System.Windows. Forms
Assembly-Version: 1.0.5000.0
Win32-Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system.windows. forms/1.0.5000.0__b77 a5c561934e089/system.windows. forms.dll
----------------------------------------
System
Assembly-Version: 1.0.5000.0
Win32-Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system/1.0.5000.0__b77 a5c561934e089/system.dll
----------------------------------------
System.Drawing
Assembly-Version: 1.0.5000.0
Win32-Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03 f5f7f11d50a3a/system.drawing. dll
----------------------------------------
Microsoft.Visua lBasic
Assembly-Version: 7.0.5000.0
Win32-Version: 7.10.3052.4
CodeBase:
file:///c:/windows/assembly/gac/microsoft.visua lbasic/7.0.5000.0__b03 f5f7f11d50a3a/microsoft.visua lbasic.dll
----------------------------------------
ColorCalc.resou rces
Assembly-Version: 0.0.0.1
Win32-Version: 0.0.0.1
CodeBase:
file:///C:/Lokale%20Daten/ColorCalc.Net/de/ColorCalc.resou rces.DLL
----------------------------------------
System.Data
Assembly-Version: 1.0.5000.0
Win32-Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system.data/1.0.5000.0__b77 a5c561934e089/system.data.dll
----------------------------------------
System.Xml
Assembly-Version: 1.0.5000.0
Win32-Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77 a5c561934e089/system.xml.dll
----------------------------------------
mscorlib.resour ces
Assembly-Version: 1.0.5000.0
Win32-Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/mscorlib.resour ces/1.0.5000.0_de_b 77a5c561934e089/mscorlib.resour ces.dll
----------------------------------------
System.Windows. Forms.resources
Assembly-Version: 1.0.5000.0
Win32-Version: 1.1.4322.573
CodeBase:
file:///c:/windows/assembly/gac/system.windows. forms.resources/1.0.5000.0_de_b 77a5c561934e089/system.windows. forms.resources .dll
----------------------------------------
Microsoft.Visua lBasic.resource s
Assembly-Version: 7.0.5000.0
Win32-Version: 7.10.3052.4
CodeBase:
file:///c:/windows/assembly/gac/microsoft.visua lbasic.resource s/7.0.5000.0_de_b 03f5f7f11d50a3a/microsoft.visua lbasic.resource s.dll
----------------------------------------

************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsd atei der Anwendung oder des Computers
(machine.config ) der jitDebugging-Wert im Abschnitt system.windows. forms
festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.

Zum Beispiel:

<configuratio n>
<system.windows .forms jitDebugging="t rue" />
</configuration>

Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht von diesem Dialogfeld behandelt.
Thanks G. Schmelzer
"Herfried K. Wagner [MVP]" <hi************ ***@gmx.at> schrieb im Newsbeitrag
news:2i******** ****@uni-berlin.de...

* "G. Schmelzer" <as**@de.de> scripsit:

I've got a problem with the debugging of a Windows Application. I start the app in Debug Mode. But when an exception appears, vs.net doesen't jump to code line where the exception occured. I only get the standard exception
message. So I cannot trace the line, in which the exception occured. I can set breakpoints, where the ide then stops.

Post the complete exception text (and the callstack, if possible). You
cannot browse the code if the exception occured in a component you don't
have the source code for, like "System.Windows .Forms.dll".

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Cor Ligthert]

Hi G.

Great that you translated all for Herfried, that will make it a lot easier
for him.

I am sure he can answer it now, I am not sure so I wait on him.
(Not that I cannot read it)

Only for fun

Cor

[G. Schmelzer]

Hi Cor,
actually, I haven't translated it. As I'm German I use the German Edition of
VS.Net ;)

If you want me to, I can translate it. But I doubt that it will be correct.

G.
"Cor Ligthert" <no**********@p lanet.nl> schrieb im Newsbeitrag
news:OC******** ******@TK2MSFTN GP09.phx.gbl...

Hi G.

Great that you translated all for Herfried, that will make it a lot easier
for him.

I am sure he can answer it now, I am not sure so I wait on him.
(Not that I cannot read it)

Only for fun

Cor

[Herfried K. Wagner [MVP]]

* "G. Schmelzer" <as**@de.de> scripsit:

Informationen über das Aufrufen von JIT-Debuggen
finden Sie am Ende dieser Meldung, anstatt in diesem Dialogfeld.

************** Ausnametext **************
System.FormatEx ception: Die Eingabezeichenf olge hat das falsche Format.
at Microsoft.Visua lBasic.Compiler Services.Double Type.Parse(Stri ng Value,
NumberFormatInf o NumberFormat)
at Microsoft.Visua lBasic.Compiler Services.Double Type.FromString (String
Value, NumberFormatInf o NumberFormat)

There is not much info in the message except that VB.NET tries to parse
a double from a string and fails because the string is in wrong format...

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Armin Zingler]

"G. Schmelzer" <as**@de.de> schrieb

Hi Herfried,
thanks for your help. Here is the exception message.

Informationen über das Aufrufen von JIT-Debuggen
finden Sie am Ende dieser Meldung, anstatt in diesem Dialogfeld.

************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsd atei der Anwendung oder des Computers
(machine.config ) der jitDebugging-Wert im Abschnitt
system.windows. forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.

Zum Beispiel:

<configuratio n>
<system.windows .forms jitDebugging="t rue" />
</configuration>

Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht von diesem Dialogfeld
behandelt.

Did you follow the step described here? After that, the IDE should jump to
the error line instead of you getting the other error dialog.
--
Armin

How to quote and why:
http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html

[G. Schmelzer]

Hi Armin,

I did change this Setting. After the change, the breakpoints weren't working
anymore....
G. Schmelzer

"Armin Zingler" <az*******@free net.de> schrieb im Newsbeitrag
news:40******** *************** @news.freenet.d e...

"G. Schmelzer" <as**@de.de> schrieb

Hi Herfried,
thanks for your help. Here is the exception message.

Informationen über das Aufrufen von JIT-Debuggen
finden Sie am Ende dieser Meldung, anstatt in diesem Dialogfeld.

************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsd atei der Anwendung oder des Computers
(machine.config ) der jitDebugging-Wert im Abschnitt
system.windows. forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.

Zum Beispiel:

<configuratio n>
<system.windows .forms jitDebugging="t rue" />
</configuration>

Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht von diesem Dialogfeld
behandelt.

Did you follow the step described here? After that, the IDE should jump to
the error line instead of you getting the other error dialog.
--
Armin

How to quote and why:
http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html