|
 |
asptoday_discuss thread: asp programming methodologies
Message #1 by "Daniel Newman" <pc@r...> on Wed, 12 Dec 2001 23:27:25
|
|
I am an experienced Coldfusion programmer, new to ASP. I often used a
method called FUSEBOX programming which simply used a switch statement and
INCLUDES to architect a site.
In Coldfusion a CFINCLUDE statement does not get executed before all other
scripts as does an asp #include. This means that files can be
programatically included making it easy to separate out functionality and
layout in multiple files.
I am looking for some system that might be equivalent as I learn ASP. How
do people architect sites with lots of different pages. Is there no way to
center a site around the default.asp page, inserting content as needed by
the logic flow of the application? Where can I find some strategies?
THX!!!
Message #2 by "Mark Phillips" <webmaster@d...> on Thu, 13 Dec 2001 23:27:22 -0000
|
|
Hi Daniel,
I'm not familiar with Cold Fusion although I have used a product called
Tango which I think is not dissimilar, and have been well used to the
technique of include files!
Writing applications in .net is a very different mindset to
Coldfusion/Tango. The architecture of the entire environment is fully object
orientated. As a result it's possible to create "controls" (like included
bits of HTML) that can do more - for example, attaching code and behaviours
and thus building up an ASP page (or a whole site) from "snippets" of code
wrapped into classes. This could include common functionality and/or
presentation.
The Wrox book "Beginning ASP.Net Using C#" touches on the subject in a later
chapter, I'm quite new to it myself but will be trying out the techniques
over the next few weeks. So while I can point you at some of the ideas, I
can't advise further yet except to say that I found tha above book very
helpful to get started.
Best Regards,
Mark
-----Original Message-----
From: Daniel Newman [mailto:pc@r...]
Sent: 12 December 2001 23:27
To: ASPToday Discuss
Subject: [asptoday_discuss] asp programming methodologies
I am an experienced Coldfusion programmer, new to ASP. I often used a
method called FUSEBOX programming which simply used a switch statement and
INCLUDES to architect a site.
In Coldfusion a CFINCLUDE statement does not get executed before all other
scripts as does an asp #include. This means that files can be
programatically included making it easy to separate out functionality and
layout in multiple files.
I am looking for some system that might be equivalent as I learn ASP. How
do people architect sites with lots of different pages. Is there no way to
center a site around the default.asp page, inserting content as needed by
the logic flow of the application? Where can I find some strategies?
THX!!!
Message #3 by Dan Newman <pc@r...> on Thu, 13 Dec 2001 15:41:06 -0800
|
|
Thanks Mark,
I am eager to move onto to learning asp.net and getting into the object
oriented approach therein.
Unfortunately the client I am working for right now, wants just ASP.
With ASP it doesn't seem easy to use a single page approach -- that I think
is fairly common with Coldfusion. In this approach a single, say index.cfm,
page is hit every time by the user and content is loaded in according to
what variables are passed into the page. The content is loaded with
CFINCLUDE statements. This works well, because CFINCLUDES are not executed
before all other code in Coldfusion as they are in ASP. The problem with ASP
in this area, is that #include s all get run on every page. A Coldfusion
page may have 30 CFINCLUDEs, but only actually execute 1. In ASP, all 30
would run no matter what -- making less than stellar performance for this
sort technique.
So I am using #include s in my ASP application -- but rather than a single
page approach with tons of them, I am using multiple pages-- 1 per each
major block of content. Can't see any other approach, but it's cool.
Anyway, just food for thoughts ...
Am looking forward to ASP.NET though -- let us know it goes for you.
Dan
> Hi Daniel,
>
> I'm not familiar with Cold Fusion although I have used a product called
> Tango which I think is not dissimilar, and have been well used to the
> technique of include files!
>
> Writing applications in .net is a very different mindset to
> Coldfusion/Tango. The architecture of the entire environment is fully
object
> orientated. As a result it's possible to create "controls" (like included
> bits of HTML) that can do more - for example, attaching code and
behaviours
> and thus building up an ASP page (or a whole site) from "snippets" of code
> wrapped into classes. This could include common functionality and/or
> presentation.
>
> The Wrox book "Beginning ASP.Net Using C#" touches on the subject in a
later
> chapter, I'm quite new to it myself but will be trying out the techniques
> over the next few weeks. So while I can point you at some of the ideas, I
> can't advise further yet except to say that I found tha above book very
> helpful to get started.
>
> Best Regards,
> Mark
>
> -----Original Message-----
> From: Daniel Newman [mailto:pc@r...]
> Sent: 12 December 2001 23:27
> To: ASPToday Discuss
> Subject: [asptoday_discuss] asp programming methodologies
>
>
> I am an experienced Coldfusion programmer, new to ASP. I often used a
> method called FUSEBOX programming which simply used a switch statement and
> INCLUDES to architect a site.
>
> In Coldfusion a CFINCLUDE statement does not get executed before all other
> scripts as does an asp #include. This means that files can be
> programatically included making it easy to separate out functionality and
> layout in multiple files.
>
> I am looking for some system that might be equivalent as I learn ASP. How
> do people architect sites with lots of different pages. Is there no way to
> center a site around the default.asp page, inserting content as needed by
> the logic flow of the application? Where can I find some strategies?
>
> THX!!!
>
>
Message #4 by "Marshall Rosenstein" <marshr@s...> on Wed, 19 Dec 2001 23:40:41
|
|
You should investigate the Server.Execute and Server.Transfer statements.
They allow you to conditionally process code located in other ASP pages.
In most cases, they are preferable to using the #include directive. Also,
you should take advantage of the VBScript Class...End Class statement to
help modularize your code.
> I am an experienced Coldfusion programmer, new to ASP. I often used a
> method called FUSEBOX programming which simply used a switch statement
and
> INCLUDES to architect a site.
>
> In Coldfusion a CFINCLUDE statement does not get executed before all
other
> scripts as does an asp #include. This means that files can be
> programatically included making it easy to separate out functionality
and
> layout in multiple files.
>
> I am looking for some system that might be equivalent as I learn ASP.
How
> do people architect sites with lots of different pages. Is there no way
to
> center a site around the default.asp page, inserting content as needed
by
> the logic flow of the application? Where can I find some strategies?
>
> THX!!!
Message #5 by Dan Newman <pc@r...> on Wed, 19 Dec 2001 16:35:04 -0800
|
|
Now we're talking ... thanks for these tips -- this is the kind of stuff
that I was looking for and had yet to find ...
thanks much I will look into both of these areas!
Dan
> You should investigate the Server.Execute and Server.Transfer statements.
> They allow you to conditionally process code located in other ASP pages.
> In most cases, they are preferable to using the #include directive. Also,
> you should take advantage of the VBScript Class...End Class statement to
> help modularize your code.
>
> > I am an experienced Coldfusion programmer, new to ASP. I often used a
> > method called FUSEBOX programming which simply used a switch statement
> and
> > INCLUDES to architect a site.
> >
> > In Coldfusion a CFINCLUDE statement does not get executed before all
> other
> > scripts as does an asp #include. This means that files can be
> > programatically included making it easy to separate out functionality
> and
> > layout in multiple files.
> >
> > I am looking for some system that might be equivalent as I learn ASP.
> How
> > do people architect sites with lots of different pages. Is there no way
> to
> > center a site around the default.asp page, inserting content as needed
> by
> > the logic flow of the application? Where can I find some strategies?
> >
> > THX!!!
>
|
|
 |