VS.NET and ".svn" is a *non-issue*

I see a lot of confusion regarding VS.NET 200x and the
".svn" directories. While I hate the .svn directories
in general, VS.NET have absolutely no problem with
them. Read along.

The "problem" is IIS6 which M$ patched to disallow
paths containing dots and they did so for security
reasons (...oh my, what a hack). So waiting for
Whidbey won't do any good.

Now, this is only the DEFAULT behaviour and can be
easily worked around (as with other M$ security
patches ;-)

The first thing to try is enabling parent path
navigation:
http://support.microsoft.com/?id=332117

If that doesn't work, then get UrlScan 2.5 from
Microsoft and configure it with AllowDotInPath=1 in
the ini-file.

UrlScan is here:
(http://www.microsoft.com/downloads/details.aspx?FamilyId=23D18937-DD7E-4613-9928-7F94EF1C902A&displaylang=en)

NEVER EVER use any of the two suggestions above in
Internet-production environments.

That said, I hope Subversion will someday have
something better than the .svn directories. They are
eating my hard drive and driving my tools nuts.

My suggestions is: Do NOT add support for "_svn". Some
tools will probably have problem with those too.
Rather, focus on replacing the entire .svn scheme with
something less insane.

Thanks.

Yahoo! Mail (http://dk.mail.yahoo.com) - Gratis: 6 MB lagerplads, spamfilter og virusscan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 12 08:59:53 2004