Visual Studio .NET issue

( CVSSCC )

Type: Public Status:Closed Created: 25 Feb 05 02:00 Updated: 25 Feb 05 02:00

--> Igor Pushkov (admin) at 25 Feb 05 02:00 writes

) CVS Server version 2.0.58d
This one makes sense. Version 1.2 not recommended to use with 2.0.58d.
The new 2.0.0 will be compatible with that server.
However you can try the following solution. Go to the plug-in options
and switch on option "my server support 'ls' command".
Let me know if this not help.

--> Ian Porter (user) at 25 Feb 05 02:00 writes

Correction cvs proxy version v.1.2.050211

--> Ian Porter (user) at 25 Feb 05 02:00 writes

Igor,
CVS proxy version v.1.2.041125
CVS Server version 2.0.58d
Regards,
Ian Porter

--> Igor Pushkov (admin) at 25 Feb 05 02:00 writes

Few questions:
1. Which version of CVS PROXY you use?
2. Which version of server you use?

--> Ian Porter (user) at 25 Feb 05 02:00 writes

Our team has managed to successfully set up a CVS repository for a .NET
project. We can all see the same version and there is no branching. When
one user updates a file, we can all see the latest version. However, when
one of us adds a file - the file does not appear for the rest of us if we
user "Get Latest Version" within VS.NET. If we use tortoise CVS we can get
the file from CVS but PushOK won't let us have it. No matter what the
writer of the file does - checks out the project file again, adds the file
again checks everything back in - the other users can't get the file in
question. What we end up having to do is individually checkout the project
file and add the file in question. Is there some configuration issue we are
missing to set up PushOk with VS.NET and CVS?

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

Visual Studio .NET issue