J
John Lafrowda
Hi all,
I'm trying to handle two projects in one solution (.net 2002, both projects
are VB). The first project contains only some public constant definitions
(for the moment) and compiles into class libarary. The second one is builds
an executable which has a reference to the assembly of the first project to
retrieve global constant definitions. The whole thing works fine as long as
no definitions are changed in the library project.
In case definitions are changed in the library project, I would expect that
the executable project integrates these changes as it is set to be dependent
on the library project and hence always built as a second step. In reality,
however, the build operation of the executable project does not recognise
changes in the library. At this time, I found only three unsatisfying ways
to force an update of the reference:
a) Remove the reference to the library and re-add the reference.
b) Switch the current state of the "Copy Local" switch of the executable to
the other option: If it is currently set to "True", a modification towards
"False" will update the reference - the same is true when changing from
"False" to "True".
c) Shut down the .net environment and restart it - the reference will be ok
then.
Now, what I'm looking for is a way to automatically update the dependencies
in a solution build process, i.e. references of the second project to the
first one should be updated (at least) when I try to build the second
project. Az the moment it seems to rely on a (local?) assembly cache as long
as do not update the reference manually as described above.
Any ideas?
Best regards,
John
I'm trying to handle two projects in one solution (.net 2002, both projects
are VB). The first project contains only some public constant definitions
(for the moment) and compiles into class libarary. The second one is builds
an executable which has a reference to the assembly of the first project to
retrieve global constant definitions. The whole thing works fine as long as
no definitions are changed in the library project.
In case definitions are changed in the library project, I would expect that
the executable project integrates these changes as it is set to be dependent
on the library project and hence always built as a second step. In reality,
however, the build operation of the executable project does not recognise
changes in the library. At this time, I found only three unsatisfying ways
to force an update of the reference:
a) Remove the reference to the library and re-add the reference.
b) Switch the current state of the "Copy Local" switch of the executable to
the other option: If it is currently set to "True", a modification towards
"False" will update the reference - the same is true when changing from
"False" to "True".
c) Shut down the .net environment and restart it - the reference will be ok
then.
Now, what I'm looking for is a way to automatically update the dependencies
in a solution build process, i.e. references of the second project to the
first one should be updated (at least) when I try to build the second
project. Az the moment it seems to rely on a (local?) assembly cache as long
as do not update the reference manually as described above.
Any ideas?
Best regards,
John