ASP.NET MVC 4 application can't run on .NET 3.5 - asp.net

We have 1 prod and 1 dev server, both running .NET 3.5. I'm trying to build an ASP.NET MVC 4 application, but it requires at least .NET 4.0.
I can't just buy another IIS server and we can't upgrade our existing ones because there are other much larger applications that run on .NET 3.5.
What are my options?

If you cannot upgrade to .NET framework 4.0 then and are tied to .NET framework 3.5 then you will have to downgrade your application to MVC 2.0. Which ought not to be difficult UNLESS your using LOTS of NEW features which are only in MVC 4.0 and not in MVC 2.0 Also having said that, you may even be able to create workarounds to some of them if not all of them.

You can run Asp.Net 2.0 and Asp.Net 4.0 side by side. Find more information here
http://msdn.microsoft.com/en-us/library/a99txfy5(v=vs.100).aspx

Related

How can I run .Net 4.5 Web application on Windows 7 for end user which has .Net 3.5 by Default?

We have existing web application which is developed on .Net 3.5 but we wish to now upgrade it to .Net 4.5. But I want to make sure that it runs even on windows 7 OS without .Net framework 4.5. Is that possible with any workarounds?
The simple answer is NO. You'll need to install .NET Framework 4.5.

Does ASP.NET 4.5 require .NET 4.5 (or is 4.0 sufficient?)

There there is various information around, for example from Microsoft about the new features of ASP.NET 4.5.
http://www.asp.net/aspnet/overview/aspnet-and-visual-studio-2012/whats-new
However, they do not talk about .NET versions, only of ASP.NET Versions.
Is .NET 4.5 required (on the server) for ASP.NET 4.5? (or is 4.0 sufficient?)
Yes, you must install .NET 4.5 on the server if you want to run ASP.NET 4.5 applications. ASP.NET and .NET come bundled - you cannot have one without the other.
Some of features needs it.But you dont have to install if you are an end user
detailed information : http://msdn.microsoft.com/en-us/library/ms171868(v=vs.110).aspx

How to run asp.net 4.0 websites on asp.net 3.5.?

i have an application developed in 4.0 asp.net. and i want to make some changes but i am using 3.5 asp.net.
is it possible? or i will have to download 4.0 version.
i modified the web config file according to 3.5 version........but it does not work.
It doesn't like .NET 3.5 to .NET 2.0, .NET 4 is a significant update. It's better to install .NET 4.

Will the MVC 2.0 assemblies compiled against 3.5 and 4.0 live side-by-side in the GAC?

We are upgrading some of our VS2008 solutions to VS2010, but we are not yet prepared to go to .NET 4.0 on all our projects. At the same time, we are looking at a move from MVC 1.0 to 2.0. I know that there are MVC 2.0 assemblies/code compiled against both the 3.5 and 4.0 .NET Frameworks, but will these two MVC versions live side-by-side in the GAC of a single machine? Meaning, can I deploy both an MVC 2/.NET 3.5 site and also an MVC 2/.NET 4 site on the same server, provided that the server has both frameworks installed and I have run both the "MVC 2 2008" and "MVC 2 2010" installers?
There is only a single System.Web.Mvc.dll v2 assembly, and it is compiled against .NET 3.5. (Though it will also run correctly on .NET 4.) The end result is that if you have MVC v2 GACed, it will automatically operate correctly on both ASP.NET 3.5 and ASP.NET 4 sites.
The only thing you need to worry about is if you are putting your own assemblies in the gac, and you have the same dll in both .net 4 and 3.5. If so just use different version numbers and different snk.

Is ASP.NET MVC 2 Bin-deployable?

I know that ASP.NET MVC 1.0 is bin-deployable as explained in Phil Haack's article.
Is ASP.NET MVC 2.0 also bin-deployable? Has anyone done this already that can point out potential pitfalls specific to version 2.0 if there are any?
I would like to deploy a relatively simple ASP.NET MVC 2.0 onto a Windows 2008 Web server that does not have ASP.NET MVC 2.0 installed. It is running .NET Framework 3.5 Service Pack 1.
I have deployed a MVC 2 application and it works fine! The release is at RTM and would suggest that its bug-free, with a few child-problems i guess! =)
If your server (IIS7) or similar dont have MCV.dll you have to choose on your .dll (Copy Local: Always)

Resources