Migrating to 64 bit -- issues

[gnsi]

I currently have a managed application (a wrapper around Windows installer
technology) which deploys
the application. Both use .Net 3.0. It also uses unmanaged bootstrapper to
ensure that .Net framework is
installed on the machine.

Now - I want to exploit the performance benefit of the 64bit in the
application. The target operating systems
for the product are Windows 2003 Server Sp1 and Windows 2008 Server.

Currently the installer and application I have support only 32 bit. And now
I want to migrate to the
64bit installer as well as 64bit application.

I have few questions here --

1) Do I need to have two separate installers?
2) Also, do I need to maintain two different codebases?
3) Can I use the AnyCPU option of the compiler to make the binaries usable
in both - 32 as well as 64 bit?
4) What if the managed code I have interacts with unmanaged code - would it
be possible to use the AnyCPU
option in that case?
5) I have searched a lot and have got few bits on this but they are not
clear enough.
For managed code analysis I can use FxCop tool, but is there any tool
which would help me analyse the
unmanaged code (it is written in C++) for portability?

6) Will there be any issues while interacting with other applications like
SQL server?

7) What remoting issues I need to sort out if the application is distributed?

8) What about the class libraries such as Microsoft.Win32?

I would appreciate any help.

 

[AlEdlund]

Assuming you're in the correct forum, Visio (and office products in general)
are 32bit applications and the allcpu model will fail.
al