Tuesday, July 17, 2012 9:11 AM
I run Visual Studio 2010. I created a CLR SP (VB.NET), debugged it locally (with a local SQL 2008 database) and live was good.
Then we upgraded to SQL 2012. I was unable to deploy my CLR to the upgraded DB and after some searching I installed something like 'SQL Database tools'. Now I could create a new Sql Server Database Project which supported SQL 2012.
Deploying (sorry, publishing) goes well but... when I try to debug my VB.NET CLR SP the only thing I can debug is the T-SQL code. The SP is called from the SQL-testscript, executes fine and gives results. But I can only debug the testscript.
This must be some setting I am not aware of so please help!
Thanx in advance!
- Edited by FOSDC Wednesday, July 18, 2012 7:40 AM
Thursday, July 19, 2012 1:02 PM
Some additional info. I just created a new Sql Server Database Project, added a SP CLR (VB) and a testscript. Same result, I can only debug the testscript (T-SQL).
I set breakpoints in the SP-code and none in the T-SQL code. However, the code 'breaks' at eacht SQL-statement and not in the SP. I do however see the results of the SP so it does run.
Does really no one know what I am doing wrong and/or which settings to change?
Monday, July 23, 2012 7:05 AM
Wednesday, August 01, 2012 9:02 AM
Thanx for reading and responding. However, I found that particular article and tried it. I found lots of other articles but none seems to cover my problem.
This worked with the 'old' Sql Server Database Projects. I know so because I debugged CLR every day. The problem seems to be something with the new Sql Database tools installation which provides me with a SQL Server Database Project in which I can choose between SQL Server 2005, SQL Server 2008, SQL Server 2012 and SQL Azure.
Therefor, this is (unfortunately) not a working answer...
Monday, September 10, 2012 9:17 AMUnfortunately still no fix. Am I really the only one with this problem?