In a previous posting (see Removing SQL Version Control,
Aug. 2, 2003) DavidM asked how to keep VS.Net from adding
the various dt_* stored procs to databases opened via
server explorer or how to remove the procs.

We have a VS.NET database solution & project on a common
share accessed by three developers.  I created the
project and we can all access it ok but when others work
on sql scripts they are shown as being checked out by me

The files/folders in a Web Project located under MS Visual Source Safe 6.0
are getting changed to .vsss.tmp extension
[Ex: File test.asp changed to test.asp.vsss.tmp].The reason is unknown.
This is causing many problems ( such as file test.asp as missing in the

In Visual Studio .Net 2003, in my solution, I added an existing project that
was in another directory. I then checked that project out of SourceSafe from
VS.Net.. When I opened the Visual SourceSafe 6.0, I found that a project was
created instead of checking out from the existing ...

We have several licenses for Visual Studio 6.0 Enterprise.
We recently bought several Upgrades for Visual Studio .NET
Professional.  The question is:  After we upgrade, are we
still licensed to use VSS from the Visual Studio 6.0 or not?

I am looking into putting store procedures into SourceSafe and I just
wondered if the version of SourceSafe matters as I am using Version 5.0 with
Visual Studio .NET
If this is the wrong newsgroup please also point me to the right one

I just noticed that in one of our databases we have a
project that has duplicate folder names.  Not sure how
this happened.  I didn't think that duplicate folder names
were allowed?  Should we be concerned or is this normal?

I need to change the GUID in a VSS 6 database.  In older
versions of VSS (5.0 and maybe earlier), this could be
done with the guidscan.exe utility, which would modify the
GUID in file um.dat.  Version 6, though, apparently has

We have developed a tool in C++ that tracks check-outs/and
check-ins using the SourceSafe Event hook interface.  We
would like to convert this tool to a .NET object to take
advantage of built-in SQL support.  However, when

I had a recent installation of VS.NET 2003 Enterprise
Architect. Afterwards installed VSS 6.0d. The VSS 6.0d
client works fine, no bug.
But when opening a project that was created by another

I have a project which utilizes an xml file for certain parameters needed to
run the exe file generated by the project.
That file doesn't need to be version-controlled but it would be nice have it
contained within SS as sometimes, certain parameters may be added. Is there

I'm writing a Visual Studio Add-In and need to know the current
servername/binding of the loaded projects to the SourceSafe-database.
I can see this information via the menu "File / Source Control / Change
Source Control...": the column "Server Name" shows me the correct SourceSafe

Has anyone run into this before, and if so, is there any
way around it?
I submitted a bug report to Microsoft, but I need a
workaround for this as soon as possible.

I am wondering whether the shadow project is recursive. What I mean exactly is:
1. I have set X as shadow folder of $projectX in VSS.
2. Now I create a new sub-project $projectX/Y under $projectX in VSS.
3. Will the new project get reflected in the shadow folder?

Hi, I need a little clarification on which is the most
recent version of SourceSafe..  I currently have version
6.0d - the Microsoft site is advertising 6.0c (SP6) as
the latest version, though refers to versions 6.0c and