How can I avoid automatically connecting to T-SQL for debugging in Visual Studio 2008?

When debugging the websites I'm working on, I try to use Attach to Process instead of F5 to start debugging (since the site is already included in Firefox). However, sometimes I get the following error:

EXECUTE permission is denied to the object 'sp_sdidebug', database 'master', owner 'dbo'.

I know this is due to the connection of the debugger for T-SQL, and not just to the managed code (see this blog post for further explanation on this).

I hope it’s possible to install somewhere to avoid being tied to T-SQL in the first place, instead of remembering to go to reset that installation every time I attach.

So, here is the real question: Does anyone know how I can change the default behavior for Visual Studio 2008, so that when I connect to a process through the debug menu, it does not automatically join T-SQL, but only for managed code? That is, how can Studio be set up to remember not to join anything other than managed code?

FYI, if there are specific settings for the project, I am using a C # web application project.

+3
source share
3 answers

You can change the debugging mechanisms used to join the process by clicking the "select ..." button in the "attach to:" line of the attach dialog box.

" " , , T-SQL .

, , , Visual Studio .

+2

( , : "" "Alt-F7" "Alt-Enter" "Project/xxxx Properties" ), [] " SQl"

+1

VS, , , .

, SQL.

0

Source: https://habr.com/ru/post/1699059/


All Articles