Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Visual Studio
  4. Debuging Step Into(F11) Problem in VS2003

Debuging Step Into(F11) Problem in VS2003

Scheduled Pinned Locked Moved Visual Studio
csharpdebugginghelpquestion
5 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    mnaveed
    wrote on last edited by
    #1

    In the Solution I have, I have 2 projects - one is a Windows Application - and the second is a C# DLL file that has functions and classes defined. The Windows form calls a function in the C# file, when a button is clicked in the form. Problem: I am trying to debug this function. Single step debug using Step into (From Debug menu) or F11 as the shortcut. However, when I hit F11 to step into the function, .NET will not go and allow me to debug the funtion one line at a time. It will not go to the function in the C# DLL at all, but rather behaves as if I hit "Step Over F10" and proceeds to next line of code in windows form without going to the C# DLL. I have the reference of the C# Dll in the Windows app. Also tried putting Break points in the C# DLL. But inspite of the breakpoints, it will not single step in the C# code, but move over to next line in the windows app. Is there a setting? I am connected to Source safe for this solution and all files are checked out. Even tried working disconnected but same problem. I do not think its a .NET install problem because for other locally created projects, the debug feature works ok... i try deleting the debug folders for all apps and rebuild but no luck. Please suggest some ways out of this crazyiness.

    Nav.

    S M J 3 Replies Last reply
    0
    • M mnaveed

      In the Solution I have, I have 2 projects - one is a Windows Application - and the second is a C# DLL file that has functions and classes defined. The Windows form calls a function in the C# file, when a button is clicked in the form. Problem: I am trying to debug this function. Single step debug using Step into (From Debug menu) or F11 as the shortcut. However, when I hit F11 to step into the function, .NET will not go and allow me to debug the funtion one line at a time. It will not go to the function in the C# DLL at all, but rather behaves as if I hit "Step Over F10" and proceeds to next line of code in windows form without going to the C# DLL. I have the reference of the C# Dll in the Windows app. Also tried putting Break points in the C# DLL. But inspite of the breakpoints, it will not single step in the C# code, but move over to next line in the windows app. Is there a setting? I am connected to Source safe for this solution and all files are checked out. Even tried working disconnected but same problem. I do not think its a .NET install problem because for other locally created projects, the debug feature works ok... i try deleting the debug folders for all apps and rebuild but no luck. Please suggest some ways out of this crazyiness.

      Nav.

      S Offline
      S Offline
      sathish s
      wrote on last edited by
      #2

      Make sure your are refering to Debug version of the C# dll and not the release version. Moreover when You build a dll in debug, It will create a .pdb file. This dllname.pdb file contains the debug information, which would help you to debug the code inside a dll. The dll and pdb file should in the same directory of the dll, if You are adding reference from a different location.

      M 1 Reply Last reply
      0
      • S sathish s

        Make sure your are refering to Debug version of the C# dll and not the release version. Moreover when You build a dll in debug, It will create a .pdb file. This dllname.pdb file contains the debug information, which would help you to debug the code inside a dll. The dll and pdb file should in the same directory of the dll, if You are adding reference from a different location.

        M Offline
        M Offline
        mnaveed
        wrote on last edited by
        #3

        thanks for reply i will try this

        Nav.

        1 Reply Last reply
        0
        • M mnaveed

          In the Solution I have, I have 2 projects - one is a Windows Application - and the second is a C# DLL file that has functions and classes defined. The Windows form calls a function in the C# file, when a button is clicked in the form. Problem: I am trying to debug this function. Single step debug using Step into (From Debug menu) or F11 as the shortcut. However, when I hit F11 to step into the function, .NET will not go and allow me to debug the funtion one line at a time. It will not go to the function in the C# DLL at all, but rather behaves as if I hit "Step Over F10" and proceeds to next line of code in windows form without going to the C# DLL. I have the reference of the C# Dll in the Windows app. Also tried putting Break points in the C# DLL. But inspite of the breakpoints, it will not single step in the C# code, but move over to next line in the windows app. Is there a setting? I am connected to Source safe for this solution and all files are checked out. Even tried working disconnected but same problem. I do not think its a .NET install problem because for other locally created projects, the debug feature works ok... i try deleting the debug folders for all apps and rebuild but no luck. Please suggest some ways out of this crazyiness.

          Nav.

          M Offline
          M Offline
          mnaveed
          wrote on last edited by
          #4

          its a debug version and pdb file is in the same folder as dll. i find out that if i change the verion of the dll its start debuging the dll other wise not. any suggesions

          Nav.

          1 Reply Last reply
          0
          • M mnaveed

            In the Solution I have, I have 2 projects - one is a Windows Application - and the second is a C# DLL file that has functions and classes defined. The Windows form calls a function in the C# file, when a button is clicked in the form. Problem: I am trying to debug this function. Single step debug using Step into (From Debug menu) or F11 as the shortcut. However, when I hit F11 to step into the function, .NET will not go and allow me to debug the funtion one line at a time. It will not go to the function in the C# DLL at all, but rather behaves as if I hit "Step Over F10" and proceeds to next line of code in windows form without going to the C# DLL. I have the reference of the C# Dll in the Windows app. Also tried putting Break points in the C# DLL. But inspite of the breakpoints, it will not single step in the C# code, but move over to next line in the windows app. Is there a setting? I am connected to Source safe for this solution and all files are checked out. Even tried working disconnected but same problem. I do not think its a .NET install problem because for other locally created projects, the debug feature works ok... i try deleting the debug folders for all apps and rebuild but no luck. Please suggest some ways out of this crazyiness.

            Nav.

            J Offline
            J Offline
            Jonathan Darka
            wrote on last edited by
            #5

            Have you enabled mixed mode debugging, also I would check how many copies of your C# DLL exist on your machine as it may be confused and not loading the correct one. Copy the latest version of your C# DLL (and its .pdb file) to the debug folder of you windows application and see if that helps.


            Darka [Xanya] "I am not a slave to a god that doesn't exist."

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • World
            • Users
            • Groups