I have not used ASP before. Are there cookbook instructions for how to
set up an asp directory structure. It is not clear to me how I must
mark directories (virtual or physical), so they will all be considered
to be part of the same application. Thanks.
Firstly you need to have IIS installed. This will create a directory on
your c:\ drive (assuming you have installed it to c:) called
C:\Inetpub. In this folder there is a directory wwwroot.
In this folder you must create other folders for each web app that your
are going to make. So your web directory could be
C:\Inetpub\wwwroot\firstwebapp.
In firstwebapp you put all your asp, html etc files. I suggest you also
use folders with in this folder to sort the file logically.
Once you have created your files, open your browser and enter the
following to view your app
http://localhost/firstwebapp/firstpage.asp
I think that that is a pretty good start. It is actually really easy
and most problems can be solved just by looking on the net for help
On 27 Sep 2005 15:23:17 -0700, "SMAccount"
wrote:
>I have not used ASP before. Are there cookbook instructions for how to
>set up an asp directory structure. It is not clear to me how I must
>mark directories (virtual or physical), so they will all be considered
>to be part of the same application. Thanks.
For ASP, there si no required structure. You're describing ASP.NET
settings, which would be a different group. The ASP.NET groups have
dotnet in the name, the ASP Classic groups have just ASP.
Jeff
OK thanks, but how do I add a virtual folder to an application and
"mark" it as being part ot the application?
OK thanks, but how do I add a virtual folder to an application and
"mark" it as being part ot the application?
On 28 Sep 2005 13:40:30 -0700, "SMAccount"
wrote:
>OK thanks, but how do I add a virtual folder to an application and
>"mark" it as being part ot the application?
In ASP you don't. In ASP.NET you can, but that's an ASP.NET question,
which isn't what this group covers. Try the groups with "dotnet" in
the name.
Jeff
It is my understanding that in a CLASSIC (not a dot net!) ASP
Application, the following happens:
(1) All code in the "application" shares a common Application Object.
(2) For each user "session", all code in the application shares a
common Session Object.
I could be wrong, but if the above two assertions are true, then there
would have to be a way of identifying which .asp files belong to the
same application. True or false?
It is my understanding that in a CLASSIC (not a dot net!) ASP
Application, the following happens:
(1) All code in the "application" shares a common Application Object.
(2) For each user "session", all code in the application shares a
common Session Object.
I could be wrong, but if the above two assertions are true, then there
would have to be a way of identifying which .asp files belong to the
same application. True or false?
"SMAccount"
news:1128002145.467295.83410@f14g2000cwb.googlegroups.com...
> It is my understanding that in a CLASSIC (not a dot net!) ASP
> Application, the following happens:
>
> (1) All code in the "application" shares a common Application Object.
>
> (2) For each user "session", all code in the application shares a
> common Session Object.
>
> I could be wrong, but if the above two assertions are true, then there
> would have to be a way of identifying which .asp files belong to the
> same application.
Sorry, I don't follow this logic. This conclusion seems to be a non
sequitor.
> True or false?
>
False.
All subfolders of the application folder are considered to be part of the
application.
Bob Barrows
So does IIS prevent one from assigning the same physical folder to two
applications by associating two different virtual folder names with it?
"SMAccount"
news:1128091690.565444.206450@f14g2000cwb.googlegroups.com.. .
> So does IIS prevent one from assigning the same physical folder to two
> applications by associating two different virtual folder names with it?
>
I've never tried it, but I suspect this is is not prevented. It's the
virtual directory that provides the context, afaik. Give it a try - should
take you 10 min. to set up a quick test for this.
You may get a more authoritative answer in the .iis newsgroup.
Bob Barrows
On 29 Sep 2005 06:55:49 -0700, "SMAccount"
wrote:
>It is my understanding that in a CLASSIC (not a dot net!) ASP
>Application, the following happens:
>
>(1) All code in the "application" shares a common Application Object.
>
>(2) For each user "session", all code in the application shares a
>common Session Object.
>
>I could be wrong, but if the above two assertions are true, then there
>would have to be a way of identifying which .asp files belong to the
>same application. True or false?
False. It doesn't work that way. No ASP files belong to any
"application" as you seem to be defining it. ASP is interpreted by
the web server as each file is requested. Sessions belong to the
user, not the "application". Some application state can be achieved,
but it's not the same as an ASP.NET application.
Jeff
On 30 Sep 2005 07:48:10 -0700, "SMAccount"
wrote:
>So does IIS prevent one from assigning the same physical folder to two
>applications by associating two different virtual folder names with it?
In Classic ASP, virtual folders aren't assigned to applications. They
are simply virtual folders, a way of pointing to a folder outside the
web folder hierarchy. There is no problem with pointing to the same
physical directory, since the physical files and virtual directory
have nothing to do in Classic ASP except house a script file.
Jeff