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.
Related
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.
We had an ASP.NET site that was built on .NET 2.0. It had sharepoint integration and everything was working fine until the site got migrated to .NET 4.0. I know that sharepoint is built on 3.5 framework and hence it is failing now. Are there any workarounds or any latest developments to make sharepoint work on ASP.NET 4.0 site?
Me and my string.IsNullOrWhitespace / named parameter loving self wishes this was possible, but it most assuredly is not yet possible. The closest you can get is if you were to utilize SOA and (obviously) your services could be written in .NET 4.0 (or any language for that matter), but your web parts, workflows, feature receivers, modules, etc are stuck in legacy 3.5.
Additionally, the "next" edition of SharePoint (SharePoint Online) which is part of Office 365 is just SharePoint 2010 with cloud compatibility... and still no .NET 4.0.
I have an unconventional legacy asp.net 1.1 web app that uses the src attribute in the page directive that utilizes JIT compile on the server as supposed to the normal compile of assemblies in Visual Studio 2003. We are approaching performance capacity limits of the 32-bit platform it's on and would like to migrate to a 64-bit capable asp.net version. I'm unsure of the best migration path to take: migrate to 3.5 or 4.0?
What are the pros and cons of going with either version? Is 3.5 in the process of being phased out? Is 4.0 established enough for high-traffic web sites in production environment? Does the same web app in 4.0 require more CPU and Memory resources than in 3.5? (new server needed?)
Thanks!
You might want to look at this:
http://support.microsoft.com/kb/894435
You will either migrate to 2.0 first or do a complete re-write. The main jump is from 1.1 to 2.0 and you need to do this manually. You can easily use the VS wizard to then convert to 4.0. Forget 3.5; it was an interim release and the config files are horrible.
As for your dev env, note that VS will remain 32-bit for a long time to come.
Both are very production worthy. It is your choice whether you can live with or without the features ASP.NET 4.0 gives you.
To address one specific point:
Is 3.5 in the process of being phased out?
.NET 3.5 is a system component of Windows 7 and 2008 R2: therefore it will be supported until those OS's go out of support. This is currently 2018 for Server 2008 R2 (see here).
We are starting developing new web-based application in weeks times.
Which version of asp.net would you guys recommend. ASP.NET 3.0 or ASP.NET 4.0 (visual studio 2008 or Visual studio 2010)?
Previously we have worked on ASP.NET 2.0 using visual studio 2005
Same with sql server should we keep using sql server 2005 or migrate it to sql server 2008
If you are starting a new project and you don't intend to use third party libraries that are not compatible with .NET 4.0 then go for ASP.NET 4.0 (Choose Visual Studio 2010 as 2008 cannot target .NET 4.0). As far as SQL Server is concerned, because this is a migration you might need to first analyze what would be the possible impacts on your current infrastructure.
If you have the tools available, and you host the site yourself (not paying a 3rd party hoster) than there is no reason to not use VS2010 and .net 4. If you do have a 3rd party host the site, they may not yet support .net 4.
At the very least, you should use VS2010 and target .net 3.5. That way when you are ready to go to .net 4, it will be an easier switch.
Agreed. If you have the tools, definitely go with 4.0.
VS 2010 is great.
If you start a new project with moderately out-dated tools, you'll soon find that you are maintaining a project with very out-dated tools. Start with the latest stable tools and you push out your upgrade costs a little further.
I would say generally that the same goes for SQL Server. Assuming you have no licensing problems or existing infrastructure, go with the latest version. SQL Server 2008 was not nearly as big an upgrade as VS 2010. You won't have any trouble with a transition to the new tools, etc.
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.