0

I'm having trouble figuring out what the differences between ASP.NET MVC and Spring.Net MVC are. I understand how ASP.NET MVC and Spring.Net work separately, but I cannot quite sort out what the "MVC" part of "Spring.Net MVC" brings, overrides or changes in the way the ASP.NET MVC framework works/is used ; e.g. should I use "Spring.Net" or "Spring.Net MVC"?

In short, the question behind this is that I want to use ASP.NET MVC, Spring.Net and Telerik's MVC controls and want to be sure that using Spring.Net MVC would not prevent using Telerik's controls. Has anyone had some experience with this?

Thanks a lot in advance!

Timothée Bourguignon
  • 2,190
  • 3
  • 23
  • 39
  • There is a framework called `Spring MVC` for Java. Don't get confused there is no framework called `Spring.Net MVC`, however as @Marijn pointed out there is infrastructure support from the Spring.Net project for MVC 1-3 called `Spring.NET ASP.NET MVC`. Btw. we are running a enterprise app using MVC3, Spring.Net, NH and Telerik with great success. – Andreas Jun 04 '12 at 16:36
  • Thanks both of you, I really mixed up `Spring MVC` and `Sring.Net ASP.NET MVC`. – Timothée Bourguignon Jun 05 '12 at 06:26

1 Answers1

1

They don't conflict. Spring.net MVC adds dependency injection capabilities to asp.net MVC; see details here, including specific web scopes. Many other DI containers supply modules that extend asp.net mvc this way.

Typically, this allows you to wire-up your controllers using the Spring.net DI container, as demonstrated in the mvc 3 quickstart (which ships with the examples). Or, more precise, Spring.net provides its own implementation of IDependencyResolver to return Controllers, ActionFilters and other services the asp.net mvc runtime requests.

Using Spring.NET MVC does not prevent you from using Telerik controls at all.

Marijn
  • 10,367
  • 5
  • 59
  • 80