When compiling, are References from their latest build?

[Dean Slindee]

I have a project with many References to other projects of mine (data access
layer projects, for instance). When I compile a data access layer project,
the Reference in the parent project goes stale (yellow icon) when the parent
project is concurrently open (two VS instances).

I have been manually deleting the stale Reference and re-adding the
Reference in the concurrently open parent project.

Is this manual process necessary, or will the stale reference be
automatically refreshed next time I compile the parent project?

Another similar question, when compiling the parent project, are all
"non-stale" references automatically refreshed from the reference file path
during the compilation of the parent project?

Thanks,
Dean S

 

[\(O\)enone]

I have a project with many References to other projects of mine (data
access layer projects, for instance). When I compile a data access
layer project, the Reference in the parent project goes stale (yellow
icon) when the parent project is concurrently open (two VS instances).

Just out of interest, what do you have the AssemblyVersion value set to for
your project?

Do you have it set to a fixed values (e.g., "1.0.0.0") or is it set to be
auto-generated (e.g., "1.0.*")?

 

[Family Tree Mike]

I have a project with many References to other projects of mine (data access
layer projects, for instance). When I compile a data access layer project,
the Reference in the parent project goes stale (yellow icon) when the parent
project is concurrently open (two VS instances).

I have been manually deleting the stale Reference and re-adding the
Reference in the concurrently open parent project.

Is this manual process necessary, or will the stale reference be
automatically refreshed next time I compile the parent project?

Another similar question, when compiling the parent project, are all
"non-stale" references automatically refreshed from the reference file path
during the compilation of the parent project?

Thanks,
Dean S

Is there a reason you don't have both projects in one solution? This would
be taken care of by the solution dependencies by setting it up as such.

 

[Dean Slindee]

Here is a link to an MSDN article relating to my question indirectly (list
item #8). Since the context menus no longer appear in VS2005, I presume
that VS is handling my question automatically. To answer your question, I
have 34 interrelated projects in a heirarchy about 5 deep. I used to have
the projects all together early on, but using references instead cleaned up
that mess.

 

[Dean Slindee]

Automatically updating version number. Turns out my problem was due to a
inappropriate login name parameter as setup by our dba. Once I pointed the
problem out to him, the problem was resolved (as in not in my code).