Can someone tell me if its possible to run both a 64bit compiled web site and a 32bit compiled website on the same IIS7.5 machine. The core OS would be Windows 2008 R2 64bit. I looked around and can only find how to switch the appPools to 32 or 64. But the question I want answered is can you have one appPool 32bit and another 64bit? If you can link to some articles that would certainly help. Thanks.
Yes, it's no problem to have differing "bitness" on different application pools.
http://blogs.msdn.com/b/rakkimk/archive/2007/11/03/iis7-running-32-bit-and-64-bit-asp-net-versions-at-the-same-time-on-different-worker-processes.aspx
-Oisin
Related
Is it possible and an acceptable solution to use a machine with windows os (not windows server) to host an asp.net website? Is all I need IIS regardless the os?
Yes it is possible. if your working with asp.net all you need is IIS witch is only integrated with Windows platforms. on the other hand if you're working with asp.net core it does not require IIS and can also be deployed to linux platforms.
I'm working on an ASP.NET project in Visual Studio 2010 remotely (over lan) on a very powerful windows server machine. I work for a small non-profit and the previous developer wrote and developed on this machine, so I came in and have been constricted to this setup. Visual Studio seems to run a bit slowly/choppy on this OS. I'm wondering if this is normal and if it is a better practice to develop locally on my Windows 7 machine.
Most developers I know run Visual Studio on their local machine. Everyone's case is different, so there's really no way for us to answer this question without actually being there. So do it, and see what works better for you. No one on SO can answer this for you.
I ran Server 2008 as a desktop OS on my previous machine for about 3 years - 4GB RAM, AMD CPU, had no problems developing with it so I don't think it's the OS per se, unless it's been installed or configured badly.
But no, that's not a normal scenario, it's never a good idea to do all the development on the production machine.
The slowness/choppiness could be a number of things: -
if the machine is being used to host the application you're developing, is the application actually in use while you're developing ? If the server is periodically or regularly under load, this could account for slowness
if the above is true, please tell me the actual ASP.NET website is a copy of the development codebase, and you're not just compiling the site in-place.. as it's being used.. the horror
is the machine doing anything else ? Is SQL Server also running on that machine, is it sending emails, are there some app-related windows services ?
have you tried profiling the application, or at least using PerfMon to see what's going on ?
any driver issues ? have you checked the eventlogs ?
how fast is your internet connection ?
In short it could be a number of things, but the development experience on Server 2008 should be no different from Vista, Win7 or 8.
I'm working on restructuring a website written in ASP .NET. I'm working on Vista machine with 2010. The intended deployment server is 64-bit machine running IIS.
Now, I know that exactly same code will work on both the machines, but I may have to compile the code differently for the deployment server. Can anyone guide me regarding correct settings for this & place to change these settings?
Thanks!
Just set "Any CPU" as a Platform in your project properties. You can access it through
Build->Configuration Manager...
And you site will work on both x32 and x64
I’m trying to install a 32-bit ASP.NET application onto a 64-bit IIS server running on Windows Server 2008. This is a clean installation of the operating system with no other applications installed.
As a prerequisite for our installation, we run the 32-bit version of aspnet_regiis –i
It fails with the following message:
The error indicates that IIS is not installed on the machine. Please install IIS before using this tool.
Additionally:
IIS is definitely installed.
The 64 bit version of aspnet_regiis runs cleanly without warnings.
“Enable 32 bit applications” is set to True in the DefaultAppPool’s Advanced Settings.
The IIS Metabase and IIS 6 configuration compatibility” component is installed.
We have a test VM where this error occurs as well as test VM where both the 32 bit and 64 bit versions of aspnet_regiis run without errors. We've had no luck distinguishing the differences between the two test VMs.
We have struggled with this issue for several days to no avail. Any suggestions would be greatly appreciated!
Is it necessary to run aspnet_regiis? 32 bit asp.net should already be installed and running on iis7, all you should need to do is set the app pool to “Enable 32 bit applications” and set you web app to use that app pool. You do not say what happens when you install/setup your web app, do you get any errors when you try to access it in a browser?
Problem solved! Apparently the issue stems from Windows Server 2008 (R1). Applying the SP2 update to the operating system cures the problem. Later iterations of the OS don't seem to exhibit this behavior.
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