views:

29

answers:

1

Currently storing database of a large application with 2,000 stored procedures in Visual Studio Database Edition.

The problem I'm having is that when I try and edit a stored procedure, Visual Studio becomes unresponsive and it can take 30 seconds to type in a single keyword.

What I believe is that Visual Studio is attempting to auto recompile the project/solution. Does anyone know of a workaround, can this be switched off?

Has anyone experienced the same issue?

+1  A: 

I would take a look @ this post, which talks about a known issue with the *.dbml file and that the suppression of warnings doesn't always aid in the problem. The original poster does post a workaround.

Ben.Vineyard
Thanks BenIt kinds of looks at the symptom of the problem with the suppression of warnings. But it still appears that VSTS attempts to build the application on the fly.Would be nice to switch it off altogether. I'm still testing to see if it resolves the problem entirely.
Simon
No problem. Please follow-up to let me know if that works for you.
Ben.Vineyard
I'll give you kudos for what it's worth - would love to be able a final solution for this. Will be interesting to see if this is somthing that happens on VS 2010.
Simon