Hello everybody,
did you note when you rename a stored procedure, and then open it, old name is displayed in tab
A possible bug: renaming a stored procedure not immediately commited
Hot Topic
- LoadTest.ThresholdExceeded problem
- differences between msf agile and formal?
- TF53010: An unexpected condition has occurred in a Team Foundation componen
- Aggregate WI integer fields
- How to login as a different user to Team Server?
- How to setup permissions?
- Reports in Team Explorer : 403 error
- Using Project Level Groups
- Centralize suppressions (no more attributes) in VS2005
- Possible to unmap a file in a workspace?
VS Team System
- About Security
- Exclude low certainty levels
- Unassociate Project Server project from TFS project
- Are standard Roles in MSF Agile enough for my Project???
- Is the december CTP the final release of MSF for CMMI?
- Workspace issue
- Web Test Recorder : Can you turn off the replacement of hidden fields by context parameter placeholders?
- Unexpected error when adding Web Part to TFS Project site
- Setting Alerts: SMTP Server Requires Authentication
- TfsReportDS Error
A possible bug: renaming a stored procedure not immediately commited
10wattmindtrip
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
nhaas