Perhaps it is not always needed, but I've read (and confirmed by trying it)
that not having an aspnet_client folder in an web application will cause
problems with some ASP controls, such as validation, and that an
aspnet_client directory should be there for each site.
I am trying out the aspnet_client as a virtual application within each
site's root in IIS, rather than copying the same physical files to each
site's directory on the server. It seems to work fine, but I'm wondering if
I'm opening up myself to other troubles.
"Lars Netzel" wrote:
> I just have one aspnet_client folder as a subfolder in wwwroot. That's it,
> everything works fine. It's just a folder, not anything virtual at all.
>
> /Lars
>
> "MurrayTh" <> skrev i meddelandet
> news:ADA7A5FE-6FF8-485D-B0BB-...
> > Instead of having a copy of the aspnet_client folder in each site's files
> > on
> > a machine, can a virtual directory/application be made with each site's
> > root
> > in IIS to the machine's c:\inetpub\wwwroot\aspnet_client folder? Would
> > this
> > create security issues? If it is OK to do this, should it be a virtual
> > directory or virtual application?
> >
>
>
>
|
Similar Threads
