S
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,
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,