ASP.net MVC3 & Spring.net - asp.net-mvc-3

What is practical difference between ASP.net MVC3 & Spring.Net. What would you suggest to use for a new application. Does Spring.net is actively developed and supported?
And whether both are compatible with each other and can be used together?
Any idea would be highly appreciated.
Thank you

Spring.NET is a Dependency Injection framework for .NET.
ASP.NET is a framework for developing web applications on top of ASP.NET using the MVC pattern.
So it's like asking What is practical difference between an apple and an orange.

Related

Is there DevExtreme support ASP.NET Core 6.0 MVC?

I used DevExtreme v22.3 but it doesn't support for ASP.NET Core 6 MVC. I used it good but it not working in some case (DataGrid, Popup, ...).
Can I have some advice for it?

How can i achieve hot deployment in asp .net core mvc project

I am thinking about how can i achieve hot deployement in asp .net core mvc project. I would appreciate if you could answer my question.

Will the next MVC 6 be part of ASP.NET 4.6 or ASP.NET Core 1.0 or both?

I am mostly interested in the unified Web API in MVC 6 for building restful services. However I am a bit confused at the moment on how these components fit together. When building a new app with the latest Visual Studio 2015, MVC 6 is available as an ASP.NET 5 template. My understanding is that ASP.NET 5 is now ASP.NET Core 1.0. What does this mean for MVC 6 and how will it be supported in the future? Will it be part of the ASP.NET Core 1.0, ASP.NET 4.6 or both?
Could someone please explain how these components fit together? Thanks!
ASP.NET Core is the unification of MVC and WebApi.
It can run on the .NET Core framework or on the .NET full desktop framework.
The MVC design pattern is still there but there is less reason to call it "MVC" when talking about it. In the old days we talked about "MVC" to distinguish it from other things like WebForms or WebPages, but ASP.NET Core doesn't have those other things so calling it "MVC" is not really necessary. It was earlier called "MVC 6" but that was before everything got renamed to ASP.NET Core.
You can find a good explanation here: ASP.NET 5 is dead - Introducing ASP.NET Core 1.0 and .NET Core 1.0
In few words:
ASP.NET 4.6 is the newest version of the ASP.NET we have known so far. This version is available right now.
ASP.NET 5 was going to be the name of something that wasn't a newer version of the ASP.NET we've used so far. SO Microsoft decided to rename it as ASP.NET Core
MVC 6 was the name of the MVC included in ASP.NET 5, so this name no longer make sense
One of the characteristics of ASP.NET Core is that, as you're asking, the MVC and Web API controllers are unified (which aren't on ASP.NET 4.6). But another very interesting thing is that ASP.NET Core runs on OSX, Linux and Windows, and there are available tools to develop thiskind of projects on these 3 platforms.
ASP.NET Core runs on .NET Core (previously named .NET 5), which is a "reduced" version of the .NET CLR that runs on OSX, Linux and Windows.
ASP.NET Core is already incomplete: it doesn't include SignalR or Web Pages so far, but it expected in the future.

visual studio tooling for mvc in asp.net website project

Can anyone help me. I could not find a solution to enable visual studio mvc templates in a asp.net web site project(not a asp.net web application project). I know that in a asp.net web application project is possible, but for asp.net web site project i havent found a solution.
Can anyone help me.
Thanks a lot.
MVC is designed to be a Web Application. There are no Microsoft templates for an MVC 'Web site'. Overall IMHO the benefits of a website are not worth the features you lose.
Here is an article provided by MSDN that explains the different features of each : http://msdn.microsoft.com/en-us/library/dd547590(v=vs.110).aspx
To answer your question directly though. MVC asp.net must be a web application.

What affect will upgrading from ASP.NET MVC2 to MVC3 have on NHibernate?

How do I upgrade ASP.NET MVC2 to MVC3 with minimal possible implications to NHibernate?
There's there should be no impact in terms of NHibernate if you properly separated concerns in your application by using abstractions. As far as upgrading an ASP.NET MVC 2 application to ASP.NET MVC 3 application is concerned you could follow the upgrading steps mentioned in the release notes or even try the Upgrade Tool.

Resources