[SPRNET-1343] Provide initial ASPNET MVC Integration for core DI capabilites Created: 22/Jul/10  Updated: 02/Feb/11  Resolved: 26/Oct/10

Status: Resolved
Project: Spring.NET
Component/s: Spring-NET-WEBMVC
Affects Version/s: 1.3.1
Fix Version/s: 1.3.1

Type: New Feature Priority: Major
Reporter: Steve Bohlen Assignee: Steve Bohlen
Resolution: Complete Votes: 1
Labels: None
Remaining Estimate: 1d
Time Spent: Not Specified
Original Estimate: 1d

Issue Links:
duplicates SPRNET-810 Add Asp.net MVC support Resolved


ASP.NET MVC provides an IControllerFactory abstraction and the (easy) ability to provide your own and wire it into the MvcApplication controller-resolution pipeline to support DI in re: controller dependencies. Spring.NET should provide its own SpringMvcApplication class derived from MvcApplication and register its own SpringControllerFactory implementation that provides for using the container to resolve controllers and their dependencies.

This is the initial very low-level (but quick to implement) introduction of at least minimal support for ASP.NET MVC by Spring.NET.

Note that depending on the release calendar for 1.3.1 in re: its relation to that of ASP.NET MVC3, the level of container integration may be greater than just for controllers since MVC3 is set to support container registration/resolution of types in connection with ActionFilters, ModelBinders, and more so there may be more container-related integration points to explore/integrate with when the time comes.

Comment by Steve Bohlen [ 26/Oct/10 ]

Initial support added.

Generated at Sat Dec 14 00:48:40 UTC 2019 using Jira 7.13.8#713008-sha1:1606a5c1e7006e1ab135aac81f7a9566b2dbc3a6.