Static revision number

[matkoch]

Is it possible to have a static revision number (apart from assemblying it myself) ?

Background is, that I'm compiling a plugin against a certain product which has a version itself. For convenience, I would like to include that version number (without dots) into my revision number.

[JakeGinnivan]

Can you give an example? Just to be clear what you mean about a revision number. Also how does it fit into pre-release tags etc?

[matkoch]

This ReSharper plugin is a good example.

There are several versions of ReSharper that I want to support. Mostly the current latest major versions (2016.1, 2016.2, 2016.3, 2017.1). The codebase of the plugin is basically the same for all different ReSharper versions (except small #ifdef workarounds). And in order to identify for which version the plugin was built, I would like to put the Major.Minor version into the revision number. The rest would be as usual.

[jbaehr]

Our proposal to support of env-vars in format strings (see pull request #1385) could also address this issue. Currently format strings are only supported for the informational version and (with #1385) for the assembly file version. However, allowing them for the assembly version, too, should be easy.

[asbjornu]

Support for using environment variables was introduced with the env: prefix in #1385. Closing.