I've got a general question...do you think that code-behind will be a

thriving feature of .NET?  Personally, I like all my code in the same page,

so I can see everything that's happening...although I have tried to

code-behind model and found it to be very cool, very safe, and very useful

in certain situations.  I use a lot of SSI in my classic ASP projects.



Are you using/will you use it in your own Web projects?



Jason

This message is in MIME format. Since your mail reader does not understand

this format, some or all of this message may not be legible.



------_=_NextPart_001_01C17289.FD575B72

Content-Type: text/plain



Jason,



For sure.



Code behind adds a lot of flexibility. Seperating presentation from business

logic. I guess you could say something similar to an n-tier model but

without the dll/com head aches, best of both worlds I think is what m$ call

it.



Some sites have a different presentation or 'skin', but the core application

stays the same, this style of syndication strongly supports code behind.  



It also allows (although other mechanisms exist), code re use, as my old uni

lecturer use to say 'Why re invent the wheel twice ?', Re using existing

black boxes does provide in general a quicker development cycle and a more

stable application...





I'm sure other people will come up with more examples :-)







Just my 2 cents worth.



Aaron



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

From: Jason Salas [mailto:jason@k...] 

Sent: Wednesday, 21 November 2001 11:07 PM

To: ASPToday Discuss

Subject: [asptoday_discuss] Will .NET code-behind survive?





I've got a general question...do you think that code-behind will be a

thriving feature of .NET?  Personally, I like all my code in the same page,

so I can see everything that's happening...although I have tried to

code-behind model and found it to be very cool, very safe, and very useful

in certain situations.  I use a lot of SSI in my classic ASP projects.



Are you using/will you use it in your own Web projects?



Jason

short answer: yes.



long answer: yes because of the great benefit of class inheritance.



You can keep on using SSI even though some people advocate user controls

as an alternative.



Lou



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

From: Jason Salas [mailto:jason@k...] 

Sent: Wednesday, November 21, 2001 12:07 PM

To: ASPToday Discuss

Subject: [asptoday_discuss] Will .NET code-behind survive?





I've got a general question...do you think that code-behind will be a

thriving feature of .NET?  Personally, I like all my code in the same

page, so I can see everything that's happening...although I have tried

to code-behind model and found it to be very cool, very safe, and very

useful in certain situations.  I use a lot of SSI in my classic ASP

projects.



Are you using/will you use it in your own Web projects?



Jason




$subst('Email.Unsub')