"Arindrajit Biswas" wrote:

> Just add a Try Catch block around your code as follows:
>
> Try
> Dim x As String
> Console.WriteLine(x.Substring(0, 34))
> Catch ex as Exception
> Console.WriteLine(ex.StackTrace)
>
> Then put a breakpoint in catch block. Debugger will break.
>
>
> "HoloDoc" wrote:
>
> > Hi,
> >
> > Running VS.NET 2005 SP1. Just recently moved from VS.NET 2003.
> >
> > Have following simple code. Basically when form loads it opens a web site
> > into control WebBrowser1. This works fine. Then use event
> > WebBrowser1_DocumentCompleted to perform actions once the document has loaded.
> >
> > The problem is any exceptions thrown after this are no longer handled
> > correctly by the debugger. Instead the exception is written to the output
> > window and the application just shows the form. I am expecting the
> > application to break at invalid code so I can diagnose the problem. I have
> > placed a invalid substring to force the error. If we force error before
> > webpage is loaded the debugger breaks correctly.
> >
> > Have done much testing and it all is related to using DocumentCompleted.
> > Thanks in advance.
> >
> >
> > Public Class Form1
> >
> > Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As
> > System.EventArgs) Handles MyBase.Load
> >
> > 'This error would generate an exception and break debugger.
> > 'Dim x As String
> > 'Console.WriteLine(x.Substring(0, 34))
> > Me.WebBrowser1.Navigate("http://any-website")
> >
> > End Sub
> >
> > Private Sub WebBrowser1_DocumentCompleted(ByVal sender As Object, ByVal
> > e As System.Windows.Forms.WebBrowserDocumentCompletedEventArgs) Handles
> > WebBrowser1.DocumentCompleted
> >
> > 'Fake an error
> > Dim x As String
> > Console.WriteLine(x.Substring(0, 34))
> > End Sub
> >
> > End Class