AutoEventWireup attribute in Microsoft ASP.NET Web Forms

转载 2006年06月22日 17:41:00


ASP.NET supports two methods to author pages:

  1. In-line code
  2. Code-behind

In-line code is code that is embedded directly within the ASP.NET page. Code-behind refers to code for your ASP.NET page that is contained within a separate class file. This allows a clean separation of your HTML from your presentation logic.

When we use Microsoft Visual Studio .NET to create ASP.NET Web Forms, code-behind pages are the default method. In addition, Visual Studio .NET automatically performs precompilation for us when we build our solution.

A little bit of background

Directives in ASP.NET control the settings and properties of page and user control compilers. They can be included anywhere on a page, although it is standard to place them at the beginning. Directives are used in both .aspx files (ASP.NET pages) and .ascx files (user control pages). ASP.NET pages actually support eight different directives.

  • @ Page
  • @ Control
  • @ Import
  • @ Implements
  • @ Register
  • @ Assembly
  • @ OutputCache
  • @ Reference

Page directives are the most commonly used directives, and are used to edit a wide variety of settings that control how the page parser and page compiler work. The following is a list of some of the more commonly used page directive attributes in ASP.NET.

  • Language indicates the language in which the inline script code within the ASP.NET page is written (the code between <% %> tags). The value of this attribute can be C#, VB, or JS.
  • Codebehind indicates the name of the file being used as the code supporting this ASP.NET page. This file should reflect the Language setting; that is, if the language being used is C#, the CodeBehind file should have a .cs extension and be written in C#.
  • Inherits indicates a qualified class from which this ASP.NET page should inherit. Generally, this will be the name of the class described in the code-behind file.
  • AutoEventWireup is a Boolean attribute that indicates whether the ASP.NET pages events are auto-wired.

Note: In the above case, ASP.NET compiles the code-behind page on the fly. We have to note that this compilation step only occurs when the code-behind file is updated. Whether the file has been updated or not, well this is detected through a timestamp change.

To get to the Real Thing

The AutoEventWireup attribute may have a value of true or false. When an ASP.NET Web Application is created by using Microsoft Visual Studio .NET, the value of the AutoEventWireup attribute is set as false.

We can specify the default value of the AutoEventWireup attribute in the following locations:

  • The Machine.config file.
  • The Web.config file.
  • Individual Web Forms (.aspx files).
  • Web User Controls (.ascx files)

The value of the AutoEventWireup attribute can be declared in the <pages> section in the Machine.config file or the Web.config file, as follows:

If you make these changes in the Machine.config file, the changes affect all ASP.NET Web Forms on the computer. If you make these changes in the Web.config file, the changes affect only the application that the file belongs to. However, to make changes in the individual Web Form Only, we have to add the AutoEventWireup attribute to the @ Page directive, as shown above.

Check out the Code

When we create a new ASP.NET Web Application in Visual Studio .NET, as mentioned earlier, by default, the value of the AutoEventWireup attribute is set to false in the .aspx page and event handlers are automatically created. We can find this in the InitializeComponent method:

The best way to see the working of this attribute would be:

  • Declare a string variable msg as public in WebForm1.aspx.cs.
  • In the HTML section of WebForm1.aspx, enter the following code in the <Head> section:

    In the Page_Load, you could enter a value for the variable msg declared.


On running the application, you will get the message We are in Page_Load() [hereafter referred to as message]. Note: this is in the default case where the attribute is set to false.

Now try commenting the event handler code for the Page_Load in the aspx.cs file; and set the AutoEventWireup attribute to false in the .aspx page. On running the application this time, you will not get the message.

Now with the event handler code for the Page_Load in the aspx.cs file still commented; set the AutoEventWireup attribute to true in the .aspx page. On running the application this time, you will get the message.

Reason: In the case where AutoEventWireup attribute is set to false (by default), event handlers are automatically required for Page_Load or Page_Init. However, when we set the value of the AutoEventWireup attribute to true, the ASP.NET runtime does not require events to specify event handlers like Page_Load or Page_Init.

A thing to be kept in mind is that the AutoEventWireup attribute of the Page directive is set to true by default for the machine (check out the value of this attribute in the machine.config) but set to false by default for a .aspx page). So if it is missing, since by default it is true (i.e., at the machine level), the page framework calls page events automatically, specifically the Page_Init and Page_Load methods. In that case, no explicit Handles clause or delegate is needed.

Performance Issues

We must not set the value of the AutoEventWireup attribute to true if performance is a key consideration. If we set the value of the AutoEventWireup attribute to true, the ASP.NET page framework must make a call to the CreateDelegate method for every Web Form (.aspx page), and instead of relying on the automatic hookup, manually override the events from the page.


The whole thing was really simple but I just thought of posting it online; hope it helps someone. To give credit to where it is due. Most of the information was garnered from different places on the net. I've just complied them together and added a bit of my own to help folks along their way. I was also able to find an article related to this in MSDN Online (Article ID: 317690) but for VB.NET.


学习ASP .NET MVC5官方教程总结(一)入门

学习ASP .NET MVC5官方教程总结(一)入门          在这一部分我们来学习教程的第一部分--入门,在讲之前先说一下我们的开发环境和版本,我们的开发环境是Visual Studio...
  • yejinwei1220
  • yejinwei1220
  • 2015年04月28日 17:13
  • 1698

ASP.NET Web API系列教程之 html表单 与服务器

5.1 HTTP Message Handlers 5.1 HTTP消息处理器 本文引自:
  • anhuidelinger
  • anhuidelinger
  • 2013年05月10日 19:24
  • 2677

《Java Web开发实战经典》.(李兴华).[PDF]pdf

下载地址:网盘下载 内容简介  · · · · · · 《Java开发实战经典(名师讲坛)》是一本综合讲解Java核心技术的书籍,在书中使用大量...
  • cf406061841
  • cf406061841
  • 2017年05月20日 11:13
  • 2099

ASP.NET Web Forms - DataList 控件

DataList 控件,类似于 Repeater 控件,用于显示绑定在该控件上的项目的重复列表。不过,DataList 控件会默认地在数据项目上添加表格。 绑定 DataSet 到 Data...
  • riyuedangkong1
  • riyuedangkong1
  • 2017年04月14日 17:14
  • 257

ASP.NET Web Forms Today

1. ASP.NET Web Forms模型ASP.NET Web Forms有三大支柱:page postbacks, view state, 和server controls. 如下面的模型所示:...
  • wangchongcy
  • wangchongcy
  • 2011年03月29日 09:19
  • 598

ASP.NET Web Forms 转换至MVC开发

作为.NET 阵营的网页开发人员几乎都是从ASP.NET Web Forms开始接触网页开发技术的,所在在这里主要介绍一下Web Forms与MVC的差异。 一、开发概念的转变        MV...
  • DestinyAaron
  • DestinyAaron
  • 2017年07月31日 11:34
  • 261

What's Ailing ASP.NET Web Forms

The recent announcement that ASP.NET will soon get an alternate engine in the ASP.NET Model View Con...
  • u014180504
  • u014180504
  • 2016年01月02日 13:43
  • 596

Essential Studio for ASP.NET Web Forms发布2017 v2,新增自定义树形网格工具栏等

Essential Studio for ASP.NET Web Forms是一个帮您轻松创建商业Web应用程序的ASP.NET界面控件,其包含了商业Web应用程序开发中所需的所有控件,如grids、...
  • Harriet666
  • Harriet666
  • 2017年05月24日 17:23
  • 722

B/S开发(二) ASP.NET Page指令之AutoEventWireUP

使用Visual Studio 2005开发一个ASP.NET Project时,在新增一个Web For http:// m时,IDE会自动在aspx文件的第一行产生Page指令,示例如下: 这次...
  • bason
  • bason
  • 2011年08月10日 11:56
  • 3045

VS 2010 和 .NET 4.0 系列之《ASP.NET 4 Web Forms 的整洁HTML标识 — 客户端ID》篇

By saucer | Published: 2010 年 09 月 29 日 【原文地址】 Cleaner HTML Markup with ASP.NET 4 Web Forms...
  • henulwj
  • henulwj
  • 2012年07月21日 09:47
  • 1103
您举报文章:AutoEventWireup attribute in Microsoft ASP.NET Web Forms