How to check if my ASP.NET web application is running as a 64-bit process on a development server with VS2010?

Question

My task is simple: I need to test my ASP.NET web application in a 64-bit environment on my development machine. (At this point, I don’t even ask you to pass it through the debugger. I only need to run it in a 64-bit process.)

So, I created a C # stock web application in Visual Studio 2010 and adjusted its properties as such:

Then I did Ctrl + F5 (or ran without debugging), and IE booted up and hung up like this:

What am I doing wrong here?

PS. Run on Windows 7 Ultimate (64-bit).

Answer 1

We had the same problem, and when the team switched to Visual Studio 2012, this registry key was really useful for us:

you can add a registry key to force visual studio to use the 64-bit version of iisexpress.exe; unfortunately, this is VS2012 solution for you.

reg add HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0\WebProjects /v Use64BitIISExpress /t REG_DWORD /d 1 

Then restart Visual Studio and check [X] Use IIS Express in Settings.

(see also source ).

UPDATE . For reference, in Visual 2013 , this parameter can be found in the interface: Settings / Projects and Solutions / Web Projects / Use the 64-bit version of IIS Express for websites and projects

Answer 2

In IIS, make sure that the application pool, Presets, Enable 32-bit applications = false

If this parameter is true, the workflow will be executed as a 32-bit WOW64 process.

Chris

Answer 3

No settings at the project or solution level. I am developing WebApp on VS2010 on 32-bit and 64-bit machines at the same time. In fact, we are working on SVN, and our few machines have Win7 32-bit, and my few helpers have Win7-64bit laptops. But there we did not encounter such a problem when compiling the application on two different machines and even on a live server, it works with oil. Hardly care about bits and bytes.

To check the test run. Publish your code and host on your local IIS or Cassini web server and access it through your local network.

Also, if possible, revert the solution and project parameters back to the original configuration parameters. As a rule, we do not need to change the goal until it is strictly necessary. Like, AFAIK, it compiles the assembly under "Any CPU" as a target that is suitable for everyone, that is, IA, X64 and X86 ..

Finally, if you encounter any kind of error, please post it here. It will also help you and us.

Answer 4

First of all, how do you know if your IIS process runs on your website as 32-bit or 64-bit? Open the task manager to check the w3wp.exe bit. If your computer is 64-bit, IIS will work by default on the 64-bit version. Your problem seems to be something else. If this is a problem, then you don’t even go that far. Check out the IIS logs (c: \ inetpub \ logs {website-ID} {date}) ... which may give you some pointers. If there is nothing there, check out the event viewer. If there is nothing, check if the virtual directory is really created in IIS Manager under the "Default Web Site" section.

Did you really test if IIS (without ASPX) works? http: // localhost? it works? If this works, I would recommend checking if your ASP.NET modules are correctly installed in IIS.

Hope this helps.