Background:

We are converting a project from asp.net 1.1 to 2.0 and also moving from VS2003 to VS2005. We are trying to use VS2005 Web Application Projects.

Issue:

When we selected to Convert to a Web Application Project, the wizard did the following that we did not anticipate:

1. Changed the autoeventwireup attribute in our aspx, ascx pages to "True". We had it set to false previously  for better performance.
2. Removed all event wiring from the code behind pages. The OnInit method was removed and the wireup from the InitializeComponent was removed, e.g.:

//Code behind before WAP Conversion:
override protected void OnInit(EventArgs e)
{
  InitializeComponent();
  base.OnInit(e);
}

private void InitializeComponent()
{
  this.Load += new System.EventHandler(this.Page_Load);
}

//Code behind after WAP Conversion:
private void InitializeComponent()
{
}

Questions:

1. Why is Microsoft pushing autoeventwireup=true? Is it the preferred way to go forward? We have had it set to false in the past for better performance but we don't want to set it to false if Microsoft will be assuming it is true and building on top of that going forward.
2. Why is it now so hard to change the default to autoeventwireup=false? We have to:
1. change the templates to include the OnInit and wireup of Page_Load
2. add wiring code every time we hook up an event
3. manually add all of the events back into the code behind after the WAP conversion
3. What is the performance overhead of autoeventwireup=true? It creates delegates at runtime to handle the wiring, correct?
4. Is there a configuration setting we can set so the autoeventwireup and wiring will not be touched during the WAP conversion?  In order to leave autoeventwireup=false, we have spent many hours after the conversion to try to set it back to false and will have to spend many more hours. Here is what we have had to do manually:
1. Find and change all of the templates that specify autoeventwireup=true.
2. Set the autoeventwireup back to false in the aspx, ascx.
3. Re-add the OnInit() method and all event wiring by looking at code history in our source control and manually adding the event wiring back in. This is obviously a very risky approach. We are in the middle of it and decided to stop until we could get some help.