Single Solution to target 64 bit and 32 bit versions?

[Fritz]

I have a single solution to handle both 32bit and 64bit versions of
the application. However, I am trying to determine how to manage the
setup project. Should I have two seperate setup projects one for 32bit
and one for 64bit or is there a way to create just one? I am leaning
towards the two seperate setup projects, but just wanted to be sure
this is the correct approach. Thanks

 

[Joe Cool]

I have a single solution to handle both 32bit and 64bit versions of
the application. However, I am trying to determine how to manage the
setup project. Should I have two seperate setup projects one for 32bit
and one for 64bit or is there a way to create just one? I am leaning
towards the two seperate setup projects, but just wanted to be sure
this is the correct approach. Thanks

Question: how do you handle both x86 ans x64 in a single solution? Set
the Build Platform target to "Any CPU"?

Does your app actually make use of specific x64 features for the x64
version? If not, why not just make a single version with Platform
target as x86 which should run OK on both x86 and x64?

 

[Fritz]

how do you handle both x86 ans x64 in a single solution? Set

the Build Platform target to "Any CPU"?

I create my two "Solution Platforms" one for x86 and one for x64 and
change the "Platfom" for each project as needed. I do leave most .NET
projects to "Any CPU" except for the EXEs and the C++ projects.

Does your app actually make use of specific x64 features for the x64
version? If not, why not just make a single version with Platform
target as x86 which should run OK on both x86 and x64?

Yes, our application links to native 64 bit dlls using P/Invoke.

 

[Family Tree Mike]

I create my two "Solution Platforms" one for x86 and one for x64 and
change the "Platfom" for each project as needed. I do leave most .NET
projects to "Any CPU" except for the EXEs and the C++ projects.


Yes, our application links to native 64 bit dlls using P/Invoke.

Some people don't like following Microsofts lead, but they seem to go
with selecting either an x86 or x64 install for their apps. I would go
that route, keeping the installer separate.

If both installers fit on one dvd, you could separate them within
folders, and have a simple intro app that guides them to the appropriate
installer.