When you used Browse to add the reference, you (probably) chose the Debug
location. Therefore, your project knows only about those files. It does not
know that there is a Release version available.
We do something like this for some common utility assemblies that are shared
across a number of solutions.
Our solution to this was to modify the project for those assemblies you wish
to include to copy the output to the PublicAssemblies directory under the
Visual Studio 8 (C:\Program Files\Microsoft Visual Studio
8\Common7\IDE\PublicAssemblies on my system). From that location,
solutions can establish references using the normal .NET tab of the add
reference dialog.
This allows you to choose which assemblies to link to by building the proper
version (or just copying them) when you want to change.
"Hugh" <Hu**@discussions.microsoft.comwrote in message
news:1A**********************************@microsof t.com...
Hi there
We are trying to build a C sharp solution in Visual Studio 2005
Professional.
We have a number of other assemblies, that do not form part of the
solution.
Assemblies that do form part of the solution have been referenced using
the
Projects tab in the Add Reference dialog.
Assemblies that do not form part of the solution have been added usingthe
Browse tab.
The problem is that when we do a Release build, it still references the
Debug build assemblies of the non solution projects, rather than the
release
assemblies.
Is there any way of forcing the references to use Debug/Release assemblies
for the "browsed" assemblies as appropriate?
Thanks in advance
Hugh