64-bit and Visual Studio 2005

We keep receiving questions about Visual Studio 2005’s support for 64-bit.  Here is a set of factoids that should help answer the most commonly enquired issues:

(a) There are two flavours of 64-bit – AMD64 or X64, and IA64.  Windows 64-bit installs on both architectures.

(b) There is no 64-bit version of VS. Visual Studio 2005 is available only as a 32-bit app.  However, you CAN install VS on a 64-bit OS and use it to create, launch and debug 64-bit apps. 

(c) VS will install only on X64.  The .Net Framework and the Debugger components install on IA64, allowing you to remotely launch and debug applications on IA64 from a VS IDE installed on another machine.

(d) VS installed on either 32-bit or 64-bit OS can create 32-bit or 64-bit applications, but of course the applications need the corresponding platform to execute.

(e) You need the Professional or Team System versions to build X64 (AMD64) apps. 

(f) You need Team System to build IA64 apps. Pro does not support this. See http://msdn2.microsoft.com/en-us/library/hs24szh9(VS.80).aspx

(g) On a 32-bit OS, the 64-bit compilers will not be installed by default, you will need to go to custom setup and check the option.

How to create 64-bit apps

A managed project is automatically built according to the architecture selected => default C# project created on AMD64 will be AMD64, X86 on X86.  The native one is always 32-bit by default.

To explicitly set a platform:

(1) open the solution explorer, select solution, right click->Configuration Manager.
(2) go to ‘Active Solution Platform’, click New.
(3) in the ‘New Solution Platform’ dialog that comes up select the new platform say Itanium. Set ‘Copy Settings From’ to ‘Any CPU’ which was the default setting in the ‘Active Solution Platform’.
(4) click OK.

You will see that the platform has changed to Itanium in the config manager.  Now when you build the  solution, you will get an Itanium exe.

Follow the same process for X64, and to rebuild 32-bit apps from that solution.


Comments (7)

  1. PatriotB says:

    I cannot count how many times I’ve seen differing information about VS 2005’s x64 support. Specifically, does the Standard Edition support x64 development?

    Your blog entry, and the page you link to, indicate that it does not.  However I asked this question on a different web log months ago and was told that Standard DOES support x64.  (http://blogs.msdn.com/freik/archive/2005/11/02/488228.aspx)  The product info page (http://msdn.microsoft.com/vstudio/products/compare/default.aspx) has since been changed to say that Standard DOES support x64, so I assume that it actually does.

  2. JohnGalt says:

    You forgot the serious issues:

    1. VS.net 2005 code editor is about 5x slower on Windows XP Pro x64 than it is on Win XP Pro x86.

    2. VS.net 2005 edit and continue doesn’t work at all. Which considering how bad the support is natively, is no big deal.

    3. If you set your processor affinity to X86 instead of "Any CPU" on an X64 version of Windows XP, you’ll get GDI+ drawing issues (transparencies all screwed up, artifacting etc.) with Nvidia video cards (don’t know about others, but likely the same deal)  Hence if you need 32bit controls like TAPI, you’re screwed.

    4. If you set your Winforms project ot Any CPU so that it uses X64, forms will load the first time about 8-10x slower than they do when set to x86 or in .NET 1.1.

    Good luck to anyone that really wants to use this configuration right now… it’s a mess and if you thought VS.net 2005 was buggy under Windows XP Pro 32… wait until you see it under X64! It’s way worse. (and that’s saying something considering how bad it is under x86!

  3. If you ever had doubts about running  your .NET 2.0 application on ITANIUM 64-bit platforms you can rest…

  4. fractalnavel says:

    deeptanshuv’s WebLog : 64-bit and Visual Studio 2005 (tags: windows visualstudio 64-bit ) Gini coefficient