You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A pre-built integration for ASP.NET will benefit a large number of people
working in this environment.
Once this is done, the MVC integration should be layered on top of it.
The primary requirements of this integration are:
Injection of dependencies into Pages and Controls
Per-request container disposal
Minimisation of static dependencies
Flexible enough to accommodate multiple container scoping schemes
Easy to configure
Reasonably testable code...
Ideally Pages should be able to be injected into without disrupting the
inheritance hierarchy, e.g. by using [InjectProperties] or a similar
attribute in conjunction with an HTTP Module. Perhaps additional attributes
targeting members could be used to implement recursive injection.
Base classes for Pages and Controls should also be provided for those not
wishing to install an HTTP Module.
From nicholas...@gmail.com on January 25, 2008 22:36:26
A pre-built integration for ASP.NET will benefit a large number of people
working in this environment.
Once this is done, the MVC integration should be layered on top of it.
The primary requirements of this integration are:
Ideally Pages should be able to be injected into without disrupting the
inheritance hierarchy, e.g. by using [InjectProperties] or a similar
attribute in conjunction with an HTTP Module. Perhaps additional attributes
targeting members could be used to implement recursive injection.
Base classes for Pages and Controls should also be provided for those not
wishing to install an HTTP Module.
Original issue: http://code.google.com/p/autofac/issues/detail?id=22
The text was updated successfully, but these errors were encountered: