Problem when rebuilding solution with several projects - not all references are updated...

[Amos]

My Solution has three different projects: GUI, Api, Match.
Project GUI includes a reference to Match.dll and Project Match includes a
reference to Api.dll . Project Api doesn't include any references.
Technically, GUI calls on classes/methods in Match, and Match calls on
classes/methods in Api. Api doesn't include user-defined references.

With Configuration Manager in "Release" (and all the projects in Release as
well), when I rebuild the whole solution (after modifying all three of them)
and look in the ..\GUI\bin\Release folder (GUI is the startup project), I
noticed that the only files updated were GUI.exe and Match.dll . Api.DLL
remains with the dame date so it doesn't include the last changes. The only
way I can update Api.dll is by deleting the reference to it in Match.dll and
adding it again with the updated dll.

Why aren't all the references updated when I do a full solution build? Will
I have to delete/add Api.dll manually everytime I update it? I assumed the
Dll's in the startup project path were updated.

Thanks.

Amos

 

[Scott English]

I take it you are using Visual Studio. Make sure that when you add
references to the other projects, you select the Project tab in the Add
Referenece window. This way, VS will build the projects in the correct
order. If you just reference the assembly and not the project, VS may not
build the projects in the correct order, that is, it may choose to build GUI
first (using the previously build assemblies) and then build the other
assemblies next.

Also, if that doesn't work, try selecting "Rebuild Solution" from the Build
menu. I think this causes a complete rebuild.