Tearing my hair off in despair now after hours of fighting and searching the Internet. I am trying to debug a simple CLR method. Configuration: Visual Studio 2010, SQL Server 2008 R2 Express, Vista Business SP2. I am a domain user, but the local administrator on the computer and the system administrator of the local instance of SQL Server. I created a new VS database project, pointed it to my db connection string (I used this db before), and then asked if I wanted to enable debuggig for the connection, to which I answered yes.
I checked that the project is rolling out perfectly (you can see the assembly and its procedure in SQL Server Management Studio), and I can call it just in SSMS. Then I added the same code EXECto the Test.sqlscript in my db project and marked it as a debugging error by default script. Then I set a breakpoint both in Test.sqland in the CLR code.
But when I press F5, I get the following output:
Canceled by user.
Auto-attach to process '[2144] sqlservr.exe' on machine 'DAWID-PC' succeeded.
The thread 'dawid-pc\sqlexpress [54]' (0x13c4) has exited with code 0 (0x0).
The thread 'dawid-pc\sqlexpress [54]' (0x13c4) has exited with code 0 (0x0).
The thread 'dawid-pc\sqlexpress [56]' (0x109c) has exited with code 0 (0x0).
The thread 'dawid-pc\sqlexpress [56]' (0x109c) has exited with code 0 (0x0).
The program '[2144] sqlservr.exe: dawid-pc\sqlexpress' has exited with code 0 (0x0).
And my debugging session ends right there.
It works for me c:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\Remote Debugger\x86\msvsmon.exe; I see that a message MyDomain\MyUsername connected.appears every time I press F5 in Visual Studio. I do not have a firewall running on my PC and no antivirus software is installed.
, ? - , , , ...