Re: Bug when IIS mapped to root of drive

Tech-Archive recommends: Fix windows errors by optimizing your registry

A bug? More likely, unpredictable results of misuse! I'm sorry, but you are
not supposed to store anything in the root. Generally, an application is
streamlined to work within it's own installation tree - but of course, the
system provides support via the search path. As I said, you might find that
some things will work sometimes, but count on unpredictability.

I am not an expert on this, but I am pretty sure that the IIS 'mapping' is a
'softlink' and I can't give you the specifics on how it would interpret
this - I assume that having a soft link will make it by-pass asking the
system of assistance, so it must be mapped to a fully verifyable file path,
whereas for VS, the D: is just a drive designation without a file path, so
it will ask the system, I am not sure if VS will understand the soft link
mapping, most likely it will ask the system to come up with something
sensible. But please do not fill up your root with junk! Leave that to the
system.

Tony. . .


"Hiwj" <Hiwj@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4F1B3DEF-1A5C-4241-BBBA-72FCC86AB15D@xxxxxxxxxxxxxxxx
>I am using Windows XP (SP2), and have found a problem with VWD2005 and
>VS2005
> when the Default Website is mapped to the root of a drive:
>
> If I map the Default Website in IIS to D:\wwwroot then everything is OK.
>
> If I map the Default Website to D: then IIS can't open the ASP.NET
> configuration dialog, the ASP.NET pages don't work in IE, but Visual
> Studio
> works OK.
>
> If I map the Default Website to D:\ then IIS can open the ASP.NET
> configuration dialog, the ASP.NET pages work fine in IE, but Visual Studio
> has problems. Sometimes it will freeze while opening the website, other
> times
> it will freeze while opening the default.aspx page in Design Mode.
>
> Is this a bug in ASP.NET, Visual Studio, or something else?


.

Relevant Pages

  • Re: How to change all relative paths in a website???
    ... The website sits on an Intranet and in IIS, ... So accessing the Intranet website using this new alias, turns the root ... So all the relative paths ...
    (microsoft.public.inetserver.asp.general)
  • Re: Page and Images not found on Localhost
    ... IIS. ... But when you move to production it usually works of the root of the ... basically what it does is maps your project name to the folder. ... When I try to either run the website in IE7 using ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Page and Images not found on Localhost
    ... IIS. ... But when you move to production it usually works of the root of the ... basically what it does is maps your project name to the folder. ... When I try to either run the website in IE7 using ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Page and Images not found on Localhost
    ... IIS. ... But when you move to production it usually works of the root of the ... basically what it does is maps your project name to the folder. ... When I try to either run the website in IE7 using ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Permission Problems SBS2003 R1
    ... website on the SBS server? ... Default permissions and user rights for IIS 6.0 ... Step 3: Please check the permissions in IIS manager: ... Step 4: Re-running CEICW on SBS server: ...
    (microsoft.public.windows.server.sbs)