Stepping through a Vs .net 2005 web service

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Doogie

    Stepping through a Vs .net 2005 web service

    I have been trying to figure out a way to step through a VS .NET 2005
    web service so I can see what is going on. The problem is that I keep
    getting this error:

    "Unable to automatically step into the server. The remote procedure
    could not be debugged. This usually indicates that the debugging not
    has been enabled on the server. See help for more information."

    I have looked at this error out here and everyone keeps saying that I
    need to have this setting in the web config file (<compilation
    debug="true">). However, I have that setting so am not sure why I
    can't get this to work.

  • John Saunders [MVP]

    #2
    Re: Stepping through a Vs .net 2005 web service

    "Doogie" <dnlwhite@dtgne t.comwrote in message
    news:1176836410 .065669.46190@n 59g2000hsh.goog legroups.com...
    >I have been trying to figure out a way to step through a VS .NET 2005
    web service so I can see what is going on. The problem is that I keep
    getting this error:
    >
    "Unable to automatically step into the server. The remote procedure
    could not be debugged. This usually indicates that the debugging not
    has been enabled on the server. See help for more information."
    >
    I have looked at this error out here and everyone keeps saying that I
    need to have this setting in the web config file (<compilation
    debug="true">). However, I have that setting so am not sure why I
    can't get this to work.

    Instead of trying to step into it, how about setting a breakpoint? Attach to
    the aspnet_wp or w3wp process, open the source file and set a breakpoint.
    Then call the service.
    --
    John Saunders [MVP]


    Comment

    • Doogie

      #3
      Re: Stepping through a Vs .net 2005 web service

      Instead of trying to step into it, how about setting a breakpoint? Attach to
      the aspnet_wp or w3wp process, open the source file and set a breakpoint.
      Then call the service.
      I tried to do that too, but do not see either of those processes when
      I go to Tools-->Attach Processes.

      I had a thought though. My web service is a "One Way" web service.
      Could that be why I can't step through it?


      Comment

      • John Saunders [MVP]

        #4
        Re: Stepping through a Vs .net 2005 web service

        "Doogie" <dnlwhite@dtgne t.comwrote in message
        news:1176860199 .029077.125720@ p77g2000hsh.goo glegroups.com.. .
        >Instead of trying to step into it, how about setting a breakpoint? Attach
        >to
        >the aspnet_wp or w3wp process, open the source file and set a breakpoint.
        >Then call the service.
        >
        I tried to do that too, but do not see either of those processes when
        I go to Tools-->Attach Processes.
        >
        I had a thought though. My web service is a "One Way" web service.
        Could that be why I can't step through it?
        I don't know if that's the reason, but why not remove the "One Way" feature
        and see if that helps.

        Also, you may need to check the "show processes from other users" checkbox
        before you can see those processes. Also, they start up on demand, so if
        there has been no previous use of ASP.NET on that machine, the processes
        won't be there. In that case, try accessing the web service through a
        browser, and _then_ attaching.
        --

        John Saunders [MVP]


        Comment

        • Doogie

          #5
          Re: Stepping through a Vs .net 2005 web service

          Turns out that the OneWay Web Service attribute was the problem.
          Removing that allowed me to step through the code.

          Comment

          • John Saunders [MVP]

            #6
            Re: Stepping through a Vs .net 2005 web service

            "Doogie" <dnlwhite@dtgne t.comwrote in message
            news:1176898789 .936522.198080@ n76g2000hsh.goo glegroups.com.. .
            Turns out that the OneWay Web Service attribute was the problem.
            Removing that allowed me to step through the code.

            Thanks for reporting back to the newsgroup. This is good information to
            have.

            --
            John Saunders [MVP]


            Comment

            Working...