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


From: Matthew Hawkins <darthmdh_at_gmail.com>
Date: 2006-03-01 02:17:26 CET

On 3/1/06, Branko ╚ibej <brane@xbc.nu> wrote:
> Matthew Hawkins wrote:
> > He always uses subversion with the regular .svn directories and has
> > simply made the Bin directory any time VS.NET <http://VS.NET> has
> > complained, and has never had any problem.
> Which version of VS.NET are we talking about? We've been told the
> problem went away with VS.NET 2005, but is there in earlier versions.

Sorry, I should have been clearer. I'm using 2003.

> If this can be shown to always be the case (I've only tested it
> > successfully here) then perhaps this is a better thing to do than the
> > ugly hack which for some clients (eg, tortoisesvn) requires a system
> > reboot; automatically create the Bin directory if a VS.NET
> > <http://VS.NET> web service is detected on checkout.
> Um. Sorry, I'm dense -- do you expect Subversion to detect VS.NET web
> services?

Yes ;-) The logic would go: If there is an .asmx and web.config file being
checked out in the same directory, create a Bin dir if none (will) exist.

However, I appreciate that if this problem has been resolved in a newer
version of Visual Studio then there's little point in switching to a
different workaround - just wait for everyone to upgrade & deprecate the
hack altogether. I just wanted to pass on that there could be another way
to work around this problem, retaining normal filesystem namespace &


Received on Wed Mar 1 02:18:02 2006

This is an archived mail posted to the Subversion Dev mailing list.