Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / General / August 2007

Tip: Looking for answers? Try searching our database.

How to debug

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Thomas H. Lanier - 31 Jul 2007 22:14 GMT
I'm trying to learn a little about VS 2008 and ASP.Net.

In trying to duplicate some of Scott Guthrie's examples using the new
LinqDataSource, I'm getting an error.
Input string was not in a correct format.
How would one go about debugging errors that occur with components such as
the LinqDataSource. In particular is there a way to trace the code executed
by a component such as the LinqDataSource?

Thanks
Jesse Houwing - 31 Jul 2007 22:31 GMT
* Thomas H. Lanier wrote, On 31-7-2007 23:14:
> I'm trying to learn a little about VS 2008 and ASP.Net.
>
[quoted text clipped - 6 lines]
>
> Thanks

I usually set Visual Studio to break on all exceptions regardless of if
they're handled or not. that way you get an automatic breakpoint the
closest you can get to the actual error.

Maybe it helps.

Jesse
Mark Rae [MVP] - 31 Jul 2007 23:51 GMT
> I usually set Visual Studio to break on all exceptions regardless of if
> they're handled or not. that way you get an automatic breakpoint the
> closest you can get to the actual error.

Absolutely! Surely every serious developer does that...

Signature

Mark Rae
ASP.NET MVP
http://www.markrae.net

Jesse Houwing - 01 Aug 2007 00:02 GMT
* Mark Rae [MVP] wrote, On 1-8-2007 0:51:

>> I usually set Visual Studio to break on all exceptions regardless of
>> if they're handled or not. that way you get an automatic breakpoint
>> the closest you can get to the actual error.
>
> Absolutely! Surely every serious developer does that...

Are you serious or being sarcatic?

I was pretty serious. There usually are ways of avoiding the exception
all together (additional validation, different method overload etc). So
when an exception is thrown I either document that it gets thrown at
that codepoint once in a while and haven't found a way to clear them up
or I solve the issue.

Ohh and should you not be able to find the 'Exceptions...' menu item in
the debug menu (it sometimes seems to disappear) you can add it by
right-clicking the menu, choosing customize and dragging it back into
the menu.

Jesse
Mark Rae [MVP] - 01 Aug 2007 09:43 GMT
>>> I usually set Visual Studio to break on all exceptions regardless of if
>>> they're handled or not. that way you get an automatic breakpoint the
[quoted text clipped - 3 lines]
>
> Are you serious or being sarcatic?

Perfectly serious.

> I was pretty serious.

Indeed.

Signature

Mark Rae
ASP.NET MVP
http://www.markrae.net

Jesse Houwing - 01 Aug 2007 10:31 GMT
* Mark Rae [MVP] wrote, On 1-8-2007 10:43:

>>>> I usually set Visual Studio to break on all exceptions regardless of
>>>> if they're handled or not. that way you get an automatic breakpoint
[quoted text clipped - 9 lines]
>
> Indeed.

phew ;)

Jesse

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.