Re: 64 bit configuration
- From: "RobinS" <robins@xxxxxxxxxxxxxxxx>
- Date: Fri, 8 Feb 2008 23:41:35 -0800
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_release 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)license_$(ConfigurationName)\*.*" "$(TargetDir)"
Presumably, you could do the same thing with DLLs.
RobinS.
GoldMail, Inc.
--------------------------------------
<bob_jeffcoat@xxxxxxxxxxx> wrote in message news:34d5e94c-e63e-4364-86bc-97a35d9832d5@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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,
.
- References:
- 64 bit configuration
- From: bob_jeffcoat
- 64 bit configuration
- Prev by Date: Re: access @@IDENTIY in LINQ?
- Next by Date: Re: Antialiasing
- Previous by thread: Re: 64 bit configuration
- Next by thread: Convert DateTime.Now() to SQL Server(tm) standard internal format for datetime
- Index(es):
Relevant Pages
|
