by chance do you have SVN:NeedsLock set ?

On Thu, Feb 26, 2009 at 11:51 AM, AndrewC <andrewcus...@gmail.com> wrote:
>
> Olga-
>
> I just tried that, and it didn't fix the problem.
>
> I closed Visual Studio, and uninstalled VisualSVN.
>
> When I went to delete the "С:\Program Files\VisualSVN\" folder, it was
> already gone.
>
> I then ran both VS2005 and VS2008, closed them, and re-installed
> VisualSVN.
>
> Finally, I opened Windows Explorer, and manually removed the Read-Only
> attribute from all the files in the Solutions that have the problem..
>
>
> Immediately upon changing any file, then Committing it to the
> repository, then attempting to make *any* change to the file in Visual
> Studio, such as adding a space to the file, I receive the same Read-
> Only error message.
>
>
>
> I was able to use VisualSVN for a full month in Evaluation mode after
> originally installing it. Interestingly, the problems showed up a week
> or two after I purchased and Registered VisualSVN. I wonder if there
> is any connection?
>
> I noticed that, upon removing and re-installing VisualSVN, I did not
> have to re-enter my License Code- VisualSVN was already registered; so
> clearly, VisualSVN is keeping the information somewhwere on my PC,
> most likely a Registry entry. Perhaps the problem is living through
> the removal and re-installation the same way?
>
>
> Some more information for you: I tried editing a *.vb code file in
> NotePad, then Committing it from WIndows Explorer using TortoiseSVN.
> As soon as I Committed the file, it was set to Read-Only. Note that
> the file was not even open in Visual Studio during this test. This
> makes me suspect the problem might be in TortoiseSVN; I will look into
> that.
>
>
> Please let me know if you come up with anything I can do to fix the
> problem; it is becoming a serious issue, as I am now unable to add my
> current project to SVN due to this issue continually wasting my time.
>
>
> Thanks,
>
> -Andrew
> -----------------------------------------------------------------------------------------------------------------------
>
>
> On Feb 25, 10:24 am, VisualSVN Support <supp...@visualsvn.com> wrote:
>> Andrew,
>>
>> Could you please try to reinstall VisualSVN plugin?
>>
>> Please try the following steps (step by step):
>>
>>  - uninstall VisualSVN,
>>  - delete folder "С:\Program Files\VisualSVN\",
>>  - run Visual Studio and exit,
>>  - install VisualSVN.
>>
>

Reply via email to