Problems adding project to source control

I have a multi-project .sln file that doesn't allow me to put one
specific subproject under source control. I get error messages like
"The project C:\Documents and Settings\mblakeknox\My Documents\Visual
Studio Projects\CTI\Client\RBSNB\RBSNBCTISERVER\RBSNBCTIServer.csproj
cannot be added to source control. In folder C:\Documents and
Settings\mblakeknox\My Documents\Visual Studio
Projects\CTI\Client\RBSNB\RBSNBCTISERVER, it overlaps a project that is
already bound to source control at a lower root. To avoid this problem,
add the project from a location below the binding root of the other
source controlled projects in the solution." when I try to add the
project to source control using File|Source Control|Add Selected
Projects to Source Control.

I had added the project to source safe using the Source Safe explorer
but have deleted it now. I then added the project to Visual Studio
using Add | Existing Project then tried to use File|Source Control|Add
Selected Projects to Source Control and am getting the above error.

Is there a way to obtain some specifics on what specific files/folders
Vsual Studio thinks are overlapping?

I have tried using Change Source Control but keep an error
message about supporting only one connection when I try to close the
Change Source Control dialog. The documentation talks
about using change source control to bind to the "unified root" but
VS/VSS don't seem to allow me to do this and only one of the existing
bindings maps to the unified root.

The folder structure on disk and in vss are the same while the VStudio
folder structure is simpler. Here's what the disk and vss structures
look like:

CTIServer
Client
Client A
Client A.sln
Client A adaptors
Client A adaptors.csproj
Client A interfaces
Client A interfaces.csproj
Client A setup
Client A setup.vdproj
Client B
Client B.sln
Client B adaptors
Client B adaptors.csproj
Client B interfaces
Client B interfaces.csproj
Client B setup
Client B setup.vdproj
Server
Server module 1
Server module 1.csproj
Server module 2
Server module 2.csproj
Switch
Switch 1
Switch 1.csproj
Switch 2
Switch 2.csproj

The Solution Explorer layout has a solution file with all the poject
files under the root of the tree.

The concept is that there's a .sln file for each client. Each sln file
includes that client's specific code plus a selection from the Server
and Switch trees.

My problem is that I haven't been able to put the Client C
adaptors.csproj under source control. But there are 3 other clients
that seem fine.

Any ideas?

Thanks

Mike

.

Relevant Pages

  • Adding project to source control
    ... specific subproject under source control. ... already bound to source control at a lower root. ... Client A ... The concept is that there's a .sln file for each client. ...
    (microsoft.public.vsnet.general)
  • Putting a C# project under source control
    ... specific subproject under source control. ... Client A ... Switch ... The concept is that there's a .sln file for each client. ...
    (microsoft.public.vstudio.sourcesafe)
  • Re: Web site vs Web Application Project
    ... source control, I do not include the SLN file. ... solutions depending on which hat he's wearing that day) and just add the ... to do so because of a communal SLN! ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: VSS Project binding issue?
    ... The error message indicates that some files are outside the "root" project ... This is known behavior for Visual Studio projects where for source control ... Microsoft Online Community Support ... nature are best handled working with a dedicated Microsoft Support Engineer ...
    (microsoft.public.vsnet.ide)
  • Self Generated SSL Certificate
    ... If I generated a self signed certificate, is there any way that I can install that same certificate on the client of register the authority so that I don't get any warnings or issues about the authority of the certificate? ... I know I can simply bypass these warnings with a browser based page but I am affraid that my source control client will not be so willing to bypass this message. ...
    (microsoft.public.windows.server.security)
Loading