Trying to understand how version releases work on GitHub. In particular the DotSpatial library https://github.com/DotSpatial/DotSpatial.

If I download the master branch and compile it, the results are the DLLs are all at version

However if I just want the compiled DLLs that are ready for use I can click on the link https://ci.appveyor.com/api/projects/mogikanin/dotspatial/artifacts/Source/bin/Release.zip?branch=master This contains the DLLs with version

How do the versions work on GitHub?

  • The last number is often the build number. If it is not built, it is ok to have it set to 0. Note that it has nothing to do with Github but with the development environment (manual setting, increasing number, number derived from the current date-time etc) – JGH May 6 '18 at 21:13
  • So who and how does appveyor control the build number? In the code itself I don't see the Assembly information set, so it must be done through a config file of some sort.There are about 94 DLLs as a result of the compilation. – sinDizzy May 6 '18 at 23:20
  • I think its the file AssemblyInfoShared.cs. It has [assembly: AssemblyVersion("2.0")] [assembly: AssemblyFileVersion("2.0")]. Seems to me If I changed it to 2.0.0.* I would then get a dynamic build. – sinDizzy May 6 '18 at 23:56
  • yes, but not necessarily. There are some tools/plugins to set any part of the version number "on the fly" without relying on the star notation – JGH May 7 '18 at 0:55

I ended up modifying the file AssemblyInfoShared.cs to a version number that was one digit above the current release.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.