Project dependency bug in .Net Studio?

  • Thread starter Thread starter Non Given
  • Start date Start date
N

Non Given

I discovered a strange bug(?) in a .Net Studio solution.

I have a solution with about 10 projects inside it. Many of these projects
reference other projects in the solution. So far, so good.

After making some changes, trying to track down a bug, I noticed that my
changes didn't seem to be making it into the application. I finally tracked
it down and noticed that if I added the project reference in Debug mode,
when I changed to Release mode, the Debug DLL version is still being used.
You can confirm this by looking at the path of the reference. It shows the
path to the Debug version, not the release version.

Am I doing something wrong here? I guess I could try to change the build
parameters so instead of a Release and Debug directory, the compilation
happens to a single directory, but that would be a pain.

Ideas?

Thanks
 
Did you set the references to the file directly? If so, remove these
references and select the project as a reference from the Projects tab in
the Add Reference dialog. This works correctly on my VS versions (2002,
2003, 2005beta).

Ron Allen
 
Back
Top