| Issue 62: | Vary injection into ASP.NET page & controls through registration |
1 of 17
Next ›
|
| 1 person starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
Per this thread (http://groups.google.com/group/autofac/browse_thread/thread/b5d9e23b4e1bc6 90), it would highly useful to vary the injection of components into a page on a per-page basis. Example, PageA.aspx has a property ILogger which receives EmailLogger, whereas PageB.aspx has a property ILogger which receives FileLogger. |
||||||||||
,
Jun 12, 2008
Sorry - I should have labeled that as an enhancement. |
|||||||||||
,
Jun 13, 2008
Thanks Jonathan. Will definitely address this in the 2.0 timeframe, meanwhile please let me know if I can help with implementing the workaround.
Status: Accepted
Labels: -Type-Defect Type-Enhancement Milestone-Release2.0 |
|||||||||||
,
Jun 13, 2008
(No comment was entered for this change.)
Owner: nicholas.blumhardt
|
|||||||||||
,
Jun 14, 2008
Creating a custom IHttpHandler appears to be, for the present time, the best solution to work around the problem. This would allow for our custom handler to instantiate the Page class and perform constructor injection. Spring.NET is doing it for old-school web services using the same technique. http://www.springframework.net/doc-latest/reference/html/webservices.html |
|||||||||||
,
Sep 13, 2009
(No comment was entered for this change.)
Labels: -Milestone-Release2.0 Milestone-Release2.1
|
|||||||||||
,
Dec 22, 2009
I'd love to be able to include this but time to complete 2.1 is at a premium, so I'm pushing this to 2.2. If anyone can provide a patch we can look at back-porting. Nick
Labels: -Milestone-Release2.1 Milestone-Release2.2
|
|||||||||||
 Sign in to add a comment
|
|||||||||||
