4

I'm writing a C++ application in Microsoft Visual Studio and have added a VS_VERSION_INFO version table in the resource script so as to include version information (including a version number which is automatically increased at every build through a VS plugin).

I also need to include a manifest file and, as described in Application Manifests, the program's version needs to be included there as well. At the moment, I'm writing it (inside the assemblyIdentity string) into the project's property pages manually.

Is there a way to keep both version numbers automatically synchronized so that I won't have to check at each build (or, at least, at every release build) that they are in fact in sync?

Alessandro Menti
  • 1,290
  • 20
  • 28
  • But why do you need to do all that? – Ajay Feb 25 '12 at 11:08
  • @Ajay Maintaining both version numbers in sync is a recommended practice (see ), especially if someone is dealing with shared assemblies (that's not my case, but (1) I wanted to learn if there was a way to do it, for future reference, and (2) it's a matter of coherence). – Alessandro Menti Feb 25 '12 at 19:12
  • @Ajay The version number of an `assemblyIdentity` element within a `dependentAssembly` element must match the true version of the dependent assembly if that assembly is a managed component, I've found. And if that also happens to be a component built internally, the number needs to vary with every build. Therefore I too would like to know how to allow this to be variable. – BlueMonkMN Dec 07 '15 at 17:04

0 Answers0