I've been reviewing some of the ASP code which I've produced to date, and

have noted that my ASP pages have ended up as the dreaded spaghetti-like

mixture of code (with a mixture of ASP statements and HTML tags).



I want to avoid this, and produce applications more aligned to the 

DNA application design model (where you have Presentation, Business Logic

and Data layers) so that I have well-defined separation of code from

content.



I've been keeping tabs on ASP+, and have noted that ASP+'s Web Forms seem

to offer the ability to separate code from content - but I was curious if

there any techniques/approaches I should be adopting NOW in order to

achieve this ? Any thoughts on this, anyone ?





Thanks.





Ray

yeah....  I have a major suggestion for you...



build include files each with a VBScript Class ... pseudo-object design in

ASP... I've got a model I've been following....  data layer-> stored

procedures -> VBScript Classes -> HTML and ASP for presentation...



All my included classes are designed to provide a layer of abstraction for

the developer, so the developer doesn't have to worry about the DB and they

can concentrate making the application work from a presentation perspective.



If you have any more questions, let me know.



HTH



Cory Koski



Web Programmer

Wabang Creative Technology and TBSource.com

e-certified as Master ASP programmer, Web programmer,

and IIS 4.0 Administrator

visit: http://www.tbsource.com/

(xxx) xxx-xxxx  ext. 41





----- Original Message -----

From: "Ray Murphy" 

To: "ASP Databases" <asp_databases@p...>

Sent: Wednesday, August 30, 2000 3:56 AM

Subject: [asp_databases] Code/Content Separation Issues





> I've been reviewing some of the ASP code which I've produced to date, and

> have noted that my ASP pages have ended up as the dreaded spaghetti-like

> mixture of code (with a mixture of ASP statements and HTML tags).

>

> I want to avoid this, and produce applications more aligned to the

> DNA application design model (where you have Presentation, Business Logic

> and Data layers) so that I have well-defined separation of code from

> content.

>

> I've been keeping tabs on ASP+, and have noted that ASP+'s Web Forms seem

> to offer the ability to separate code from content - but I was curious if

> there any techniques/approaches I should be adopting NOW in order to

> achieve this ? Any thoughts on this, anyone ?

>

>

> Thanks.

>

>

> Ray

>

	I've just finished an article on using templates to separate code from

content. It should be online at www.4guysfromrolla.com within the next two

weeks... The routines in the article show how to achieve this in a very

clean way. If you can't wait until the article is posted let me know and I

can email it to you.



	Cheers,

	--JQS



-----Original Message-----

From: Ray Murphy 

Sent: Wednesday, August 30, 2000 3:56 AM

To: ASP Databases

Subject: [asp_databases] Code/Content Separation Issues





I've been reviewing some of the ASP code which I've produced to date, and

have noted that my ASP pages have ended up as the dreaded spaghetti-like

mixture of code (with a mixture of ASP statements and HTML tags).



I want to avoid this, and produce applications more aligned to the

DNA application design model (where you have Presentation, Business Logic

and Data layers) so that I have well-defined separation of code from

content.



I've been keeping tabs on ASP+, and have noted that ASP+'s Web Forms seem

to offer the ability to separate code from content - but I was curious if

there any techniques/approaches I should be adopting NOW in order to

achieve this ? Any thoughts on this, anyone ?





Thanks.





Ray