Having the command always runs defeats the purpose of a build. However, I don't know your environment or what you're trying to accomplish. What you'll want to do is set up a custom build step for the particular header you want to produce. The trick is to specify $(InputDir)nul in the Additional Dependencies field. The nul will always return a newer time later than the file so your command will always run.
Dig Deeper on Win Development Resources
Related Q&A from John Robbins
What is a JAD session? This term is referred to often in job postings and seems like some kind of brainstorm you carry out with a client to define IT... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.