Solution problem : Project *always* out of date

[Sin]

I have a solution in which I have 4 projects.

P1 is a EXE project (dependencies : P2 and P4)
P2 is a DLL project (dependencies : P4)
P3 is a DLL project (dependencies : P2)
P4 is a DLL project (dependencies : None)

All of these projects are plain unmanaged win32, no COM, no ATL, no MFC,
etc.

For some reason, even though I've just rebuild ALL of these projects using a
Batch build or Solution rebuild, P4 is ALWAYS out of date when I start
debugging P1. If I answer yes to rebuild it, it only links P4 and proceeds
to debug P1...

It does it in debug AND release and I've cleaned both associated folders by
hand to insure nothing was left in there. Problem is still there.

Any ideas?

BTW: P3 is not used by any of the other projects. P3 is a DLL written for a
VB6 application which obviously isn't part of the solution. P1 connects to
the VB6 project through TCP.

Thanks,

--
Alex.

[martinc]

I am experiencing something similar. I have a MFC based
project that is permanently out of date even immediately
after it has just been rebuilt.

I have traced the cause to the resource .rc file. In the
BuildLog.htm there is an error message that is not shown
in the IDE debug output window (bug?):-

"Commands : warning PRJ0041 : Cannot find missing
dependency 'std\std.h' for file 'Commands.rc'. Your
project may still build, but may continue to appear out of
date until this file is found."

The .rc file does include the 'std\std.h' header file (via
the 'Resource Includes...' dialog) which is defined in the
parallel project 'std'. The VC++ include path is set up to
contain ".." to pickup such header files and the project
builds perfectly OK including the resources using the RC
resource compiler. The problem seems to be that the IDE's
dependency checking is not using the VC++ include path
when looking for the headers included in the .rc file.
Unfortunately I haven't found a workaround yet. If anyone
else has any ideas I'd be pleased to know

regards,
martinc.