![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
|
Welcome to Vista Forums we are your forum to discuss Windows Vista x64 and x86 systems. Whether you need help or just want to post an idea you have on Vista, this is the forum for you.
br> br> |
| |||||||
| | Thread Tools | Display Modes |
| | #1 (permalink) |
| Guest | 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... |
| | #2 (permalink) |
| Guest | 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... > > |
| |
| |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| how to debug vbscript? | Gene. | VB Script | 16 | 07-21-2008 09:44 PM |
| debug.txt go away | keepout@yahoo.com.invalid | Vista General | 6 | 05-20-2008 11:02 PM |
| debug | derek wilkie | Live Mail | 3 | 04-08-2008 04:57 PM |
| Network Service Access to C:\Windows\Debug\Usermode | Will | Vista security | 1 | 10-29-2007 03:17 PM |
| Re: Debug woes | Jason Dolinger | Avalon | 3 | 01-10-2006 03:52 PM |