You so lost that battle. ASP.NET 2.0 is a bundle of new magic.
On 5/6/06, Marc Brooks <[EMAIL PROTECTED]> wrote:
I count three ways of doing the same thing, one of which requires a
"magic" flag. That's two code smells at least. The framework is
complex enough, why have so many _directly equiv
There are four if you count VB's Handles keyword. It's ironic the default VB
.aspx template uses AutoEventWireup="false". The Handles keyword allows the
language to define a method and wire the event in one fell swoop.
--
Scott
http://www.OdeToCode.com/blogs/scott/
> -Original Message-
>
The "magic" flag is the default behavior, actually. It was the default way
the ASP.NET team originally intended for people to handle the page events.
It was the VS.NET team's implementation of the wizards back in VS.NET 2002
that went counter to that. Since everyone uses VS.NET, that's what people
You can turn that off, override the On_ methods or wire up the event
handlers in OnInit yourself.
I don't see a problem with AutoEventWireUp.
I count three ways of doing the same thing, one of which requires a
"magic" flag. That's two code smells at least. The framework is
complex enough, why
because that's how it works by default to wire up the event handlers, e.g.
Page_Load.
You can turn that off, override the On_ methods or wire up the event
handlers in OnInit yourself.
I don't see a problem with AutoEventWireUp.
cheers,
dominick
-
Dominick Baier, Dev
Hi all,Can anyone tell me why and by default that VS2005 sets the Autowireup
attribute of the page directice to true??
This was heavily frowned upon in 2003.
THanks
Paul
===
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage yo
