So, you want to build yourself the binaries or want to fix a bug.
To enhance or fix bugs, please read Source code page to introduce yourself to the code. In Local build, we describe the build process: a mandatory read. Useful tips are contained in Debugging and Troubleshooting pages.
TFS Server API changed frequently in the past: TFS Aggregator contains specific checks for the TFS version. These check can be: - source code conditional compile - WiX sources - MSBuild project files So, caveat emptor: TFS versions are scattered all-over the places.
Note that to rebuild, edit or debug the code you must use Visual Studio 2015, Community or Professional Edition at a minimum (see Local build for details). TFS is not required locally: you can use Remote Debugging.
The CI build page explains some important things of our CI build infrastructure in VSTS.
| Branch | Artifacts | Purpose |
|---|---|---|
| master | Yes | Released code, versions are tagged |
| hotfix/* | Yes | Fast release cycle for bug fixes, branches from tag, merged to master after Issuer confirms fix is working |
| release/* | Yes | Release candidates, branch named after soon-to-be-relased version, tags mark interim releases |
| develop | No | Integration branch for developers |
| feature/* | No | New feature, idea |
Wiki master branch content must match the latest release. To prepare documentation for a future release, use a branch as in the code repository.
release/v# branchrelease/v# branch to master (use PR when possible)release/v# branch to master and delete itmaster branch to developdevelop branch and push