If VS (devenv.exe) is used to create a new web app, the virtual dir will
point to a physical dir that is a sub-dir of c:\inetpub\wwwroot\ , and the
\aspnet_client\ folder will be located at c:\inetpub\wwwroot\aspnet_client\

However, if this default location for the physical dir is not desired, IIS
may be used to create a new virtual dir that points to a physical dir that
is not a sub-dir of  c:\inetpub\wwwroot\  ( for example, c:\myapp\ ) ....

But how is the \aspnet_client\ folder supposed to be created for this web
app ?  VS will not create it (if you create a new web-app project in VS and
point it to the virtual dir for c:\myapp\).

Do you just physically copy c:\inetpub\wwwroot\aspnet_client\  to c:\myapp\
?

What configuration settings control where a web-app looks for its
\aspnet_client\ folder ?

[ Post a follow-up to this message ]

If this alternate physical directory (e.g. c:\myapp) is a virtual directory
underneath your existing website, then your existing aspnet_client folder
will work fine.

This is because a browser retrieves the javascript files located inside that
folder using HTTP, and IIS does the necessary translation of virtual URLs
into physical directories.

Your app will be located at http://yourservername/yourApp regardless of
whether the actual physical folder for your application is
c:\inetpub\wwwroot\yourApp or c:\yourApp.

Likewise, the aspnet_client contents are retrieved via
http://yourservername/aspnet_client

HTH

Cheers
Ken

--
IIS Blog: www.adopenstatic.com/cs/blogs/ken/
Web: www.adopenstatic.com


"John Grandy" <johnagrandy-at-yahoo-dot-com> wrote in message
news:uMLVq$EfFHA.1044@tk2msftngp13.phx.gbl...
: If VS (devenv.exe) is used to create a new web app, the virtual dir will
: point to a physical dir that is a sub-dir of c:\inetpub\wwwroot\ , and the
: \aspnet_client\ folder will be located at
c:\inetpub\wwwroot\aspnet_client\
:
: However, if this default location for the physical dir is not desired, IIS
: may be used to create a new virtual dir that points to a physical dir that
: is not a sub-dir of  c:\inetpub\wwwroot\  ( for example, c:\myapp\ ) ....
:
: But how is the \aspnet_client\ folder supposed to be created for this web
: app ?  VS will not create it (if you create a new web-app project in VS
and
: point it to the virtual dir for c:\myapp\).
:
: Do you just physically copy c:\inetpub\wwwroot\aspnet_client\  to
c:\myapp\
: ?
:
: What configuration settings control where a web-app looks for its
: \aspnet_client\ folder ?
:
:

[ Post a follow-up to this message ]

Hi Ken, and thanks for the response.

I am looking at a web server with a very high quality commercial application
that is not configured in the manner you describe.

In IIS , the default web site does not map to "c:\inetput\wwwroot", rather
it maps to "c:\webapps\webapp1"

There is an \aspnet_client\ folder in two places:

"c:\inetpub\wwwroot\aspnet_client\"
"c:\webapps\webapp1\aspnet_client\"

I assume that the app is using the \aspnet_client\ folder in the latter
location.   But I can not figure out how it was configured .... or why.

"Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message
news:OuHYTXFfFHA.2320@TK2MSFTNGP10.phx.gbl...
> If this alternate physical directory (e.g. c:\myapp) is a virtual
> directory
> underneath your existing website, then your existing aspnet_client folder
> will work fine.
>
> This is because a browser retrieves the javascript files located inside
> that
> folder using HTTP, and IIS does the necessary translation of virtual URLs
> into physical directories.
>
> Your app will be located at http://yourservername/yourApp regardless of
> whether the actual physical folder for your application is
> c:\inetpub\wwwroot\yourApp or c:\yourApp.
>
> Likewise, the aspnet_client contents are retrieved via
> http://yourservername/aspnet_client
>
> HTH
>
> Cheers
> Ken
>
> --
> IIS Blog: www.adopenstatic.com/cs/blogs/ken/
> Web: www.adopenstatic.com
>
>
> "John Grandy" <johnagrandy-at-yahoo-dot-com> wrote in message
> news:uMLVq$EfFHA.1044@tk2msftngp13.phx.gbl...
> : If VS (devenv.exe) is used to create a new web app, the virtual dir will
> : point to a physical dir that is a sub-dir of c:\inetpub\wwwroot\ , and
> the
> : \aspnet_client\ folder will be located at
> c:\inetpub\wwwroot\aspnet_client\
> :
> : However, if this default location for the physical dir is not desired,
> IIS
> : may be used to create a new virtual dir that points to a physical dir
> that
> : is not a sub-dir of  c:\inetpub\wwwroot\  ( for example, c:\myapp\ )
> ....
> :
> : But how is the \aspnet_client\ folder supposed to be created for this
> web
> : app ?  VS will not create it (if you create a new web-app project in VS
> and
> : point it to the virtual dir for c:\myapp\).
> :
> : Do you just physically copy c:\inetpub\wwwroot\aspnet_client\  to
> c:\myapp\
> : ?
> :
> : What configuration settings control where a web-app looks for its
> : \aspnet_client\ folder ?
> :
> :
>
>

[ Post a follow-up to this message ]

Hi,

Running aspnet_regiis.exe will place the correct aspnet_client folder under
each website currently configured on the server. So, at one time, there may
have been a website run from c:\inetpub\wwwroot (since that's the default).
Perhaps latter on a second website was added (or the default one changed),
and aspnet_regiis was run again to add the aspnet_client folder underneath
this new site.

Cheers
Ken

--
IIS Blog: www.adopenstatic.com/cs/blogs/ken/
Web: www.adopenstatic.com


"John Grandy" <johnagrandy-at-yahoo-dot-com> wrote in message
news:%23m3LVbFfFHA.748@tk2msftngp13.phx.gbl...
: Hi Ken, and thanks for the response.
:
: I am looking at a web server with a very high quality commercial
application
: that is not configured in the manner you describe.
:
: In IIS , the default web site does not map to "c:\inetput\wwwroot", rather
: it maps to "c:\webapps\webapp1"
:
: There is an \aspnet_client\ folder in two places:
:
: "c:\inetpub\wwwroot\aspnet_client\"
: "c:\webapps\webapp1\aspnet_client\"
:
: I assume that the app is using the \aspnet_client\ folder in the latter
: location.   But I can not figure out how it was configured .... or why.
:
: "Ken Schaefer" <kenREMOVE@THISadOpenStatic.com> wrote in message
: news:OuHYTXFfFHA.2320@TK2MSFTNGP10.phx.gbl...
: > If this alternate physical directory (e.g. c:\myapp) is a virtual
: > directory
: > underneath your existing website, then your existing aspnet_client
folder
: > will work fine.
: >
: > This is because a browser retrieves the javascript files located inside
: > that
: > folder using HTTP, and IIS does the necessary translation of virtual
URLs
: > into physical directories.
: >
: > Your app will be located at http://yourservername/yourApp regardless of
: > whether the actual physical folder for your application is
: > c:\inetpub\wwwroot\yourApp or c:\yourApp.
: >
: > Likewise, the aspnet_client contents are retrieved via
: > http://yourservername/aspnet_client
: >
: > HTH
: >
: > Cheers
: > Ken
: >
: > --
: > IIS Blog: www.adopenstatic.com/cs/blogs/ken/
: > Web: www.adopenstatic.com
: >
: >
: > "John Grandy" <johnagrandy-at-yahoo-dot-com> wrote in message
: > news:uMLVq$EfFHA.1044@tk2msftngp13.phx.gbl...
: > : If VS (devenv.exe) is used to create a new web app, the virtual dir
will
: > : point to a physical dir that is a sub-dir of c:\inetpub\wwwroot\ , and
: > the
: > : \aspnet_client\ folder will be located at
: > c:\inetpub\wwwroot\aspnet_client\
: > :
: > : However, if this default location for the physical dir is not desired,
: > IIS
: > : may be used to create a new virtual dir that points to a physical dir
: > that
: > : is not a sub-dir of  c:\inetpub\wwwroot\  ( for example, c:\myapp\ )
: > ....
: > :
: > : But how is the \aspnet_client\ folder supposed to be created for this
: > web
: > : app ?  VS will not create it (if you create a new web-app project in
VS
: > and
: > : point it to the virtual dir for c:\myapp\).
: > :
: > : Do you just physically copy c:\inetpub\wwwroot\aspnet_client\  to
: > c:\myapp\
: > : ?
: > :
: > : What configuration settings control where a web-app looks for its
: > : \aspnet_client\ folder ?
: > :
: > :
: >
: >
:
:

[ Post a follow-up to this message ]