Hi,
There is no built-in support for configuration-based references, surely
because all configurations normally need the same references.
You could automate adding/removing references using a macro or add-in. Let
us know if you want to follow that route.
If you are only worried about the DLLs copied to the output folder, they can
be removed with a post-build action or macro.

Signature
Best regards,
Carlos J. Quintero
MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
>I am looking to be able to use the Visual Studio 2005 IDE to manage ALL
> of my configurations. It is easy to create custom configurations
[quoted text clipped - 21 lines]
>
> Thanks in advance.
martin.douglas@gmail.com - 25 Oct 2006 04:16 GMT
A macro approach would suffice. I need to get the entries out of the
project file in essence so that ClickOnce will not detect the DLL's as
dependencies and try to deploy them.
Thanks
Carlos J. Quintero [VB MVP] - 25 Oct 2006 12:15 GMT
See my article:
HOWTO: Getting information specific to VB.NET and C# projects from an add-in
or macro.
http://www.mztools.com/resources_vsnet_addins.htm
to learn how to access programatically the references of a project. You can
remove a reference with Reference.Remove and add them later with
References.AddXXX(...).

Signature
Best regards,
Carlos J. Quintero
MZ-Tools: Productivity add-ins for Visual Studio
You can code, design and document much faster:
http://www.mztools.com
>A macro approach would suffice. I need to get the entries out of the
> project file in essence so that ClickOnce will not detect the DLL's as
> dependencies and try to deploy them.
>
> Thanks