A possible bug: renaming a stored procedure not immediately commited

That's a very good catch. It happens either via refactoring or just renaming the script directly via the SQL script.

It happens because when you create an object in the project (either through the Add New Item command or Importing a Database Schema), a file automatically gets generated on the file system. When you rename the object, we do not rename the file underneath it.

The T-SQL editor in the project system always shows the file name in the tab.

So, that's the explanation :)

Hope this helps explain why you are seeing this. If you'd like to log a bug or suggestion on this or anything else, you can do so at http://connect.microsoft.com/VisualStudio

-Tom

tomsmi at 2007-9-10 >