In ASP.NET, what conditions would cause OnServerClick="foo" to fail, so that "foo()" never gets called?

Question

I've written an ASP.NET application that runs on thousands of sites. But at least at one site, the following code fails:

void foo(Sender o, EventArgs e)  
{
    ....
}

<input runat="server" ....  OnServerClick="foo" ...

Have you ever experienced the OnServer events failing? I experimented at this site and couldn't come up with exactly the magic that makes it fail, but IIS Windows Authentication might be related, or this line of code might be related, based on turning things on and off, commenting things out:

void Page_Init (object sender, EventArgs e) {ViewStateUserKey = Session.SessionID;}

But how would these things be related? And again, this same code works at thousands of other sites.

So, have you ever encountered OnServer events failing triggered by setttings or conditions that were outside of your code?

Answer 1

AutoEventWireUp="false" either in a page directive, setting in web.config or machine wide in machine.config

False = Event will not be bound automagically.

Other possibilities: EnableViewState setting or Viewstate is getting stripped/corrupted in transport.

MachineKey setting in configs and combination of Encrypting Viewstate

Temporary ASP.Net Files could be corrupt

Unpatched / Wrong .net runtime

Would probably start with the machine.config