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

[Ed Sutton]

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

[Alan Pretre]

"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

[Robert Jeppesen]

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

[Alan Pretre]

"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