| Gerhard Menzl 2005-02-11, 8:59 am |
| I have a solution consisting of two C++ .NET application projects, two
C++ .NET DLLs, and one C# DLL. Two DLLs are referenced by both
applications, and one DLL is referenced by one application only.
Now I have observed that in the course of a release build, release
versions of the DLLs get built first as expected, but subsequently (when
the applications are built) get overwritten with their debug versions!
The build trace actually shows the commands that copy the DLLs from the
debug output directory to the release output directory.
A similar confusion exists with the /FU compiler option, but this time
it's the other way round: the debug version of the project properties
contains release paths. I have tried to correct this by changing the
input file paths on the property pages for the respective references,
but alas, the paths are non-editable.
Has anyone ever experienced similar problems? Does anyone know how to
resolve this in this IDE maze? It used to be so easy with makefiles ...
--
Gerhard Menzl
Humans may reply by replacing the thermal post part of my e-mail address
with "kapsch" and the top level domain part with "net".
|