auto-checkout inconsistently works

( CVSSCC )

Type: Public Status:Closed Created: 14 May 04 05:00 Updated: 18 May 04 05:00

--> Jeanne Webb (user) at 18 May 04 05:00 writes

Will you please get me out of this tech support correspondence? I do not
want to be involved in it. Please email Brian Trexler directly at
brian.trexler@bentley.com. Thank you.
Jeanne Webb
-----Original Message-----
From: PushOk Software [mailto:support@pushok.com]
Sent: Tuesday, May 18, 2004 6:38 AM
To: Jeanne Webb
Subject: [pst140] auto-checkout inconsistently works
http://www.pushok.com/tickets_messages.php?id=140
Ticket group changed
from 'Common' to 'CVSSCC Proxy'

--> Igor Pushkov (admin) at 14 May 04 05:00 writes

First of all I should say that this must work (as it work for all
other users), so we just need to
find reason why it is not work in your case.
1. You should be sure that files have "read only" flag when they are
not checked out. In plug-in this control configuration option
"checkout files read only". It is switched on by default.
When you make something with these files outside the IDE you should be
sure that other CVSGUI is also configured to make files read only. In
WinCVS this controlled by the same option, but it is switched off by
default. Tortoise does not have appropriate option for this, but you
can use CVSREAD environment variable (you just need to crate it with
any value you have).
If CVSGUI client are not configured correctly for this option, any
action in them will remove read only flag for file.
Read only flag itself is very important, since IDE does not check file
state if file not read only.
2. Ensure that you do not switch on option "Allow checked-in files to
be edited" in VS .NET.
Let me know results.
P.S. Also I want to comment option "strict checkout status". It is
switched on by default, and plug-in consider file checked out only if
you apply "cvs edit" or checkout command. However you can switch it
off, and files modified outside ide (some trick) will also have
checkout state. Only one thing with this option, you should
explicitly call "refresh status" command to see changes in file
status. Please note this is not solution for you problem, just some
info if you want to modify files outside the IDE.

--> Jeanne Webb (user) at 14 May 04 05:00 writes

Visual Studio .NET integration with source control has a feature which
auto-prompts for checkout when someone attempts to edit the file and it is
not in a checkout state. Occasionally, this does not work and the IDE
allows edits without checking the file out. I've seen this behavior with
SourceSafe integration and it usually means the read-only bit on the file
has changed (tricking the IDE). For PushOK, it is not effected by the
read-only bit so I am wondering how it determines whether auto-prompting
should occur. I'm telling developers to explicitly checkout but it's easy
to forget. The ultimate problem is that when you do check-in for a
project, it doesn't check-in modifications for the files it doesn't
recognize as checked out (this is a big problem because some files never
get checked in unless going outside the IDE and through WinCVS).

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful