468,242 Members | 1,710 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,242 developers. It's quick & easy.

How make Release build use references to Release components & visa versa?

My solution contains multiple C# and C++ components as well as a deployment
project.

In my top-level C# WinForms application, I added references to some
components by browsing to the \bin\debug\*.dll of the desired component.
How can I make it use a debug build of a component for a debug build, and a
release build of a component for a release build?

Thanks in advance for any tips or direction,

-Ed
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.520 / Virus Database: 318 - Release Date: 9/19/2003
Nov 15 '05 #1
3 1338
"Ed Sutton" <no****************@nomadics.com> wrote in message
news:uL*************@TK2MSFTNGP10.phx.gbl...
In my top-level C# WinForms application, I added references to some
components by browsing to the \bin\debug\*.dll of the desired component.
How can I make it use a debug build of a component for a debug build, and a release build of a component for a release build?


We created a build tool that sets the references on the fly based on whether
it's debug or release. It's too bad VS doesn't allow you to separate them
out in the project.

-- Alan
Nov 15 '05 #2
Doesn't VS do this itself if you set a reference to a project instead of a dll?

--
Robert Jeppesen
robert.jeppesen%at%durius-dot-se
"Alan Pretre" <no@spam> wrote in message news:Og**************@TK2MSFTNGP12.phx.gbl...
"Ed Sutton" <no****************@nomadics.com> wrote in message
news:uL*************@TK2MSFTNGP10.phx.gbl...
In my top-level C# WinForms application, I added references to some
components by browsing to the \bin\debug\*.dll of the desired component.
How can I make it use a debug build of a component for a debug build, and

a
release build of a component for a release build?


We created a build tool that sets the references on the fly based on whether
it's debug or release. It's too bad VS doesn't allow you to separate them
out in the project.

-- Alan

Nov 15 '05 #3
"Robert Jeppesen" <robert.jeppesen(#)durius.se> wrote in message
news:Ox**************@tk2msftngp13.phx.gbl...
Doesn't VS do this itself if you set a reference to a project instead of a

dll?

Project references are OK. The problem will come with references to foreign
assemblies (those not built in your solution).

-- Alan
Nov 15 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

15 posts views Thread by Web Developer | last post: by
4 posts views Thread by pnp | last post: by
7 posts views Thread by Srinivasa Rao | last post: by
6 posts views Thread by Andrew Rowley | last post: by
4 posts views Thread by fniles | last post: by
6 posts views Thread by =?Utf-8?B?SHVnaA==?= | last post: by
3 posts views Thread by =?Utf-8?B?bG10dGFn?= | last post: by
reply views Thread by kermitthefrogpy | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.