".svn" directory name no good (in fact, it is worse than I thought)

>>Do you:
>>1) Know a work-around for ASP.NET projects?
>>
>svn export

How is that going to help me? I need the project files to be under version
control, yet have the virtual directory point to it. Some guys at the
AnkhSVN project suggested creating a couple of batch files that you run
before and after starting VS.NET (to rename .svn into something else and
then back again.)

But that is really stupid, yet nothing else works properly. I assure you,
".svn" is going to bite a lot of Windows users.

>>2) Plan to change the directory name to something Windows can handle
>>properly in general?
>>
>Windows can handle it, the individual applications are the problem.

Applications that *ship* with Windows cannot handle it! Try creating a
".svn" directory using the File Explorer. It won't work.

Also, some of the Win32 SDK functions cannot handle it, at least not the
.NET version of those functions.

I see no reason why this shouldn't be changed this into something that works
properly ASAP (given that this name is fairly localized in the code base)

"wc.svn" for instance? For migration purposes, both .svn and wc.svn could be
supported for a while.

Please, fix this before it's to late. PRI 1 in my head.

_________________________________________________________________
Hotmail messages direct to your mobile phone http://www.msn.co.uk/msnmobile

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 24 23:16:24 2003