4

So do we need to increment the build number when the source code changes? No, you need to increment it when you build the application. Build numbers increment per build. That's why it's called a build number. Generally speaking, builds refer to compilations done by a dedicated build agent, and it does not include any local compilation a developer may do on ...


4

In a typical setup, build numbers are used when you have a central server that builds your software (often as part of a Continuous Integration pipeline). Those builds are then done periodically and/or when a change in the repository is detected. In such a setup, the build number is provided by the build server and will increase for each build that the server ...


3

the language considers String from "string 1.0" a different type from String from "string 1.1" Well, you found a major flow in the language you're designing. Types should be identified by their namespace. As soon as the namespace is kept unchanged between versions, a consumer would use string.String independently if the type is actually ...


1

If the business requires that you store an additional field/column of data, then there are essentially three possibilities: You modify the code to require the new field but don't touch the old data. This effectively renders the existing data inaccessible which is not likely to be accepted by the business. You write the reading code such that it can handle ...


Only top voted, non community-wiki answers of a minimum length are eligible