The documentation at http://learn.iis.net/page.aspx/1010/iis-75-express-readme/
says that:
Both 32-bit and 64-bit systems are supported, however only a 32-bit build of IIS 7.5 Express exists.
Why is this limitation there? are there any plans to get a 64-bit build?
I'm getting a lot of OOME using the 32-bit express on my test machine ... how were are supposed to simulate running on the real IIS, if the test server is so limited ...
IIS Express 8.0 has 64-bit support. At the time of writing it's an RC.
http://www.microsoft.com/en-us/download/details.aspx?id=34679
It's now here iisexpress_8_0_RTM_x64_en-US.msi -
http://www.microsoft.com/en-us/download/details.aspx?id=34679
This option is now part of Vs 2013 / 2015:
Tools -> Options -> Projects and Solutions -> Web Projects -> Use the
64 bit version of IIS Express
As of the date of this answer, there is no 64-bit build for IIS express. We all hope this changes sometime soon in the future.
Related
I see the following error with Visual Studio 2015 (Tried both community and professional edition).
Wrote a simple Visual C++ CosoleApplication which has "printf("Hello World\n");".
Debug with Platform "x86" Compile and step through Works.
Debug with Platform "x64" Compiles but when it runs it throws this error.
Code is simple with following lines:
// ConsoleApplication1.cpp : Defines the entry point for the console application.
//
#include "stdafx.h"
int main()
{
printf("Hello World \n");
return 0;
}
My desktop has following configuration:
OS: Windows 7 Enterprise 64-bit version
Anti-Virus: McAfee Anti-virus software running; Can't disable that.
Firewall: ON (Can't disable that for security)
Question: Stepping through the code with (Debug x86 platform) works. Why "Debug x64 platform" does NOT work ?
Any suggestion would be helpful.
Thanks
gshant
I was having the same trouble. This is what I did.
Go to Project, Project properties.
Select Application Tab and make note of what framework you are using. For me it was 4.5.2.
Use the pull down to select a different Framework. At the bottom there is an option to install additional Frameworks.
After the web page opens, select the Framework you previously noted and download the Development Pack.
Close Visual Studio and install the Development Pack.
This worked for me when I selected x64.
Hope this helps you.
Make sure you have both the x86 and x64 .NET Core runtimes installed.
https://www.microsoft.com/net/download/windows
This answer deals with using IIS 7 to debug. I have not checked it with IIS Express.
If your web application is 32-bit (x86), you need to run IIS Manager and:
Look at the "Basic Settings" of your web site. Check what IIS
application pool your project is using.
Look at the "Advanced Settings" of this application pool and ensure
that "Enable 32-bit applications" is True.
This was a firewall issue for me. I'm not sure the exact root cause, but I found stopping my firewall resolves this. If I find the exact root cause, I'll update my answer so firewall exception rules can be written.
I believe the issue is when you are debugging it is actually using the remote debugger still under the hood (connecting x86 Visual Studio to an x64 process, etc) and a firewall can block this.
The solution for me was to go:
Project -> Properties -> Build -> Prefer 32-bit enabled
with Platform target -> "Any CPU".
I am using TFS 2010 and visual studio 2012.
I have created a C# api to connect to tfs. The code works. I used couple of microsoft.foundation dlls. They are using version 2.0
But I had to configure my application pool in IIS on my server (windows server 2008 64-bit) by setting Enable 32-bit applications to True.
The production server doesn't like the 32 bit and is acting up. The dlls can't be used.
I must find the equivalent 64 bit. Can someone point me to where I can find them?
Thank you
#sudhir3, thank you for your suggestion.
Like I said, the code is not an issue and it works, but that involved setting the 32 bit flag on the app pool.
Further investigations lead me to know that there is no equivalent of 64 bit for the 32 bit dll. VS itself is still 32 bit. No near conversion by microsoft to 64 bit is near.
So, I I ended up leaving the IIS 32 bit flag in the app pool set to false and created web api webservice that passed values to a powershell cmdlet, which in turn executes my TFS api code.
I'm looking to set up a local server on my laptop which is running Windows XP Home Edition. I've noticed that it is impossible to install IIS on the Home Edition, but is there a way around this? Is there other software that I can install to run a server?
the purpose behind this is to mess around and play with ASP to create dynamic websites and my only computer I own has Home Edition.
Also, would running a server on my 5 year old laptop with 2GB of RAM be a good idea?
Windows XP Home Edition does not come with IIS (only Professional). There are workarounds available, but Home Edition was not designed for this. Visual Studio (full and express) come with Cassini, which is a version of IIS you can use for testing/development.
What is your desired result?
You can always install Apache. It should work fine on your HW.
This is what I use: http://www.aprelium.com/abyssws/
The X1 version is totally free and works great. You can then add PHP as needed (or not)
Yes there are ways like http://www.15seconds.com/issue/020118.htm
If you are developing using Visual Studio 2005, 8 , 10 you don't need IIS.
The hardware should be fine as you will be the only user accessing the website :)
Download Ultidev Cassini and be happy...Ez to configure and use in both localhost and local network.
Currently I have a set of web applications that need to be installed (using IIS). They can only run in 32-bit mode so requires IIS to be set to run 32-bit apps. The steps that we've taken to do this work for server 2003 64-bit, and 2008 64-bit, but does not work on server 2008 R2 64-bit. I've spent many hours on this and I'm stumped.
The following are the steps performed to get the web apps installed:
1. Set "enable32BitAppOnWin64" app to true
2. Uninstall old ASP.NET stuff using 32-bit version of aspnet_regiis.exe: "aspnet_regiis -ua"
3. Install ASP.NET stuff using 32-bit version of aspnet_regiis.exe: "aspnet_regiis -i -enable"
As mentioned before, the above works fine on server 2003 64-bit and server 2008 64-bit, just not server 2008 R2 64-bit. Steps 2 and 3 give me the error: "Operation failed with 0x8007000B. An attempt was made to load a program with an incorrect format". After some searching, this is something to do with me running 32-bit application (aspnet_regiis) with IIS which is a 64-bit app. Step one has worked, as the flag has been set in the IIS GUI.
Would really appreciate it if someone could tell me where I'm going wrong, and why this doesn't work for 2008 R2.
Thanks
I know its a late post, but what I ended up having to do was run aspnet_regiis on the Framework64 folder and selecting the "Enable 32-bit Applications" on the application pool I was using and my sites came up.
In Vista and higher OS's ASP.NET is part of the OS and needs to be installed. You can install ASP.NET from the add windows features under Web Server.
The v4.0 version should work fine from both 32 and 64 bit folders.
Check for your Windows version.
If its a Windows 32 bit try running 'aspnet_regiis -i' from
C:\Windows\Microsoft.Net\Framework\v2.0.52707 folder
Or If its a 64 bit run it from
C:\Windows\Microsoft.Net\Framework64\v2.0.52707 folder
I know that there are issues with the VFP OLEDB provider on 64 bit machines. ... but what issues do you encounter while actually running a VFP application - on a 64 bit machine? Has anyone had any experience in this area?
My first thought was that it would just run as a 32bit app, without making use of the 64 bit power. However, I ran into difficulties with a FoxPro application connecting to a SQL Server database (probably an OLEDB issue as well). Are there other issues as well?
This is somewhat of a specialized scenario, and it may not be related to 64 bitness, but since you asked...
My organization recently hosted a legacy VFP 7 app on a Windows Server 2008 Enterprise 64 bit server for access over Terminal Services. The app runs fine, but there is some kind of bug with the TS Easy Print technology. When you print from the app to a redirected client printer over Easy Print, the top, left, and bottom sides of each page of the document get clipped. The workaround we use is to have the users print to pdfFactory on the server first, then print from pdfFactory to the redirected client printer over Easy Print. Works great.
This is somewhat of a stab in the dark...but I believe there are some drivers with MDAC that aren't available in x64 windows. I think you may be able to install the normal 32-bit MDAC but it will install to the x86 folder.
We've seen zero problems with our VFP9 apps on 64-bit XP, Server 2003, Vista, or Server 2008.
Our print engine is a VB DLL though, so we wouldn't run into any VFP-specific printing issues.