VS2003 / Stored Procedures & SourceSafe
-
When one wants to version control their stored procedures, they can do this fairly easily through the VS.NET IDE. As an FYI - If you care - Here is an old sample of how to do this http://weblogs.asp.net/fmarguerie/archive/2003/02/24/2880.aspx OK, all is good, now, if one MOVES the VSS database (in this case, to a different server), everything seems to go haywire. (Using VS .NET 2003, SourceSafe version 6.0d, SQL Server 2000) The problem seems to be rooted in the fact that there is no place to tell .NET IDE the new location of your srcsafe.ini file! The FIRST time around, (after some preliminary tasks), in server explorer window, you simply right-click on the "+-Stored Procedures" entry and select "Add To Source Control". A nice dialog comes up and you enter the location of your SS database, and your project name, etc. All SP's are added to VSS and bam! you are good to go. When you go here to check in and out, refresh, you are asked for a SourceSafe login, etc. Now, the VSS database has moved. So, when you try to log in to VSS it fails (just keeps popping up the login dialog until you click cancel). When you right click, Add and Remove from source control are disabled. I have tried clearing out the database, unchecking and re-checking "Enable Version Control" in Tools->Options->Database Tools->Server Explorer... nothing works! Somewhere, the OLD location of this VSS database is being stored and I need to change it. Any Help????? Thanks, -Len Miller "If I had eight hours to chop down a tree, I'd spend six sharpening my axe." -Abraham Lincoln
-
When one wants to version control their stored procedures, they can do this fairly easily through the VS.NET IDE. As an FYI - If you care - Here is an old sample of how to do this http://weblogs.asp.net/fmarguerie/archive/2003/02/24/2880.aspx OK, all is good, now, if one MOVES the VSS database (in this case, to a different server), everything seems to go haywire. (Using VS .NET 2003, SourceSafe version 6.0d, SQL Server 2000) The problem seems to be rooted in the fact that there is no place to tell .NET IDE the new location of your srcsafe.ini file! The FIRST time around, (after some preliminary tasks), in server explorer window, you simply right-click on the "+-Stored Procedures" entry and select "Add To Source Control". A nice dialog comes up and you enter the location of your SS database, and your project name, etc. All SP's are added to VSS and bam! you are good to go. When you go here to check in and out, refresh, you are asked for a SourceSafe login, etc. Now, the VSS database has moved. So, when you try to log in to VSS it fails (just keeps popping up the login dialog until you click cancel). When you right click, Add and Remove from source control are disabled. I have tried clearing out the database, unchecking and re-checking "Enable Version Control" in Tools->Options->Database Tools->Server Explorer... nothing works! Somewhere, the OLD location of this VSS database is being stored and I need to change it. Any Help????? Thanks, -Len Miller "If I had eight hours to chop down a tree, I'd spend six sharpening my axe." -Abraham Lincoln
If you are using integrated VSS, you could try unbinding the project or solution and re-binding. I know we had this same issue and I believe this is how we solved it.
-
If you are using integrated VSS, you could try unbinding the project or solution and re-binding. I know we had this same issue and I believe this is how we solved it.
Hi Darell, Thanks for the reply. The problem is, the Server Explorer window is un-related to any solution. I do not have a particular solution that is at issue, it is when I navigate to "Stored Procedures" under my server explorer window. Thanks, -Len Thanks, -Len Miller "If I had eight hours to chop down a tree, I'd spend six sharpening my axe." -Abraham Lincoln