Hi Rainer,
Is it possible the files that don't get automatically checked out on edit
are already read-write on disk?
QueryEdit (the service called before an edit happens ) does not checkout a
file if:
- the file is already read-write on disk
- the editor/project missbehave and forgot to call QueryEdit before
modifying the file the first time, so the file is already dirty in memory
- in-memory edits are allowed (in Tools/Options/SourceControl/Environment
page), and the checkout is attempted but fails for some reason (e.g. because
the file is already checkedout exclusively by another user)
In the last 2 cases you should get the file automatically checked out when
you save it (again, if the editor does not missbehave and forgets to call
the QuerySave function)

Signature
Alin Constantin
This posting is provided "AS IS" with no warranties, and confers no rights.
>I set VSS 2005 to check out automatically when editing which works in 80%
>of
[quoted text clipped - 9 lines]
> I
> have to say, VSS is very slow and (see above) buggy!
Rainer - 26 Mar 2006 23:57 GMT
> Hi Rainer,
>
[quoted text clipped - 26 lines]
> > I
> > have to say, VSS is very slow and (see above) buggy!
Rainer - 26 Mar 2006 23:59 GMT
Hi,
Thanks for your help and sorry for my second reply post, I pressed too
quickly send msg ;-). To my problem, you were right, that many files didn't
have their Read-Only attribute set. When I set it manually, it worked again.
The funny part is, that I never changed them before, so VS or VSS changed
them once wrongly.
Thanks again, Rainer.
> Hi Rainer,
>
[quoted text clipped - 26 lines]
> > I
> > have to say, VSS is very slow and (see above) buggy!
Alin Constantin [MSFT] - 27 Mar 2006 00:56 GMT
Hi Rainer,
We have seen a case when VSS2005 leaves incorrectly a file read-only when it
should have been read-write, so I wouldn't be surprised if VSS2005 has
another bug for the reverse case (I'm assuming you haven't used the "Make
file writable" option for Get... or haven't edited files outside
VisualStudio with other editors that could have made the files writable
without letting you know this)
If you find a repro case of such bug in VSS (when it incorrectly leave a
file writable instead of letting it read-only), please let us know by
opening a bug at http://lab.msdn.microsoft.com/productfeedback and telling
us the scenario.
Thank you,
Alin Constantin
-------
This posting is provided "AS IS" with no warranties, and confers no rights.
> Hi,
>
[quoted text clipped - 44 lines]
>> > I
>> > have to say, VSS is very slow and (see above) buggy!