Windows Integrity Application Development Environments

DDK on either the development machine (x86/x64) or the target machine (IA64). You can debug on

the IA64 machine using the free WinDbg. This option is only as expensive as the IDE you buy.

Or, you could code, compile, and debug from the command line on IA64 without spending a cent on

development tools.

The rest of this paper describes each development tool in detail.

Microsoft VisualStudio

VisualStudio is Microsoft’s flagship software development environment. VS2005 now supports

building on all architectures from within the IDE. There are two major variants of this product.

VisualStudio 2005 Team System

You can use the VisualStudio 2005 Team System to build for the IA64 target. VS2005 Team System

runs on x86 and x64, but not on IA64. It does not run in emulation mode.

This product line includes:

• Team Edition for Software Architects

• Team Edition for Software developers

• Team Edition for Software testers

• Team Suite (which includes the broadest set of tools)

Each product is bundled with an MSDN subscription.

Visual Studio 2005 Standard and Professional

Visual Studio Standard and Visual Studio Professional do not include the IA64 compiler and you

cannot use them to build an IA64 target. These editions make for a good editor and a sanity

compilation test.

Visual Studio v6, v7 (.net or VS2003)

These older Visual Studio packages do not offer official IA64 support. There is a way to integrate an

external compiler and invoke it from within the VisualStudio IDE, but we do not recommend this for

anything other than the Intel compiler.

The only safe way of using Visual Studio 6 is by taking advantage of its Makefile export feature. You

can then use this Makefile in a separate SDK environment. This might be a good option for existing

VS6 projects.

Advantages:

 Create Makefiles from Visual Studio 6 projects

Disadvantages:

 No IA64 support except with Intel C++ compiler