Just to shed a little more light on the issue. M$ in their "security"
push has "fixed" IIS so that it cannot accept directory names with "."
in them. Just try it. Create a folder in your wwwroot called "test.test"
(put a file in there) and try and get to it. You'll get a page not found
error. They got burned bad by all the "..\..\winnt\system32\cmd.exe"
type hacks. VS.NET uses http to grab the files for web projects so that
remote and local web projects all work in the same way. What I'm saying
here is that M$ spent a lot of time and $$$ explicitly not allowing
folders with "." in them so expecting them to do anything about it is
completely out of the question.
-----Original Message-----
From: Steve Williams [mailto:stevewilliams@kromestudios.com]
Sent: September 24, 2003 9:49 PM
To: dev@subversion.tigris.org
Subject: Re: ".svn" directory name no good (in fact, it is worse than I
thought)
All this to work-around a deficiency in VS.NET with ASP.NET projects?
So what that Windows Explorer cannot create a folder such as '.svn'? It
can
be easily done via the command-line. Mention was also made of some
Win32
API functions that don't handle these directory names either, but I also
notice that no-one came up with specific function names.
Sly
----- Original Message -----
From: <kfogel@collab.net>
To: "Ben Collins-Sussman" <sussman@collab.net>
Cc: "Files" <files@poetryunlimited.com>; <james-tigris@jrv.org>;
<dev@subversion.tigris.org>; <roncannes@hotmail.com>
Sent: Thursday, September 25, 2003 1:51 PM
Subject: Re: ".svn" directory name no good (in fact, it is worse than I
thought)
> Ben Collins-Sussman <sussman@collab.net> writes:
> > It means I can't hand you my working copy. Why not? Because I just
> > happen to use "7ex983p" as my admin directory names. I like it.
> >
> > "Oh, you want to read my working copy too? I guess you'd better
> > temporarily configure your client to use that same admin directory
> > name. You can change your configuration back later."
>
> The other issue is that we treat this directory specially in certain
> situations -- for example, import ignores it, other operations may
> balk at working on it. If we also allow "_svn", then all those
> conditionals have to change, and now we have *two* reserved names
> instead of one. Third-party tools have to try *two* possibilities to
> determine if a directory is a Subversion working copy or not... Where
> does it end?
>
> Violate the 0-1-infinity principle, pay the price.
>
> ---------------------------------------------------------------------
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 25 07:53:39 2003