This document describes the steps you need to do when you release a product based on DS.
- Determine the version of your release. If the release has any breaking changes (_in fileformat?) since the last release you should at least increment the minor number. So you could go from 1.1.0 to 1.2.0
- Update the version in AssemblyInfoTemplate.cs of the DeltaShell.Core project with the version determined in 1
- Determine the file version of your release. If there was any change in expected.hbm.xml (DeltaShell.Plugins.Data.NHibernate.IntegrationTests) since the last release the version should be incremented
- Use the file-version to update the ProjectFileVersion of NHibernateProjectRepository.cs
- If you want an msi that replaces your previous version (for a example a bugfix release) you should only change the product version msi name. Then you don't want to change the upgradecode GUID as this is the identifier to replace your previous version.
If you want to create a side-by-side version you should follow the whole instruction here. - Check in your changes with the message ("Release x.x.x") (x.x.x is the version of 1)
- Tag/Branch your release like "Release x.x.x"
- Have a beer
