RE: The .svn directory name causing trouble

The local project workaround works, but adds a level of complexity to
the debugging ASP.NET projects. To debug with the work around you must
"attach" to the ASP.NET worker process running your code. This is
non-trivial when running multiple worker processes on a remote server.

-----Original Message-----
From: D.J. Heap [mailto:dj@shadyvale.net]
Sent: September 24, 2003 5:19 PM
To: Branko Cibej
Cc: nick vajberg; dev@subversion.tigris.org
Subject: Re: The .svn directory name causing trouble

The workaround of changing web projects to local projects looks like it
would solve the problem completely, as long as you are not working on a
remote machine, of course. I haven't tried it, though.

It still might be a really nasty problem for people developing against
remote web servers, though...can someone with a remote development
server setup try it or post specifics?

DJ

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 25 03:52:18 2003