Andrew! Thank you for posting this information!
We'll consider adding the article on this problem in our Knowledge Base. On Thu, Feb 26, 2009 at 3:53 AM, AndrewC <andrewcus...@gmail.com> wrote: > > PROBLEM APPEARS TO BE RESOLVED - 02/25/2009 > > OK, as I noted above, in one of my first posts on this issue, I have > the PushOK SCC Proxy installed, *in VS2005 only*, for CVS source > control. The PushOK SCC Proxy includes a Windows Service that > apparently monitors all Source Control check-ins/check-outs, or in SVN > terminology, all Updates and Commits. I knew that this Proxy monitors > CVS actions. Presumably, because CVS can work like Visual Source Safe > --that is, it can Lock files when you check them out, by setting the > Read-Only bit on them-- the Proxy monitors Check-ins and sets the Read- > Only bit on all files after check-in. I knew this, but had forgotten > because I stopped using CVS/PushOK almost a year ago when it blew up a > major project I was working on for a client. > > What I *didn't know* is that there is a setting in the PushOK > configuration dialog that allows you to also monitor *SVN* Check-ins/ > Commits-- AND IT IS ON BY DEFAULT! In spite of the fact that the > PushOK product I purchased ostensibly only supports CVS, not SVN!! And > the fact that I never installed the thing into VS2008... > > > Long story short- I went into the PushOK settings: START->(All) > Programs->PushOK Software->SCC RW Monitor -- then uncheck the checkbox > next to "Monitor files controlled by Subversion". Then click OK. > > If you are still using the PushOK Proxy for CVS, as I am for > occaisonal maintenance of my older apps/websites, you can leave the > other 2 checkboxes checked. I left them checked, and am not having any > problems with SVN at the moment. > > > Olga- > > PLEASE PLEASE PLEASE add this to your FAQ, and to your Tech Support > notes. I cannot imagine I am the only person to have this problem, as > I came across quite a few mentions once I understood what the problem > was. And I *did* mention to you, in my second post above, that I had > the PushOK client installed. > > I would even go as far as to say that your Tech notes should instruct > Techs to check for this issue *first* when a user reports an issue > with files becoming Read-Only when they shouldn't; or possibly > second, after checking the SVN Properties. > > > Thanks for your help, everyone. I will certainly post again if the > issue reappears, but for now I am happy, with crossed fingers. ;-) > > > -Andrew > -- Olga Dolidze VisualSVN Support
