Will ASP.NET MVC 3 run on Windows Server 2008 R2 Core? I've done some searching and can't seem to find this information.
Thanks
I just set up a Windows Server 2008 R2 in Server Core configuration. I installed MVC3 using the standard installer:
.\AspNetMVC3Setup.exe /q /log C:\mvc3setup.htm
This installed successfully and a sample MVC3 site works just fine.
According to the Server Core Installation Option Getting Started Guide, Windows Server 2008 R2 Core supports Web Server (including a subset of ASP.NET). Based on some to the additional features you can install (optional features) it looks very limited.
The red flags that stand out for me on the optional features are:
Subset of .NET Framework 3.0 and 3.5
Subset of .NET Framework 2.0
Based on the documentation, I come to the conclusion that running MVC3 would be very difficult and not possible.
Related
I would like to update my PowerShell from v2 to v3 but when installing, I get a message "Update not applicable to your computer". I tried to install the Windows6.1-KB2506143-x64 Windows Management Framework 3.0 - RC because I am practicing scripting but I can not use the scripts that I am learning in v2.
I do not have a virtual machine.
What is the problem?
Make sure you meet the system requirement of .net 4.0
Windows Management Framework 3.0 requires Microsoft .NET Framework 4.0"
The full release of PowerShell and the Windows Management Framework 3.0 has been released, I would suggest using it instead of the release candidate version you mentioned. You can find download links here: http://go.microsoft.com/fwlink/?LinkId=251995
The supported systems matrix is tighter than previous releases - you have to be running one of the following operating systems with the correct service pack level as well:
Windows 7 Service Pack 1 (32-bit & 64-bit)
Windows Server 2008 R2 Service Pack 1 (64-bit only, includes Server Core)
Windows Server 2008 Service Pack 2 (32-bit & 64-bit)
Also note, if you have any of the pre-release builds of v3 installed, you will have to remove them before installing the officially released version.
Whatever I do for several days now, Web Developer 2010 Express does not see 4.0 NET Framework. If to right click on solution properties in the Application – Target Framework it lists 2.0, 3.0 and 3.5, which are NOT installed on my computer but 4.0 which is actually installed. I tried to clean all using dotnetfx_cleanup_tool, reinstalled 4.0 client and full several times, copied reference assemblies to different folders and so on but WDE still does not see it.
I also have SDK for Windows 7 and .NET Framework 4 installed.
Where and how does it find frameworks, does in scan registry or some config file?
To target .NET 2.0/3.0/3.5, you have to install .NET 3.5.
And Web Develoepr requires full profile, not client profile.
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
I have installed ASP.NET 4 using the Web Platform installer of a Windows 2008 SP2 Server with IIS7.
The MVC sites work fine, when I set a default (created at an install time) ASP.NET 4.0 application pool to it.
But when I want my site to have it's own application pool, I am unable to create a new pool with .Net Framework 4 support - only .Net 2.0.
Is it a correct behaviour of IIS7? Do ASP.NET 4 apps all have to be hosted in the same default ASP.NET 4.0 app pool?
In command prompt type cd C:\Windows\Microsoft.NET\Framework\v4.0.30319\ and run aspnet_regiis.exe -ir. That should help you.
In Visual Studio 2008, the target framework settings for a project are
.NET Framework 2.0
.NET Framework 3.0
.NET Framework 3.5
However, in Visual Studio 2010 they are
.NET Framework 2.0
.NET Framework 3.0
.NET Framework 3.5
.NET Framework 3.5 Client Profile
.NET Framework 4
.NET Framework 4 Client Profile
What do the Client Profile settings mean?
Edit
A little more experimentation shows that with MVC, WebForms and WCF projects you don't get the Client Profile options. When creating WinForms and Console applications, the default target framework is .NET 4 Client Profile. Which makes sense.
The client profile is a smaller version of the full .NET framework that contains only the more commonly used content. Scott wrote a nice post about this. Here and here is an official introduction.
The client profile was added recently, so VS 2008 does not know about it yet. The client profile is one of the major features that come with .NET 4 and VS 2010. Since the Client Profile is a subset of the full .NET 4 framework, you don't need to install it if you already got the full .NET 4.
It can be an advantage to develop against the Client Profile since it exists on more machines than the full framework (and it is smaller in download size for your customers).
The disadvantage that comes along naturally - it does not include everything. If you are developing a server application or a program that uses uncommon parts of the framework, you'll need the full framework in any case. Typical client programs, however, are likely satisfied with the Client Profile.
The Client Profiles are smaller, more compact versions of the .Net Framework. More info here.
It is a subset of the .NET framework for CLIENT applications (i.e. applications installed on the client computer).
As such, they do not incorporate server technologies. THis allows the client download to only install a smaller part.
Server technologies are for example ASP.NET.
Using ".net client profile" as search on Google, first link leads to http://msdn.microsoft.com/en-us/library/cc656912.aspx which has a detailed explanation.
Also the local .NET documentation (F1 - I hope you are aware this exists) has the same content.