DISQUS

Kingsley Joseph · 6 months ago

Technology may not be immune from the stubbornness of standards that no one feels inclined to change:
http://www.snopes.com/history/american/gauge.asp

jackbravo · 6 months ago

Está buenísimo.... backwards campatibility FTW!

madssj · 6 months ago

Two words. Backwards compatibility.

bones90 · 6 months ago

leaky abstraction?

Carlos Fonseca · 6 months ago

And probably none of those old apps work because of some other problem. But since it's not because of the files, it's cool xD

castis · 6 months ago

Backwards compatibility is only relevant for a few years. Everyone needs to stop sucking microsofts dick and learn what they're doing.

MSFanboy · 6 months ago

Surely this isn’t supposed to be a criticism of ASP.NET MVC 1.0 and/or the platform? I wouldn't even include this in the list of improvements to be prioritised for the next version.

It's an interesting point -- although it's purely academic because the developer can obviously choose any route and has no need to use a reserved directory name. If the developer did want to deliberately use a disallowed route, although there would never be any reason for doing so, but there are various options for a workaround. However, this is just a quirk of Windows which would never causes a problem for reral-life users or developers.

You don't even need anything other than Windows to see this in action. Just try to create a directory with a reserved name and you'll see it won't let you. Similarly, if you try to create a directory with invalid or impossible characters, e.g. a space " ", obviously this is also not be allowed. This doesn't affect real people, whether they are Windows users or developers, because they can just use a more sensible directory name -- for the same reason no web user would ever be affected by this.

dtobias · 6 months ago

This brings back ancient memories of typing things from DOS command lines like "copy con filename.ext" or "copy filename.ext prn" to create a text file from console input or print a text file, respectively. I assume these things still work from the DOS console in Windows, though it's been many years since I've tried them.

Mohamed_Meligy · 6 months ago

Have you tried it yourself?

I know it has something called "virtual Path Provider" which it overrides and eliminates physical file checking. Even if it doesn't you can do that yourself!

Henrique · 6 months ago

That's seriously f****d up.

ricka0 · 3 months ago

Try to create a view with any of the banned names (in MVC) and you get the following error:
---------------------------
Microsoft Visual Studio
---------------------------
FileStream will not open Win32 devices such as disk partitions and tape drives. Avoid use of "\\.\" in the path.
---------------------------
OK
---------------------------