64 bit configuration

[bob_jeffcoat]

Hi,
I'm trying to build my application for both 32 and 64 bit Windows but
my project references a non-managed Dll that comes in 2 formats, one
for 32 and one for 64. How do I set up my solution so that I can
build for both targets easily? Is it possible?

Also, are there any problems using 'unsafe' code if I'm trying to run
on x64?

Thanks,

[Willy Denoyette [MVP]]

<bo**********@h otmail.comwrote in message
news:34******** *************** ***********@e4g 2000hsg.googleg roups.com...

Hi,
I'm trying to build my application for both 32 and 64 bit Windows but
my project references a non-managed Dll that comes in 2 formats, one
for 32 and one for 64. How do I set up my solution so that I can
build for both targets easily? Is it possible?

Also, are there any problems using 'unsafe' code if I'm trying to run
on x64?

Thanks,

This program doesn't take advantage of 64-bit, so I would suggest you to
build a 32-bit version only, a 32-bit version will run on both 32 and 64 bit
Windows.

Willy.

[christery]

>

This program doesn't take advantage of 64-bit, so I would suggest you to
build a 32-bit version only, a 32-bit version will run on both 32 and 64 bit
Windows.

Willy.

But lagging if Im correctly informed, running MS SQL server 64 bit
version only came with 32 bit management so it was best to manage it
from anywhere but the server. Guessing it gets problems with memory
alignment just like Alpha/I64 running OpenVMS or is it emulating
32bit?

//CY

[Willy Denoyette [MVP]]

<ch*******@gmai l.comwrote in message
news:93******** *************** ***********@h11 g2000prf.google groups.com...

This program doesn't take advantage of 64-bit, so I would suggest you to
build a 32-bit version only, a 32-bit version will run on both 32 and 64
bit
Windows.

Willy.

But lagging if Im correctly informed, running MS SQL server 64 bit
version only came with 32 bit management so it was best to manage it
from anywhere but the server. Guessing it gets problems with memory
alignment just like Alpha/I64 running OpenVMS or is it emulating
32bit?

//CY

IA-64 and Alpha are "real" 64-bit processors, that is they can only run, a
single, 64-bit based instruction set.
The X86-64 kind architectures(A MD 64 and Intel 64) have two different modes
of operation, a native mode and an extended mode.
These processors can run native 32-bit (IA-32) code when initialized in
native mode, and 64-bit code (IA-32e)when initialized for long mode, the
"64-bit" instruction set is nothing more than an extension of the IA-32
instruction set (hence the IA-32e), and is completely different from the
IA64 instruction set. The great advantage of this architecture is that it
can run 32-bit X86 and "64-bit" user code while running a 64-bit (X64) based
OS, without the need for a 32-bit "emulator" like the IA64 and Alpha
architecture does.
All the (X64) OS has to do, is perform a switch from IA-32 mode to IA-32e
mode when a 32-bit user program transitions into the kernel, this switch
takes a hit of less than 100 cycles, which is < 0.2% of the time taken to
transition into kernel space.
The alignment requirements depend on the mode the processor actually
executes, no surprises here, 32-bit code must adhere to the IA-32
requirements, while IA-32e has the 64-bit requirements.
Willy.

[RobinS]

We have a case where we have a license file that changes based on the build
configuration. So if you're compiling in Debug mode, it needs one license
file; if you're compiling in Release mode, it needs a different one.

We handled this by setting up a folder called \license_debug and a folder
called \license_releas e in the project, and putting the appropriate license
in each folder.

Then with post-build commands, we use the right variables and copy the right
one into the main folder. This is why our folders are called debug and
release. Here's the post-build command:

COPY/Y "$(TargetDir)li cense_$(Configu rationName)\*.* " "$(TargetDi r)"

Presumably, you could do the same thing with DLLs.

RobinS.
GoldMail, Inc.
--------------------------------------
<bo**********@h otmail.comwrote in message
news:34******** *************** ***********@e4g 2000hsg.googleg roups.com...

Hi,
I'm trying to build my application for both 32 and 64 bit Windows but
my project references a non-managed Dll that comes in 2 formats, one
for 32 and one for 64. How do I set up my solution so that I can
build for both targets easily? Is it possible?

Also, are there any problems using 'unsafe' code if I'm trying to run
on x64?

Thanks,