Updating version number at compile time
For example, software compiled to run on Free BSD 10.1 will still run on Free BSD 10-STABLE compiled later.STABLE branches occasionally have bugs or incompatibilities which might affect users, although these are typically fixed quickly. Processors vary, as do the build systems used with different versions of Free BSD, so testing is the only sure method to tell how a different number of jobs affects the build speed.Line 6 shows the file name we’ll be building: property to “temp” at the same time.
When I try that, I get a second installation instead of an update.
The reason is simple: The Msi-Installer only looks at the first three positions in the version number (see documentation) thus ignoring any changes in the build number.
Example: You define your assembly version as "1.2.3.*" - your setup receives version "220.127.116.111".
There are a number of plug-ins for Visual Studio that allow you to set auto-increment rules for assembly version numbers (I like this one), so we won’t start there. In this picture, I’ve got a Visual Studio plug-in incrementing the Version numbers automatically, every time I build the project. Firstly, you need to replace your hard-coded (which we set in the Add-In project’s properties).
Let’s look at how to get the build number from our Add-In project to our Wi X-output installer file. You can change these numbers manually if you don’t want to use an automated tool. That takes care of the version number that shows up in the Windows Home Server Console.