| Thread | Last Post | Replies |
|
| The specified procedure could not be found | 22 Dec 2003 07:17 GMT | 4 |
I had a Windows XP corruption and after running repair my Visual Studio .Net 2003 keeps on prompting "The specified procedure could not be found" whenever something needs to be checked in or out from source safe.
|
| Integration no longer working | 21 Dec 2003 14:00 GMT | 1 |
I have never had a problem with MSDev6 and VSS but after having to reinstall my machine I now have. Now when I choose "Open Workspace" and click the "Source Control" button to navigate to a project and choosing OK I just get a "No
|
| Archive --- Out of memory | 19 Dec 2003 14:41 GMT | 3 |
VSS6, SP6 on Windows 2000(SP3) When I archive the projects, I got "Out of memory". Can anybody tell me how to fix? Thanks.
|
| Move VSS to another server | 18 Dec 2003 18:39 GMT | 2 |
I think all of the following will be OK, 1. Copy all folder/files to another server. 2. Archive/Restore projects to another server. 3. Using RAR/ZIP all files/folder first ,then copy to
|
| Undoing Shadows | 17 Dec 2003 07:22 GMT | 1 |
I inherited the adminstration duties to our VSS (ver 5.0). I need to stop a Shadow that has been set up and have no clue as to how to go about it. Help! Thanks!
|
| SourceSafe permissions question | 16 Dec 2003 19:43 GMT | 3 |
Hoping there's a SourceSafe guru out there than can maybe suggest how we can solve a problem - or even maybe someone who could suggest a product similar enough to SS to make upgrading easy, but that supports the functionality we want.
|
| Needs to wrap the VSS | 16 Dec 2003 11:37 GMT | 1 |
Dear Friends, I have to do check-in/out and maintain history of my own files. I have to do with out using the VSS as an appliction.
|
| Upgrading to .net question | 16 Dec 2003 06:15 GMT | 1 |
We are using VB6 and sourcesafe 6.0. We are looking into upgrading to visual studio .net. Will sourcesafe from VS .net work with VB6? (can we leave one old development environment around that
|
| VSS 6.0 and Windows XP compatability | 15 Dec 2003 21:14 GMT | 4 |
Can anyone tell me if the VSS 6.0 client can run without problems on Windows XP Pro? Thanks, Duncan
|
| THIS NEWSGROUP SUCKS | 15 Dec 2003 20:51 GMT | 2 |
MICROSOFT: I posted a question here last week, and filled out the necessary information at the header. HELL I THOUGH that since this is moderated by MICROSOFT that it would be
|
| web deployment | 15 Dec 2003 20:42 GMT | 3 |
I am developing an ASP project, i have put all my sources to VSS, configured as webdeployment to my production server. After i have checkout my asp file to edit the code. Is
|
| SourceSafe automation and Status.dat filing left open | 15 Dec 2003 20:35 GMT | 3 |
I am running a SourceSafe automation tool that runs under a windows service. It creates an instance of a SourceSafe database object and peforms an open method at the beginning of its processing. If there is a system
|
| Merging Changes | 14 Dec 2003 03:07 GMT | 1 |
I'm having a problem with Branching my project and merging the changes back. From the VSS help file i have labeled the version 'beta 1' i have then made several changes / check ins to a cs file, example.cs. To get changes into the beta 1 version and for those changes to be incldued
|
| ASP.Net, Https and SourceSafe | 12 Dec 2003 18:24 GMT | 1 |
I began writing an ASP.Net project[VS.Net 2003] where I was communicating with IIS over http. I got a basic framework working and then I uploaded the project into SourceSafe.
|
| Yet another "unspecified error" message | 12 Dec 2003 18:02 GMT | 1 |
I have recently upgraded from dotNet2002 to dotNet2003 and upgraded from VSS-6.0c to VSS-6.0d. I am not able to open any project from source control, receiveing the dreaded "unspecified error". To date, have tried/verified:
|