I moved some Classic ASP sites from Windows Server 2003-32 to 2008-64.
It required few adjustments. All is running smoothly.
Now I'm moving these same Classic ASP sites to Windows Server 2012-64.
Are there any big differences [in respect to running Classic ASP] between 2008 and 2012 I need to know about?
It seems like 2008 maintained much backwards compatibility with Classic ASP and I want to make sure 2012 still supports Classic ASP as well.
Primarily I'm looking for suggestions as to any IIS settings I need to change. Luckily, I'm not depending on any 3rd party components. Note: I'm using CLSupload, which is merely some functions that rely on Microsoft ActiveX Data Objects 2.5 Library 2.5.
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.
Plain and simple: Is it even possible for a SignalR Application to run off IIS 8.5 on Windows Server 2012 R2, or is this not a compatible setup? There are tons of threads all over Stack Overflow that pose the same issue, that the dynamically generated script located at signalr/hubs is 404ing, but the threads with solutions are not using my iis/server setup.
I tried following the tutorial at https://learn.microsoft.com/en-us/aspnet/signalr/overview/getting-started/tutorial-getting-started-with-signalr but it seems that it only works in Visual Studio's IIS Express. As soon as I move the application to our server, I get the error everyone else on SO is getting.
Here's the supported platforms for Signalr on the official documentation:
https://learn.microsoft.com/en-us/aspnet/signalr/overview/getting-started/supported-platforms
It stops short of Windows Server 2012 R2, but the documentation is dated. Any advice is appreciated.
Yes, Windows Server 2012 R2 and Windows Server 2016 both support SignalR. Just ensure WebSocket support is enabled and you're all set.
IIS Express is a cut-down version of IIS (which frustratingly does not work with IIS Manager), but internally it uses the same execution engine (including HTTP.sys integration) so it uses the same web.config files as the full-fat IIS too, so it supports SignalR too.
("IIS Express" is a thing because previously VS shipped with a simple web-server called Cassini, which used ASP.NET System.Web.dll for everything, which worked for simple applications but for more complex applications there was sufficient differing behaviour that it made development difficult)
I am wondering if it is better to develop .Net 2010 web application on XP as compare to Vista? I have developed many .Net applications on XP without any problem and personaly like XP over vista. Now i have started a new job and we are all mainly using Vista Ultimate 32 bit.
Are there any known issues with vista for VS2010 development?
Application will be published on Window Server 2003 or 2008 so my main concern is developing and running application localy.
Also, is Visual Source Safe 6.0 Compatiable with Vista?
You'll have some difficulty since XP is only 32 bit (unless you've got the 64-bit edition which is a little flakey re: drivers).
Also, certain features like XNA Game Studio, Windows Phone 7 development, DirectX 11, etc... just aren't supported on an XP development environment.
You may also hit issues with regards to integrating with the Azure cloud platform as it has some dependencies that don't work fully on XP.
That said, if you're only going for a simple Winforms/Console app/ASP.Net site, you probably won't ever notice the difference
Oh and .Net 4.5 isn't supported on XP
As an aside, please DO NOT USE visual source safe - it's truly awful. It doesn't guarantee consistency, has no concept of branching and merging, doesn't allow multiple users to work on the same files and is generally unreliable (not to mention the fact that it relies on every client playing nicely and a single malicious user can drop the entire data store since it's really just a windows share with some files, not an actual server). See this article: Visual SourceSafe Version Control: Unsafe at any Speed? for more details.
You should use TFS or an open source alternative (I've also played with SVN and used AnkhSVN to integrate into VS - Not perfect but pretty good). If you want to use TFS but don't have the servers/experience to set up a server yourself, There's a (currently free) beta being run by microsoft at tfspreview.com which integrates right into VS 2010 SP1 and later and provides all the same functionality as well as a whole slew of other features like bug/workitem tracking, analytics, etc...
We have a legacy system that uses both classic ASP and VB6/COM+, and are planning a migration to the .NET stack.
We are attempting to develop a migration schedule, and one key driving point will be "when will our old stuff stop working?".
For VB6/COM+, Microsoft has stated that it has no plans to include the VB6 runtime in versions of Windows after Windows 7 (yes I am aware that this is open to interpretation).
I have yet to find a similar statement for classic ASP. I have seen people reference the Microsoft end-of-life schedule for Windows 2008 Server R2 (which is sometime in 2018) and infer that:
(a) since classic ASP runs on Win2008R2 and
(b) Win2008R2 is good until 2018 then
(c) classic ASP is good until 2018.
Not sure I buy that, especially because we have contractual obligations to support new versions of Windows xx months after they come out, so staying on Win2008R2 as a solution is not an option.
Can anyone point me to something from Microsoft concerning end-of-life for classic ASP?
It will stay with us for some more years to come, according to this blog post:
Here's some interesting news from ScottGu and team. I was wondering what the lifecycle for ASP "Classic" was. I looked on the Microsoft Lifecycle page and didn't see it. I was fortunate enough to talk to ScottGu as well as Rich Ersek and was told:
Classic ASP is actually very much alive. It will ship again with Windows Vista and Windows Longhorn Server – so will be supported at least 10 years from that ship date. - ScottGu
and
Asp.DLL is part of VISTA so the runtime will continue to be supported based on the Vista support lifecycle.
All classic ASP development tools (i.e., Visual Interdev) are now in their extended support period and we will not be updating tools for classic ASP.
To get the best tooling/platform option ASP.NET is the way to go. - Rich Ersek
Windows Vista final release date as far as I've found is January 30, 2007 so it means classic ASP will be supported in new versions at least until 2017 and probably much further.
Scott Guthrie is Microsoft's Corporate Vice President, Server & Tools Business so he knows what he's talking about.
Edit: Finally (January 30th 2012) - official confirmation that classic ASP is going to stay with us for long years, including Windows 8:
The next major version of Internet Information Services (IIS) will be shipped as part of the Windows 8 operating system. The use of ASP pages will be supported on Windows 8 for a minimum of 10 years from the Windows 8 release date.
Here is a technet article on how to install on Windows Server 2012, so it should be supported for a long time...
http://technet.microsoft.com/en-us/library/hh831387
if you scroll to the properties section of that article it says it applies to Microsoft Active Server Pages 4.0. it doesn't say classic asp, or asp 1.0, or asp 1.1.
http://support.microsoft.com/kb/2669020
I have a web solution which uses ASP.NET AJAX Controls and has been running on Windows Server 2008 32 bit machine very well.
Now the server admins want to move this web to a new Windows Server 2008 64 bit machine, I was just wondering if ASP.NET AJAX is compatiable to this system, I can't seem to find anything about this issue by googling (Maybe I wasn't asking the right questions :)). Do I have to build the .dll's specifically for a 64 bit machine ? Is AJAX included for machines with .NET framework 3.0 installed (my solution is in .NET 3.0) ?
No, you don't have to build a special version for the 64-bit machine, that's the beauty of managed code as it isn't compiled for a specific platform until it is actually being run by the VM.
Also, AJAX 3.5 is included in .NET Framework 3.5, so you might want to install that.
Here's a blog post covering this issue.