requirements to deploy the mvc 3 application to the server - asp.net-mvc-3

I want to deploy the application in the Windows Server 2008 R2. But I am wondering if I need to install the .Net Framework 4.0 since the version available in the server is 2.0? Do I need also to install the MVC Framework?

you don't need to install MVC, only dlls can do the task
there are different ways to do it, see links
http://msdn.microsoft.com/en-us/library/dd410407(v=vs.90).aspx
http://msdn.microsoft.com/en-us/library/gg286946.aspx
http://weblogs.asp.net/scottgu/archive/2011/01/18/running-an-asp-net-mvc-3-app-on-a-web-server-that-doesn-t-have-asp-net-mvc-3-installed.aspx

You may use the ASP.NET MVC3 installer,
or simply copy the required dlls into bin directory of your web application
such as System.Web.Mvc.dll,
System.Web.Helpers.dll,
System.Web.Razor.dll,
System.Web.WebPages.dll,
System.Web.WebPages.Razor.dll,
System.Web.WebPages.Administration.dll,
System.Web.WebPages.Deployment.dll,
Microsoft.Web.Infrastructure.dll

Related

What needs to be installed in a Windows Server 2008 R2 to allow it to run ASPNET MVC 4 apps?

I've installed the .NET 4.5 framework using the dotNetFx45_Full_x86_x64.exe installer, and the ASPNET MVC4 framework using the AspNetMVC4Setup.exe installer in a Windows 2008 R2 server, yet I keep getting the message 'There is no build provider registered for the extension '.cshtml'.' while trying to run my ASPNET MVC4 app.
I've fixed this temporarily by adding a buildProviders section in my Web.config, but I would like to know how to setup a server so that I can use the current framework without having to touch my Web.config (the same way I can run them in my dev machine).
This is a shot in the dark, but "aspnet_regiis -i" maybe?
(make sure to run the version in the correct directory on your server)
http://msdn.microsoft.com/en-us/library/k6h9cz8h(v=vs.80).aspx
UPDATE:
Did you also deploy the following .dlls in your BIN folder of your web app?
System.Web.Helpers.dll
System.Web.Mvc.dll
System.Web.WebPages.Deployment.dll
system.Web.WebPages.dll
System.Web.WebPages.Razor.dll

How to set up Windows Web Server 2008 R2 for MVC Applications

What I am looking for and seem unable to find, it's late and I'm tired, is a step by step guide on how to set up windows 2008 server to run asp.net mvc applications.
I am a web applications developer, amongst other things, and can do that bit fine. Normally I let someone else, like the hosting company, worry about the setup and just publish using 1-Click with web deploy or ftp.
However, for this projects I have a local Windows Web Server 2008 R2 installed but I don't know how to set it up to run the application. the deploy works, all the files arrive in the correct folder on the server, but can I get it to work?
No.
Hence the question.
For your information the app is built using Sharp Architecture, MVC3 and Razor and targeted at .NET 4 which is installed on both my development PC and the server.
Any suggestions?
Thanks.
Best thing would be to download Windows Web Platform installer and select the options you want, for example, .NET 4, MVC3 etc etc ...
Then, remember to enable ASP.NET in your IIS (under Roles or something...).

configuring website using windows server2003,IIS6.0 and MVC

I have been going through http://haacked.com/archive/2008/11/26/asp.net-mvc-on-iis-6-walkthrough.aspx but so far I have not been able to configure my website. These are the steps I have done:
Downloaded and installed .net 4.0
I have built and published my website to inetpub/root on windows server2003
I have used IIS to do the cofiguration as per haacked. It seems that despite setting the asp.net 4.0(please see image) in the webservice extensions
did you install MVC on the server? So that it has the MVC DLLs
MVC install
You should change the path to aspnet_isapi.dll to the one from .NET 4:
C:\Windows\Microsoft.NET\Framework\v4.0.21006\aspnet_isapi.dll

Problem with deploying ASP.NET MVC3 app

This question is related to this: Problem with bin Deploying ASP.NET MVC 3 I erase the line with targetFramework="4.0" but now I have another problem. It says:
Could not load file or assembly 'EntityFramework' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.
I can´t get access to IIS server because it is from provider of my hosting. It´s weird because one of my website is running on this server (MVC3 too) and now I am trying add next and it is not working. Thanks for every help.
Have you made sure your provider has .NET 4.0 installed on their server?
It sounds like you are trying to run a .NET 4.0 application on a server that only has .NET 3.5 installed

Why does Windows application is requiring .Net 3.5 framework

I have the Target Framework set to 2.0 on my windows application, yet when I try to install my app on the server, after publishing it through VS 2008, it is trying to install .Net 3.5 on the server.
I do not want to install 3.5 on my server.
When I copy the files from my local /bin/debug/ to the server and double click on the exe, nothing happens. On my local machine, my app runs.
How can I make this app run on the server without it needing the .Net 3.5 framework?
Do any of your dependencies require .NET 3.5? Do you have anything in any config files which might require .NET 3.5?
I suggest you take a copy of what you've got for safekeeping, and then cut it down to the very smallest app which demonstrates the problem. In fact, you might want to start from scratch with a "no-op" app and see whether that has the same behaviour.
Check unused references, perhaps? Are you actually getting an error about the 3.5 framework?
Try building the application in release mode and deploy it to the server. You will need to grab the application from the /bin/release folder instead of the /bin/debug folder.
Also, check the target framework under the application section of the project properties.
If you're using Visual Studio to build your setup project, open the setup project's properties and look through the settings. One setting says which .Net version will be demanded by the installer package. You have to set that; it doesn't inherit from known properties of your other projects.

Resources