We have a project in which it was necessary to add versioning. The project has already configured TeamCity build server. Having read the manuals on the Internet, I didn’t quite understand how to correctly connect the versioning of Visual Studio libraries with the versioning of TeamCity assemblies. Can anyone tell me how to organize the easiest versioning method that satisfies the following requests: 1) The version of the library that we did not change did not change during builds and builds in timicity. 2) It was easy to compare - what versions of libraries within a particular assembly are. 3) it is not entirely clear whether the version of the timiti assembly should be the same as the largest version of the visual studio libraries.

  • one
    1) No one should be wondering what version of the build in Visual Studio is there for the programmer 2) Version numbers should be set up only by the build server, and it increases the build number for each build. With the release of a new major version, the version number is manually increased by the server-timim build. - tym32167
  • I need a version to be shown in the .dll properties and I could determine the functionality that is present (or missing) in the current version. Plus, this version should match the version of the sprint in Redmine. If you increase the major version in TimCity, will it in the properties of the .dll also change the version? - Titov SP
  • You should have one source of the version for the assembly - I suggested to you that you should make a source of timicity. In timiti, you can customize the step, where it will patch the assembly and put there the version that is specified in timiti. So, if you change the version in timic and your build configurations are set up correctly, all new builds will be released with the new version. - tym32167
  • Regarding Redmine - it has no relation to the build process, because there you plan and set the numbers of your sprints / versions manually - tym32167
  • Well, and if you make the source of the TimCity version, then in the project to me in AssemblyInfo, just do it anyway what to write? Will it be ignored? - Titov SP

0