Post-Build Step Always Forces Project Build

[matt_felzani]

We are noticing that for a Utility project that we have in VS.Net (C++)
that the Post-Build step is being performed every time that the IDE
finds the project as a dependency. While it does not take a long time
to do the step, it does have a ripple effect in that the output from
the Post-Build step is linked in another project and ultimately forces
that to rebuild as well ... the daisy-chain effect is a big problem
because the workspace contains north of 170 projects (I know, another
problem all together). This project has been converted from VS6.0 and
we did not have this issue in that IDE.

Anyway, any input would be appreciated. Thank you!

 

[Tarek Madkour [MSFT]]

(e-mail address removed) wrote in

We are noticing that for a Utility project that we have in
VS.Net (C++) that the Post-Build step is being performed every
time that the IDE finds the project as a dependency.

The behavior for utility projects was changed starting VS2002 to
make the build events fire all the time (regardless of the up-to-
date state of the custom build steps in the project).

To get the old behavior, you can associate your post-build step
action with a file in the project that is dependent on the outputs
of the other custom build steps the post-build step relied on.

Thanks,