[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Visual Studio build fails because .svn\wc.db is open

From: Andy Levy <andy.levy_at_gmail.com>
Date: Fri, 10 Feb 2012 17:00:35 -0500

On Fri, Feb 10, 2012 at 16:45, Daniel Becroft <djcbecroft_at_gmail.com> wrote:
> On Sat, Feb 11, 2012 at 3:43 AM, Bob Archer <Bob.Archer_at_amsi.com> wrote:
>>
>> > For a variety of reasons the intent is for me to commit only compiled
>> > code to a
>> > repository.  I admit I am a relative newbie to using a repository and
>> > TortoiseSVN.  What I have done so far is:
>> >
>> > - Create a directory in my repository under /branches (as I was
>> > directed)
>> > - Checkout the empty branch to my populated build directory
>> > - SVN Commit the directory to the repository (which uploaded all the
>> > files)
>> >
>> >       At this point if I try to build again, I get the message:
>> >
>> > Error 5       Unable to delete file "C:\Users\.....\Test
>> > Server\\.svn\wc.db".
>> > The process cannot access the file 'C:\Users\.....\Test
>> > Server\\.svn\wc.db'
>> > because it is being used by another process.
>> >
>> > So presumably that's because TortoiseSVN has wc.db open and thus Visual
>> > Studio can't delete it to repopulate the folder.  How do I work around
>> > that?  Is
>> > there a better way to accomplish this?
>> >
>>
>> Move to 1.7... the .svn folder is only in the root working copy folder in
>> that case so you won't have an issue.
>>
>> BOb
>
>
> If the original poster is getting an error regarding wc.db, then they are
> already on 1.7.

And apparently their source is not versioned, but the compiled artifacts are.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2920739

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-02-10 23:01:19 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.