references of the second project to theįirst one should be updated (at least) when I try to build the second Now, what I'm looking for is a way to automatically update the dependencies net environment and restart it - the reference will be ok 'False' will update the reference - the same is true when changing fromĬ) Shut down the. The other option: If it is currently set to 'True', a modification towards At this time, I found only three unsatisfying waysĪ) Remove the reference to the library and re-add the reference.ī) Switch the current state of the 'Copy Local' switch of the executable to
However, the build operation of the executable project does not recogniseĬhanges in the library. On the library project and hence always built as a second step. The executable project integrates these changes as it is set to be dependent In case definitions are changed in the library project, I would expect that No definitions are changed in the library project. The second one is buildsĪn executable which has a reference to the assembly of the first project to (for the moment) and compiles into class libarary. The first project contains only some public constant definitions I'm trying to handle two projects in one solution (.net 2002, both projectsĪre VB).
