We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now


Wait While Custom Build Tool Runs

Medium Priority
Last Modified: 2013-11-20
I run a custom build tool to date/version stamp my resources.  On most machines  (Win95 MSVC4.2) the build process waits for the tool to close before proceeding. On one, it does not wait.  On my machine, it waits in 4.2, but in recently installed DevStudio 5.0 it does not. The behavior is not specific to my tool.  Notepad behaves the same way.
Watch Question

Are you sure you didn't mix the custum build with the pre-link page?
Anyway, why not use the pre-link option?
Or, don't you want to version your files only if the build was succesful?  if yes, use the post biuld option!


Your answer was three questions. No I am not mixing the Custom Tab with the pre link page.  MSVC 4 didn't have a prelink page.  I am not stamping the executable, I am writing the VS_VERSION_INFO block of the resources.  I have access to all of the versioning info, and I don't have to worry about space allocation in the executable.  Fail or succeed, the stamp is the same.

Let me be more specific:
Since you mentioned that you HAVE passed to VC5.0 wich has the tab i mentioned ( and maybe because you aren't familur with VC5.0 because you've just recently switched from 4.2 ), i only suggested you check.

Any way, if it is important that you do your stuff after the bulid, the i suggest you use the post-build option of the VC5.0.

Mybe my English isn't clear enough, since i'm not an American.


I don't think my question was clear. In 4.x the build process stopped while my tool collected version information from the user.  This is the desired behavior. It worked on all but one machine.

We are testing development on 5.0.  5.0 does not wait on any of the tested machines.  This is not desired.  I AM NOT stamping the executable.  I am stamping the resource VS_VERION_INFO block.

An alternate solution for 5.x would be to run my tool as a pre link operation on the resources, and then add something to force the resource compiler to recompile prior to linking. If you can tell me how to trigger the resource compile so the linker sees the change I'll accept an answer.
Unlock this solution and get a sample of our free trial.
(No credit card required)


No it is not possible.  The problem is the build process does not wait for my tool to finish before proceeding.  The dependency check process does not see the updated date on the file after my tool closes.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.