Re: Include File or Include Virtual

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Bryan Harrington (news_at_psacake.com)
Date: 03/29/04


Date: Mon, 29 Mar 2004 12:17:21 -0500

Well.. that's part of my problem I suppose.. I don't know what the absolute
path will be if the end user decides to install it in a subdirectory instead
of it's own virtual web.

"Manohar Kamath [MVP]" <mkamath@TAKETHISOUTkamath.com> wrote in message
news:efATThaFEHA.3372@TK2MSFTNGP10.phx.gbl...
> Use absolute paths for common elements (includes, stylesheets, etc.) than
> relative paths. Takes care of many problems than you know :)
>
> --
> Manohar Kamath
> Editor, .netWire
> www.dotnetwire.com
>
>
> "Bryan Harrington" <news@psacake.com> wrote in message
> news:euwcqPaFEHA.1128@TK2MSFTNGP11.phx.gbl...
> > Hello all.. I'm working on an application that I'd like to use some
shared
> > files.
> >
> > Right now my directory structure is:
> >
> > / (root)
> > .../Shared/
> > .../Reports/
> > .../Tools/
> >
> > I would like to have CSS, shared functions etc.. in the shared folder
and
> > use them in the root, reports and tools.
> >
> > So.. in my dev environment I don't have a problem, but I have a remote
> > developer that wants to install in a subdirectory.. so all my includes
> don't
> > work..
> >
> > <!--#INCLUDE FILE="shared/Common.asp"-->
> >
> > should I change to virtual? I'm stuck on how to make this work in both
> > installing in a root web situation, and a sub directory situation.
> >
> > Thoughts?
> >
> >
>
>



Relevant Pages