![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
| |
| | #1 (permalink) |
| | Re: Cannot debug WCF service When you attach to the WCF service, are you manually choosing the debugger engines to load? If not, the JIT debugger could be loading the SQL debugger automatically. -- Bryan Phillips MCSD, MCDBA, MCSE Blog: http://bphillips76.spaces.live.com Web Site: http://www.composablesystems.net "StanB" <StanB@discussions.microsoft.com> wrote in message news:B09855BA-9368-4E0A-BB77-839F9798D3C4@microsoft.com: > This worked fine with ASMX: set breakpoint before service call, hit F11, > debugger attaches and steps into the service code. > > I can't figure out why it does not work for WCF. > > First of all, debugger does not atomatically attach to the service. > > Secondly, if I attach manually it fails later in the code with the weird > message about execute permissions on sp_sdidebug. It appears that debugger is > trying to step into SQL code, however SQL debugger is turned off for all > projects. This maybe a separate issue, though. > > I really would like to switch from ASMX to WCF but I need to be able to > debug. It is weird because ASMX debug works fine in the same solution... |
My System Specs![]() |
| | #2 (permalink) |
| | Re: Cannot debug WCF service Thank you Bryan, T-SQL debugger was automatically selected. It still works funky and sometimes tries to step into other stored procedures, but it least I have a workaround.. I still don't understand what VS.NET does not automatically attach to WCF server.. "Bryan Phillips" wrote: > When you attach to the WCF service, are you manually choosing the > debugger engines to load? If not, the JIT debugger could be loading the > SQL debugger automatically. > > -- > Bryan Phillips > MCSD, MCDBA, MCSE > Blog: http://bphillips76.spaces.live.com > Web Site: http://www.composablesystems.net > > > > "StanB" <StanB@discussions.microsoft.com> wrote in message > news:B09855BA-9368-4E0A-BB77-839F9798D3C4@microsoft.com: > > > This worked fine with ASMX: set breakpoint before service call, hit F11, > > debugger attaches and steps into the service code. > > > > I can't figure out why it does not work for WCF. > > > > First of all, debugger does not atomatically attach to the service. > > > > Secondly, if I attach manually it fails later in the code with the weird > > message about execute permissions on sp_sdidebug. It appears that debugger is > > trying to step into SQL code, however SQL debugger is turned off for all > > projects. This maybe a separate issue, though. > > > > I really would like to switch from ASMX to WCF but I need to be able to > > debug. It is weird because ASMX debug works fine in the same solution... > > |
My System Specs![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| MS-DOS and debug | General Discussion | |||
| Debug | Vista General | |||
| debug.txt go away | Vista General | |||
| debug | Live Mail | |||
| Network Service Access to C:\Windows\Debug\Usermode | Vista security | |||