Automatic application versioning that not only persits between builds, but also doesn't depend on the build number. Below is an example showing how this extension could be used.
Note: AutoAppVersion has been designed to work with Azure DevOps pipelines and DotNet Core projects.
Make sure your project file (.csproj or .vbproj) has a version element
Set your Version Mask Override in AAV
AAV will start to automatically increment the masked version number on each build.
Increase your app's minor version
AAV will detect the minor version has increased, and restart the masked incrementation from 0.
Increase your app's major version
AAV will detect the major version has increased, and restart the masked incrementation from 0.
AAV writes the new version number directly into your current build's project file allowing any following tasks to utilize the project version like normal. The new version is also saved to a variable defined in your build definition.
- You have options which can stop the build if AAV detects certain problems.
- You can tell AAV to set your project's FileVersion and AssemblyVersion based on the build's generated version number.
- You have the option to specify and set an environment variable with the latest version number which can be used by proceeding tasks in your build.
Need help setting up
Check out the wiki on getting started.
Minimum supported environments
- Minimum agent version: 2.123.0
All the version numbers
Check out the following scenario:
- Increment your app's current version.
- Apply new version number to FileVersion.
- Apply new version number to AssemblyVersion.
- Ensure .Net pack uses your new version number when generating new packages.
- Make sure all new bugs that are sent to Bugsnag include the new version number.
- Finally, notify Bugsnag of your latest release, and it's new version number.
If you find yourself in this scenario, click here to find out how my Azure DevOps extensions can be made to work together to automate this entire process.