Does Server Core 2008 support asp.net? I see references online saying that it isn't supported, but they are all old references from CTPs.
Server Core 2008 does not support ASP.NET. However, Windows 2008 R2 Server Core supports .NET up to 3.5 out of the box, and since 2011-02-21 it can also run .NET 4.0 apps. To enable .NET 4.0 support, you need to install Service Pack 1 and the .NET 4.0 Standalone Installer for Server Core.
No.
Answer here:
http://www.microsoft.com/windowsserver2008/en/us/compare-core-installation.aspx
"ASP.NET is not available with Server Core installation option in any edition"
The short answer, as others have said: no.
The longer answer: IIS is there, classic ASP is there, and other server-side languages such as PHP will work, too. What's missing is .NET Framework, and adding it to Server Core is in the works.
Currenly the .NET Framework is not on Server Core, which means ASP.NET is currently not available. This is something the .NET team wants to add and we're working on adding it as soon as possible.
No
With the new Server Core 2008 R2 you can run asp.net in IIS, but only up to version 3.5. 4.0 is not supported since you cant install .Net 4.0 on Server Core 2008 R2 at all.
Related
This is a very hard question to Google because there are different versions of ASP.NET out there. What I want to know is the versions of Windows Server that support ASP.NET 2.0 (no MVC, no CORE) just the original version that was released back in 2006 (See: https://en.wikipedia.org/wiki/.NET_Framework_version_history#.NET_Framework_2.0)
Thanks!
First, only Windows Server 2012 and above are supported now.
Second, you have to manually enable ASP.NET 3.5 there, which supports ASP.NET 2.0 web apps,
https://learn.microsoft.com/en-us/iis/get-started/whats-new-in-iis-8/iis-80-using-aspnet-35-and-aspnet-45
However, keep in mind that such ASP.NET 2.0 apps are ancient. Upgrade if you can.
I start working on new Web App and still doing the research about the framework to pick. One of the requirements: the app will be deployed to IIS on Windows Server 2008 that has SSL3 certificate. Also the app will be deployed to newer Windows Server with TLS certificate. So the issue I'm facing is similar to this question.
Will .Net Core ASP.Net MVC support both SSL3 and TLS* or Should I go with standard .Net Framework?
If not, What version of .Net Framework to pick?
I could be wrong here, but SSL3 is very old and has succeeded by replaced by TLS 1.2.
If the server is running Windows Server 2008 R2 SP1 (release 2, service pack 1) or greater then I would recommending going with .NET Core.
However, if the server is Windows Server 2008 without R2 then you will need to use an older version of the .NET Framework say 4.6.1.
Before jumping in you should sit down with the decision makers point out that developing a solution on legacy infrastructure holds serious security and business risks.
If I have a server running on .NET Framework 4.0.
Will it be possible to run ASP.NET vNext on top of that? Or will a higher framework version be required?
As stated on Asp.NET vNext's page on GitHub the minimum requirements for Windows as follows:
Windows 7 or Windows Server 2008 R2.
.NET 4.5.1 for hosting in IIS
However, ASP.NET vNext will let you deploy different versions of the .NET Framework via NuGet packages for different apps on server as stated here. But it's not .NET Framework 4.0 anyway. So, you need the higher version.
I have old Web Client Software Factory project built with VS2008, WCSF 2008 and MS Enterprise Library 3.1
I have to make changes to the project so I migrated the solution to Visual Studio 2012. It compiles fine with .NET 3.5 and runs on IIS 7.5 as 32bit web application (classic mode asp.net v2.0).
Is it possible to migrate such project to .NET 4.5 (64 bit)?
My guess is no. The last version of WCSF is 2010 and for the MS Enterprise Library is 5.0.
I think they both are built on .NET 3.5
Did anyone try such migration before?
Thanks
I'm planning to do the same thing for couple of my applications.
I did checked out on MSDN and the WCSF project discussion on codeplex seems there's no future roadmap for this WCSF.
See:
Web Client Software Factory
Roadmap for 2012 and beyond ?
This only references requirements for clients:
http://msdn.microsoft.com/en-us/library/8z6watww%28v=VS.100%29.aspx
I am looking for similar documentation in reference not just for .NET 4, but ASP.NET 4 and what IIS versions, OS SP's, etc. are required. I would like to see if there are any pitfalls to requesting IT to install ASP.NET 4 and MVC 3 on our server. Don't want to have egg on my face :)
Per the documentaiton on the installer download for .NET 4.0 ( http://www.microsoft.com/download/en/details.aspx?id=17851)
Additional Requirements for Server
Installation
If you have to perform a server
installation, your computer must have
the following software in addition to
the basic requirements:
•Internet Information Services (IIS)
version 6.0 or later. To access the
features of ASP.NET, IIS with the
latest security updates must be
installed before the .NET Framework is
installed. ASP.NET is supported only
on Windows XP Professional, Windows
Server 2003, Windows Server 2008, and
Windows Server 2008 R2.
So it will run in IIS 6.0 or above. If you want to know which operating systems support asp.net 4.0, that would be any operating system that supports IIS version 6.0 or above. This jives with my comment on your question.
That said, the biggest thing to watch out for is that you have to configure any .NET 4.0 IIS application to use a different applicaiton pool than 2.0, 3.0, or 3.5. There's more info on this here: http://johan.driessen.se/posts/getting-an-asp.net-4-application-to-work-on-iis6
WinXP has IIS 5 and the .net framework and ASP.NET 4 is supported on it. For server technologies, IIS6 and newer are supported, as Server 2003 which has IIS6 is the oldest server technology that supports ASP.NET 4.