Beginners Question Debugging Visual Basic .NEt 2003

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Nosnets
    #1

    Beginners Question Debugging Visual Basic .NEt 2003

    I am learning from a text book. Debugging breakpoints does not work. The
    Breakpoint properties dialogue contains the following comment
    "The breakpoint will not currently be hit. No symbols have been loaded for
    this document."
    After some research with the help system I typed the following path into
    Debug Symbol Files, a property of the Solution
    "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\ID E\symsvr.dll"
    The server is definitely present in my machine at the given address. However
    this has made no difference. I would be grateful if some one could advise me
    how to restore the debug function
    nosnets
    Tags: None
    • JP.Sklenka
      #2
      RE: Beginners Question Debugging Visual Basic .NEt 2003

      I don't mean to over simplify your issue here but please confirm that your
      build configuration is set to Debug and not Production. Make sure you are
      able to build without errors as well (so if you are prompted with a dialog
      window indicating your project had build errors and would you like to
      continue, select no and fix the errors displayed in your task window).

      "Nosnets" wrote:
      [color=blue]
      > I am learning from a text book. Debugging breakpoints does not work. The
      > Breakpoint properties dialogue contains the following comment
      > "The breakpoint will not currently be hit. No symbols have been loaded for
      > this document."
      > After some research with the help system I typed the following path into
      > Debug Symbol Files, a property of the Solution
      > "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\ID E\symsvr.dll"
      > The server is definitely present in my machine at the given address. However
      > this has made no difference. I would be grateful if some one could advise me
      > how to restore the debug function
      > nosnets[/color]

        Comment

        • Nosnets
          #3
          RE: Beginners Question Debugging Visual Basic .NEt 2003

          Thanks very much for your help. My build configuration was not set to debug.
          I would not have spotted this without your help. Ronger Stenso

          "JP.Sklenka " wrote:
          [color=blue]
          > I don't mean to over simplify your issue here but please confirm that your
          > build configuration is set to Debug and not Production. Make sure you are
          > able to build without errors as well (so if you are prompted with a dialog
          > window indicating your project had build errors and would you like to
          > continue, select no and fix the errors displayed in your task window).
          >
          > "Nosnets" wrote:
          >[color=green]
          > > I am learning from a text book. Debugging breakpoints does not work. The
          > > Breakpoint properties dialogue contains the following comment
          > > "The breakpoint will not currently be hit. No symbols have been loaded for
          > > this document."
          > > After some research with the help system I typed the following path into
          > > Debug Symbol Files, a property of the Solution
          > > "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\ID E\symsvr.dll"
          > > The server is definitely present in my machine at the given address. However
          > > this has made no difference. I would be grateful if some one could advise me
          > > how to restore the debug function
          > > nosnets[/color][/color]

            Comment

            • spamsux
              #4
              Re: Beginners Question Debugging Visual Basic .NEt 2003

              For other debug problems ...

              Addtional ways to get rid of the "No sybmols loaded.."

              Something that worked for me.
              1. iisreset
              2. Consider clearing out the temporary files found in
              C:\WINDOWS\Micr osoft.NET\Frame work\v1.1.4322\ Temporary ASP.NET Files
              3. Delete C:\Documents and Settings\<your login>\VSWebCac he\<your
              project>
              4. Open VS .NET again

                Comment

                Previous template Next
                Working...