ASP.NET MVC controllers static methods

Question

A discussion came up at work recently about why ASP.NET MVC doesn\'t use static methods for its controller methods. Whilst I was on the side of the fence against us

Answer 1

While I don't know minds of those that designed the ASP.NET MVC Framework here is the big one for me:

An instance controller is instantiated once per request, multiple requests can be happening simultaneously. If a controller is static then any state on the controller is shared across all requests simultaneously. You probably don't want that. Updating that shared state becomes a minefield of locking contention, possible deadlocks and very hard to track bugs if locking isn't implemented properly.

In short, a static controller would be a nightmare to work with.