Are there any issues with running an asp.net 1.1 application under windows server 2008 64-bit web edition?
I have never tried it myself, but I did find the following pages that you might find interesting:
This blog has an in depth walk through of configuring ASP.NET 1.1 on Windows Server 2008. The author does not say if it is x86 or x64, so I would just assume its x86. But either way, it looks like the author had to jump through some hoops to get the ISAPI filter setup correctly.
I also found this thread on the IIS7 forums where someone discuses having poor performance from ASP.NET 1.1. on x64 Win2k8. So from poor performance I would assume it worked to some extent. Unfortunately towards the end of the thread the author mentions encounter 500 errors, and then the discuss stops :-(
So from what I've read I would guess that its possible, but I would also guess that you would have less hassle if you could find some alternative that didn't involve both II7 and x64.
I have recently been testing our application on 64 bit 2008. Our application is .net framework 3.5 but we had a few problems.
The main issue we had was with 3rd party components such as Aspose words which were not built for 64 bit and caused an error. Unfortunatly you wont know without trying it..
.NET 1.1 is 32 bit only hence the app pool would have to run as 32 bit and use the classic pipeline. I haven't tried myself and I would do all that I can to not have to install .NET 1.1 on a 2008 server but it should work.
No problem. Just follow intructions on
http://learn.iis.net/page.aspx/472/how-to-install-aspnet-11-with-iis7-on-vista-and-windows-2008/
The option "CGI Restrictions" (last step) is found on IIS7 admin by clicking on the machine name.
I'm pretty sure that the article at http://learn.iis.net/page.aspx/472/how-to-install-aspnet-11-with-iis7-on-vista-and-windows-2008/ is for NON-R2 versions of Windows Server.
As far as I know ASP.NET 1.1 cannot run (or at least, not run well) on Windows.
There are some band-aid solutions around that various people have posted / blogged but this isn't supported by Microsoft.
Related
I hate to ask a question that seems like it should be easy to find the answer to on the web, however I am unable to find a straightforward answer anywhere as to how to check what version of ASP.NET is installed on my Windows Server 2008 r2. Any help with this would be much appreciated. Kind regards, Jon
Read registry key, HKEY_LOCAL_MACHINE\Software\Microsoft\InetStp\Components\ as documented in
https://learn.microsoft.com/en-us/iis/install/installing-iis-7/discover-installed-components
As you use IIS 7, its "ASP.NET" feature matches ASP.NET 3.5 you are looking for. If you want to check ASP.NET 4.x, then this approach won't work.
Generally speaking, the ASP.NET component in IIS wraps over aspnet_regiis command line tool to register ASP.NET bits on IIS (ISAPI and so on). Microsoft designed it this way so it felt more natural. However, it turns out to be a disaster later, as .NET Framework new releases can easily break the design.
For example, on IIS 7 if you use ASP.NET 4.x then you have to manually run aspnet_regiis from .NET Framework 4.x installation folder, as there is not ASP.NET 4.x component on IIS 7.
You can go to
C:\windows\Microsoft.NET\Framework
and check if there is v3.5 folder
I have an ASP.NET (Webforms) working with .Net Framework 4.0.
If I deploy that site with osFamily="1" (on a Windows 2008 server) the .NET CLR takes 120 ms average (according to NewRelic logs).
If I take the exact site and I deploy it with osFamily="3" (on a Windows 2012 server) the .NET CLR takes more than 500 ms.
I know I should move to MVC4 and perhaps .Net Framework 4.5, but I would like to know if anyone else has had the same problem and if you know what could be causing this?
Edit
Looks like osFamily=2 also has the same problem.
From the forum discussion it seems that it's a known issue.
The issue is reported here.
Upgrading from VS2010 to VS2012, we noticed that deploying is very slow, which can be worked around but then stepping in code is very slow as well.
First, we thought it maybe the device but it is very slow even in the emulator. This machine we tested, is i7 processor with 12MB of RAM. This also seem the case for many who have reported on our forums.
Read more.
A solution seems to be the changing the driver to winusb (C:\Program Files\GHI Electronics\GHI Premium NETMF v4.2 SDK\USB Drivers\GHI_NETMF_WinUsb) - according to one of the comments.
http://social.msdn.microsoft.com/Forums/windowsazure/en-us/7cf664b0-5876-4d6a-b54d-fda46c544c6f/azure-deployment-slower-with-w2012-server-than-w2008-server-or-w2008-server-r2?forum=windowsazuretroubleshooting:
'I tried with .NET 4.5 with the same results. I think is something related to Azure SDK 1.7 & 2.0
Programmatically configure Azure cache client' Answer by Jordi Torra
It seems to be a problem with the Azure SDK 1.7 & 2.0.
I just got application written in ASP.NET and VB, can i deploy it on any IIS?
Are there any files in project with that kind of information?
There are no files or magic numbers anywhere that can tell you this. Chances are preety good that it will run on a newer versions of IIS but even then your goign to need to know what functionality it requires. For example is it using WebDav? IIS is preety good at being backwards compatible but forward compability not so good. For example IIS7 introduced new functionality which if the application is using it, would prevent it from running on IIS6.
Do you know what version of .net it requires that is more likely to bite you then anything else?
Any IIS that supports ISAPI, I guess, but IIS 5.1 + is recommended (.NET probably won't run on OS that run IIS4 anyway).
Here is a good MSDN link detailing which IIS version comes with which version of Windows as well as useful links for configuring it.
ASP.NET and IIS Configuration
IIS 6 is the minimum for recent .NET versions (i.e. Windows 2003) because Win2000 is not supported (considering server only here).
The Windows version will tell you the IIS version:
Server 2003: IIS 6
Server 2008: IIS 7
Server 2008 R2: IIS 7.5
Also XP: IIS5.1; Vista: IIS7
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.
So, much to my annoyance I discover (after lots of research), that when running 1.1 and 2.0 dot.net frameworks on a 64bit 2003 install, it removes the asp.net tab from the IIS properties. I've tried the registry hacks, I've tried registering 32bit versions of both frameworks, and no luck. My only work around is running the excellent ASP.NET switcher from Dennis Bauer.
Does anyone else have any insight?
Also, you might try running the 32-bit version of MMC. IIRC, MMC can only load extensions that are the same bit-ness as itself, and the .Net 2.0 extension is 32-bit only.
That said, the tool you linked in your question is very useful for working around this issue as well.