CVSProxy does not always launch checkout procedure when I edit a file

( CVSSCC , VS .NET, 2.0.x, WIN 2000/XP, CVS NT 2.x >= 2.0.58 )

Type: Public Status:Closed Created: 13 Oct 05 10:00 Updated: 18 Oct 05 10:00

--> Igor Pushkov (admin) at 18 Oct 05 10:00 writes

Unfortunately not, plug-in cannot detect the changing of file. To be
more true, plug-in can detect this, and it does this, but it cannot
transmit this information to IDE. That is because plug-in mostly is working
in passive mode - IDE asks and plug-in respond. Some mechanism exists in
SCC API, but VS .NET does not use it.
So, when you modify files outside VS .NET, you have to use
"Refresh status" command to make sure that status is displayed correctly.

--> GENETICS Chivers (user) at 18 Oct 05 10:00 writes

I assumed that CVSProxy behaves like WinCVS - detecting that a file is
modified even if it was modified outside the project. Anyway if I modify a
file outside the project(using Notepad) even with the "Strict checkout
status" option swithced off the file still appears as uncheked.

--> Igor Pushkov (admin) at 17 Oct 05 10:00 writes

Switching off this option you just allow plug-in correctly display status
for incorectly checked out files (externally modified). This is not affect
checkout dialog prompt, since it is not appear due to absense of read-only
flag (as I explain).
Read-only flag can be removed from file when you modify file externally,
sometime when you merging changes and so on. You need to find reason why in
your case files lost read-only flag. And finding this reason you can inform
us and we suggest best solution to avoid this.

--> GENETICS Chivers (user) at 17 Oct 05 10:00 writes

I disabled "Strict checkout status" but I still had a situation where I
start editing a project file that is not read-only and CVSProxy does not
detect and shows the checkout dialogue. When I try with another project
file which is read-only or when I modify the current file to be read-only
the check-in dialogue appears. So for us this issue still remains
unresolved

--> Sergey Korotkov (admin) at 14 Oct 05 10:00 writes

This can happens if you modify file externally, outside the VS .NET. The
main thing there is that file loses the read-only flag. VS .NET does not
check files status when they are not read-only and not ask plug-in to check
out file before editing.
You have two solutions for this problem. First is find reason why file
loses read-only attribute and avoid this in the future. Second is switch
off plug-in configuration option ŤStrict checkout statusť. In this case
plug-in will consider file as checked out not only when you explicitly make
this, but also if it is being modified somewhere outside. The last will at
least give you chance to check on all changes you made on your PC.

--> GENETICS Chivers (user) at 13 Oct 05 10:00 writes

When I open different solutions in VS.NET 2003 and start editing different
files from a solution's project the Checkout dialogue is not fired
always(thus allowing me to edit a file that has the status "not checked
out").
The issue that I have is that even if I modify a source control file this
change is not detected so when I commit my changes this file is not
commited.
This can cause serious problems if changes remain on local systems
uncommited.

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

CVSProxy does not always launch checkout procedure when I edit a file