When I'm working on a VS.NET solution which has been added into VSS, I need
to checkout the solution & project.
Hence, no one else is able to check these files out and work on this
project.
I.e. when i'm working on a project in VS.NET, another person cannot do the
same.
Is there something wrong in what i'm doing?
Pieter Coucke - 09 May 2006 10:30 GMT
You're using the wrong Source Code Control software :-)
Take a look here: it's free, opensource, easy to use and to isntall, and it
works (!) and doesn't annoy or block the developers, and it is replacing the
defacto standard CVS: http://tortoisesvn.tigris.org/
> When I'm working on a VS.NET solution which has been added into VSS, I
> need to checkout the solution & project.
[quoted text clipped - 5 lines]
>
> Is there something wrong in what i'm doing?
LeAnne - 09 May 2006 10:38 GMT
But I have to use VSS.
Isn't there a way around this problem?
> You're using the wrong Source Code Control software :-)
> Take a look here: it's free, opensource, easy to use and to isntall, and
[quoted text clipped - 10 lines]
>>
>> Is there something wrong in what i'm doing?
Chubbly Geezer - 09 May 2006 10:59 GMT
Can you not just check out the modules that you need and not the whole
project.
> But I have to use VSS.
> Isn't there a way around this problem?
[quoted text clipped - 13 lines]
>>>
>>> Is there something wrong in what i'm doing?
Mehdi - 09 May 2006 19:42 GMT
> When I'm working on a VS.NET solution which has been added into VSS, I need
> to checkout the solution & project.
No. You only need to check out the file you want to work on. Checking out a
project is only needed if you want to add or remove a file or a reference
from a project. Once that's done, you can check the project back in. The
same goes for the solution.
> Hence, no one else is able to check these files out and work on this
> project.
>
> I.e. when i'm working on a project in VS.NET, another person cannot do the
> same.
Each developper should only check out the file they need to modify and
nothing else.