Just a note - I was working with version 3.8.0.0 of CSLA.dll, a previous alpha/beta? version and picked up the latest beta with the PropertyStatus changes etc which was also CSLA.dll version 3.8.0.0.
This caught me out with my deployment msi as it did not replace the older file with the new one.
Any reason why the versioning is hard-coded or would it be better to have VS auto-increment the last two parts of the number? i.e. 3.8.3589.17596.
I specifically use the x.y.z parts of the number. The fourth part could be auto-incremented.
But remember that I provide you with source, not binaries. So the auto-number would be unique to you. That's probably fine for the fourth part, but not for the x.y.z because they have very clear universal meaning to identify the specific release version of the framework.
Copyright (c) Marimer LLC