Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
What I don't like about debugging
Message
De
03/09/2013 17:06:20
John Baird
Coatesville, Pennsylvanie, États-Unis
 
 
À
03/09/2013 16:29:21
Information générale
Forum:
ASP.NET
Catégorie:
Test et débogage
Versions des environnements
Environment:
C# 4.0
OS:
Windows 7
Network:
Windows 2003 Server
Database:
MS SQL Server
Application:
Web
Divers
Thread ID:
01581956
Message ID:
01581973
Vues:
54
>>>>Hi everybody,
>>>>
>>>>Unlike VFP, then an exception is caught, there seems to be no way to go back to the previous line of code that caused the exception and examine the content of the variable.
>>>>
>>>>Is it really a problem in VS or I am doing something wrong?
>>>>
>>>>Thanks in advance.
>>>
>>>It depends on if the variable is still in scope. If its an unhandled exception and the debugger stops you on the line of the error, you should still be able to view the variable's value. If you are handling the exception and the variable goes out of scope you'll need to set a breakpoint and view the value before the exception.
>>
>>I have a top level try/catch block. So, one method calls another method, then another and another... and finally the exception is caught at the top level method.
>>
>>I have to repeat the whole test in order to see why I got the exception.
>
>Try going to Debug>Exceptions. Click the checkbox in the Thrown column for the type of exception you are trying to fix, or just Common Language Runtime Exceptions for all .NET managed exception


Or use the CallSTack and go back .. each line allows you to view the variables at that spot.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform