Editable files appear checked in, inside Visual Studio

( CVSSCC )

Type: Public Status:Closed Created: 11 Apr 05 04:00 Updated: 12 Apr 05 04:00

--> Igor Pushkov (admin) at 12 Apr 05 04:00 writes

Plug-in cannot control you, and as result you can remove write
protection or modify file externally without making "cvs edit" (which
means checkout in terms of VS.NET).
As result you have files that "improperly checked out", or just
externally modified. From some point of view this is normal, since CVS
allows this. However this is not a good practice, since nobody will
know that you edit file (without cvs edit). So you have two options to
solve the problem:
1. Always use "cvs edit" for external modifications.
2. Switch off plug-in option "Strict checkout status". This way you
allow plug-in to consider externally modified files (without cvs edit)
as checked out. By default plug-in consider "checked out" only
properly modified files.

--> Colin Bell (user) at 11 Apr 05 04:00 writes

Occasionally, certain files checked out for editing appear as though they
are checked in, inside Visual Studio. Even though these files are
write-enabled, and I get the 'CVS Commit' option in the Explorer context
menu, I see the lock symbol in Visual Studio. These files do not appear in
my pending checkins dialog, and do not get checked in when I attempt to
check in the entire solution tree. If I attempt to commit via Explorer,
everything works as expected.

I know of one other person experiencing the same problem as me, and we both
have Visual Studio 2005 Beta installed. However, the problem exists in both
Visual Studio 2003, and the 2005 beta.

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

Editable files appear checked in, inside Visual Studio