D
Dave
I have two environments: DEV and PROD. In DEV I have two independent webs.
In PROD one of the webs is the root and the other is a subweb of the root.
Each enviornment has a different file system configuration so I must
manually change the file location references in my code when I post from DEV
to PROD.
For example, I want to reference an include file that is located in the
subweb from the root web. The physical file structure looks like this....
--DEV
c:\inetpub\wwwroot\myroot
c:\inetpub\wwwroot\mysubweb\includes\mypage.inc
--PROD
e:\InetPub\Clients\myroot\mysubweb\includes\mypage.inc
....which means if I call the include file from myroot I have to use
different references ....
--DEV
<!--#include file="../mysubweb/includes/mypage.inc"-->
--PROD
<!--#include file="mysubweb/includes/mypage.inc.inc"-->
I am using ASP 3.0 and I have several include files for db connections,
menus, etc that are shared between the two webs.
What is the best practice for handling this situtation as efficiently as
possible?
Thanks
Dave
In PROD one of the webs is the root and the other is a subweb of the root.
Each enviornment has a different file system configuration so I must
manually change the file location references in my code when I post from DEV
to PROD.
For example, I want to reference an include file that is located in the
subweb from the root web. The physical file structure looks like this....
--DEV
c:\inetpub\wwwroot\myroot
c:\inetpub\wwwroot\mysubweb\includes\mypage.inc
--PROD
e:\InetPub\Clients\myroot\mysubweb\includes\mypage.inc
....which means if I call the include file from myroot I have to use
different references ....
--DEV
<!--#include file="../mysubweb/includes/mypage.inc"-->
--PROD
<!--#include file="mysubweb/includes/mypage.inc.inc"-->
I am using ASP 3.0 and I have several include files for db connections,
menus, etc that are shared between the two webs.
What is the best practice for handling this situtation as efficiently as
possible?
Thanks
Dave