Unbind projects displaying "not under source control&qu

PACEGMBH · Post by **PACEGMBH** » Wed Nov 02, 2005 7:10 am

Hi,

we have bind a VS 2003 solution to vault to use the VS integration of vault. This solution contains some binded projects and some unbinded projects. These unbinded projects are not part of the vault repository. At these unbinded projects VS display the "not under source control" icon at any file and if we choose "View Pending Checkins" VS lists all files of the unbinded projects to check in.

What shall we configure to avoid VS display the "not under source control" icon at unbinded projects in a solution?

We use the vault 3.1.3 (3538).

Thank you

Post by **Tonya** » Wed Nov 02, 2005 9:43 am

Hello,

we have bind a VS 2003 solution to vault to use the VS integration of vault. This solution contains some binded projects and some unbinded projects.

How did you bind the solution to Vault?

Are the files that are in an unbound state checked out? Were these files originally bound to source code control?

What shall we configure to avoid VS display the "not under source control" icon at unbinded projects in a solution?

I am a little but confused with this question. Are you wanting the files bound to source code control again? Or are the "not under source control" icons creating a problem?

Thanks,

Tonya Nunn
SourceGear Support

PACEGMBH · Post by **PACEGMBH** » Thu Nov 03, 2005 2:31 am

Hi Tonya,

How did you bind the solution to Vault?

We bind the solution with VS "File | Source Control | Change Source Control. Subsequently we must adapt the sln file by hand.

Are the files that are in an unbound state checked out? Were these files originally bound to source code control?

No, these files (projects) are not checked out. These files (projects) are not under source control.

Are you wanting the files bound to source code control again?

We want these files (projects) not bind to source control again.

Or are the "not under source control" icons creating a problem?

Not the icons create the problem. The state of the files (projects). If we in VS go to "View | Pendig Checkins" the dialog want all these files and projects check in to the source control but these files are not under source control and so it is to remain. How we can avoid, that VS want to check in these files?

The VS solution looks in approximately so:

Solution XYZ (under source control = OK)
- Project 1 (under source control = OK)
  Project 2 (under source control = OK)
  Project 3 (under source control = OK)
  Project 4 (not under source control = OK but VS want check in)
  Project 5 (not under source control = OK but VS want check in)
  Project 6 (not under source control = OK but VS want check in)
  .
  .
  .

The projects 4, 5 and 6 and so on we want not to have under source control, we want not check in, we want not check out because these projects are in another repository different from the repository of projects 1, 2 and 3 and we want they not edit (this will do another team with another solution file).

Thanks,

Andre

Post by **Tonya** » Thu Nov 03, 2005 10:44 am

Andre,

I believe the problem you are experiencing is because you have the entire solution under source code control. You can't have the solution under source code control without all of the projects. This isn't necessarily a Vault liability, it's how VS.Net works.

We bind the solution with VS "File | Source Control | Change Source Control. Subsequently we must adapt the sln file by hand.

The fact that you are modifying the .sln file manually is probably how you have managed to get some projects under source code control and others not. If you add the solution to scc using VS.Net it's going to add all of the projects. If you want the solution under scc, then all of the projects will need to be added. Or you could not add the solution to scc and only choose the projects that you prefer.

Tonya

PACEGMBH · Post by **PACEGMBH** » Fri Nov 04, 2005 1:59 am

Hi Tonya,

thank you very much . I hoped it give another solution for the problem.

So i should remove the projects 4, 5, 6 and so on from the solution file.

Thank you

Andre

Post by **Tonya** » Fri Nov 04, 2005 9:21 am

That's up to you. You could remove these projects from the solution or just remove the solution from source code control and only have the projects that you prefer be integrated with source code control. If you decide to go this route, you can keep all of your projects uner this solution and everything should work properly.

Tonya