E
Eric Twietmeyer
Hi,
Does anyone know why starting with VS.NET 2002 (and same with 2003) it is no
longer possible to browse to a directory that has "ept" as part of the path?
It worked fine in Vc 6.x. My initials and user name happen to be "ept", and
so I have directories with that name. It is no longer possible to browse to
any subfolder and therefore open any file under an "ept" directory. I can
browse to such a folder using explorer and then drag a project or plain file
into the IDE. Or, if I had already opened the file in such a directory and
it then appears in the recent file / project list, then I can open it from
there. I simply can not browse to it from the open file / open project
dialog.
I have found that "EPT:" was apparently some kind of special printer port in
very very early DOS days. So I guess at one time in the distant past it
made sense to not allow directories with this name (like I guess COM1 etc.
still are). As mentioned, the restriction did not exist in Vc6, and Windows
Explorer has no problem browsing to a directory called "ept" or a subdir of
it.
Or perhaps I am the only person to use "ept" as a directory name???? I find
that hard to believe....
-Eric P. Twietmeyer
Does anyone know why starting with VS.NET 2002 (and same with 2003) it is no
longer possible to browse to a directory that has "ept" as part of the path?
It worked fine in Vc 6.x. My initials and user name happen to be "ept", and
so I have directories with that name. It is no longer possible to browse to
any subfolder and therefore open any file under an "ept" directory. I can
browse to such a folder using explorer and then drag a project or plain file
into the IDE. Or, if I had already opened the file in such a directory and
it then appears in the recent file / project list, then I can open it from
there. I simply can not browse to it from the open file / open project
dialog.
I have found that "EPT:" was apparently some kind of special printer port in
very very early DOS days. So I guess at one time in the distant past it
made sense to not allow directories with this name (like I guess COM1 etc.
still are). As mentioned, the restriction did not exist in Vc6, and Windows
Explorer has no problem browsing to a directory called "ept" or a subdir of
it.
Or perhaps I am the only person to use "ept" as a directory name???? I find
that hard to believe....
-Eric P. Twietmeyer