On Tue, 2 Dec 2003 16:03:48 -0500, "GhislainTanguay"
<fredpoideletethis@hotmail.com> wrote:
[color=blue]
>Hi everyone, i work on a ASP (Not .NET but version 3) project. This project
>is on our server for development. I use SQL-SERVER, IIS and
VB for DLL.
>On the server i have create a folder with my project name "Aptitudes" under
>inetpub/wwwroot/.[/color]
[color=blue]
>I recently talked with an external consultant and he told me that I did
>something wrong when I created my Aptitudes folder.
>He said that when we will be ready for transfering the project on a
>commercial server everything will go wrong because I didn't put my project
>directly under inetpub. Dll will not see my project, and so on...
>
>Is it the truth? I don't understand why it will be so complicated.[/color]
It may or may not be depending on what path coding you use. If you
duplicate the production paths in the development environement it's a
breeze, but sometimes it isn't possible and sometimes clients will
decide your stuff has to be somewhere else. The ASP DLL doesn't
really care, as long as the proper permissions are in place, and if
you use paths relative to your application's root it's trivial to make
work with any placement.
Many times I've used a simple config file for this purpose, with a
base URL or root designation to account for a client moving the
application somewhere else. It's easier in a database driven site,
but even an include works fine, similar to including a database
connection string for easy modification.
Jeff