Settings the properties doesn't need to be done on the server machine. You can do it on your developer machine in your working copy.
I suggest using the command line if you don't use TortoiseSVN : svn propset svn:needs-lock 1 C:\WorkingCopy\filename (set the property on the file) svn commit C:\WorkingCopy (commit your changes) Ezeckiel On Jan 8, 5:19 am, Caner <[email protected]> wrote: > Hi, > Thanks Peter, I'll keep in mind, and will suggest my team to rediscuss > the model considering your situation. > Thanks Ezeckiel, I've checked the properties dialog again. The problem > is that, in our server which is not used as a PC by any team member, > TortoiseSVN is not installed. Hence, VisualSVN->properties does not > trigger TortoiseSVN's properties dialog which contains svn:needs-lock > option, but its own simple dialog. Or, probably, you meant VisualSVN > plugin-> properties at Visual Studio. I have found what you stated at > Visaul Studio->VisualSVN->properties. > > Regards > > Caner > > On Jan 7, 6:33 pm, Ezeckiel <[email protected]> wrote: > > > The VisualSVN->Properties menus bring up the TortoiseSVN properties > > window. It's the same as TortoiseSVN->Properties in windows explorer > > if you use TortoiseSVN as subversion client. > > You can use still followed the instructions given > > athttp://visualsvn.com/support/topic/00016/guideonceyou have opened > > that window. > > > Ezeckiel > > > On Jan 5, 9:38 am, Caner <[email protected]> wrote: > > > > Hi, > > > OK, I've found what is going wrong. I'm not using Visual Studio > > > (other IDE's) hence not VisualSVN plugin which I'm not familiar to. > > > Hence, I tried to do it on VisualSVN Server. That's why the menus I > > > was checking appeared totally different. So anyone who desires to set > > > svn:needs-lock should try to apply the instructions on Visual Studio's > > > VisualSVN plugin. > > > > Regards. > > > > Caner
