Andrew!

> I do have some CVS clients installed, such as the PushOK client, and WinCVS, 
> but that shouldn't matter, right?

Just to check could you please send us the screenshot of the Visual
Studio main menu with the "commit" command you're choosing?

Do you have problems  (files became read-only) if you commit outside
the VS, e.g. using TortoiseSVN or Subversion standard client svn.exe?
Please check.

Thank you!

On Sun, Feb 15, 2009 at 8:38 PM, AndrewC <andrewcus...@gmail.com> wrote:
>
> Hi Olga-
>
> Thanks for replying.
>
> I am using v1.6.1 of the Visual SVN plug-in.
>
> I also have TortoiseSVN installed: v1.5.7, Build 15182 - 32 Bit ,
> 2009/01/24 22:44:13
>
> These are the only SVN clients I have installed. I do have some CVS
> clients installed, such as the PushOK client, and WinCVS, but that
> shouldn't matter, right? I have not used any of them on any project I
> have in SVN.
>
>
> The files that become Read-Only are from a Visual Basic Windows Forms
> application. They are .VB files, and both the code files and the form
> designer files become Read-Only, as do Class files (plain code files).
> However, I have just tested with an .XML file and the same issue
> occurs. It now appears that all files of all types have the issue
> occurring.
>
>
> There are no VisualSVN* files at all in my C:\Users\< my username>
> \AppData\Local\Temp folder. I am on Windows Vista Business, 32-bit.
>
> My server is running VisualSVN Server v1.6.3.
>
>
> Thanks,
>
> -Andrew
> ------------------------------------------------------------------------------------------------------------------------------------
>
> On Feb 15, 8:34 am, VisualSVN Support <supp...@visualsvn.com> wrote:
>> Hi Andrew!
>>
>> Please provide more details:
>>
>> *what version of the VisualSVN do you use?
>>
>> *do you have any other SVN client installed except VisualSVN,
>> TortoiseSVN, svn.exe?
>>
>> >I now see that another  file is Read-Only
>>
>> What type is this file?
>>
>> There should be VisualSVN log files in your temp folder (somewhat like
>> "C:\Documents and
>> Settings\<username>\LocalSettings\Temp\VisualSVN-2007-06-02-00-01-416.log"
>> on Windows XP and
>> "C:\Users\<username>\AppData\Local\Temp\VisualSVN-2007-06-02-00-01-416.log"
>> on Windows Vista). Could you please send us the last one?
>>
>> Thank you!
>>
>>
>>
>>
>>
>> On Fri, Feb 13, 2009 at 6:35 AM, AndrewC <andrewcus...@gmail.com> wrote:
>>
>> > Hi-
>>
>> > I am using the VisualSVN add-in in Visual Studio 2008. I have always
>> > used Copy-Modify-Merge, *never* locking files.
>>
>> > Today, all of a sudden, when attempting to Commit a file, I received
>> > the following message in a dialog box:
>>
>> > "The file Form1.vb, which you attempted to edit, is read-only on disk.
>> > Would you like to make the file writeable or edit it anyway?"
>>
>> > I went to Windows Explorer and confirmed that Read-Only had, indeed,
>> > been set somehow. I un-set it. I was then able to Commit my changes;
>> > however, the next time I tried to Commit, I received the same message.
>> > It is appearing now every time I try to Commit this file. Other files
>> > in the same solution did not have the problem at first.
>>
>> > I checked the VisualSVN Properties on the file, and there is nothing
>> > set there.
>>
>> > Upon exiting and re-starting Visual Studio, I now see that another
>> > file is Read-Only and has the lock icon on its Tab; and now every time
>> > I Commit a file, it becomes Read-Only upon Committing.
>>
>> > What is going on? I can't work this way.
>>
>> > Please help.
>>
>> > Thanks,
>>
>> > -Andrew
>>
>> --
>> Olga Dolidze
>> VisualSVN Support- Hide quoted text -
>>
>> - Show quoted text -
>



-- 
Olga Dolidze
VisualSVN Support

Reply via email to