Its biggest advantage as far as I'm concerned is that you can compile the code
as a .dll and then reference it from your .aspx page. This enables you to sell
your customer a working site but making it hard for them to steal your code.
The WDVL Discussion List from WDVL.COM
To Join
I'm with Tim in that I don't think every form should trigger a postback to
the server. There are many occasions where that's just a waste of time and
bandwidth. In many respect I tend to think that ASP.NET makes more sense for
intranets and enterprise applications that run on a webserver. That's
Cheryl wrote:
Its biggest advantage as far as I'm concerned is that if you have a
designer and developer working together the designer doesn't have to
even see much less be able to mess up the code when working on the page.
Scott wrote:
Hmm, OK. Wondered about that. I've got VS.NET 2003, but due
- Original Message -
From: Cheryl D Wise [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, December 08, 2004 4:13 PM
Subject: RE: [wdvltalk] OT Code in pages vs Code behind pages.
Code in the page is like classic asp. While code behind is in a separate
page and linked to the page via
Hoenig, Robert wrote:
Does anyone know the difference between Code in pages and Code behind
pages?? This would be in reference to an ASP.Net programming job.
Google:
http://www.4guysfromrolla.com/webtech/100500-1.shtml
And I believe it's referred to as Code-Behind by most and Evil by
me. If
Code in the page is like classic asp. While code behind is in a separate
page and linked to the page via an asp @page declaration:
%@ Page Language=vb Codebehind=week21a.aspx.vb
Inherits=testdeploy2.WebForm2%
In theory it makes code reuse easier. Difficult to work with unless you are
using an
