Browse by Tags
Sorry, but there are no more tags available to filter with.
-
-
Here is how I manage them… Major and minor version should be driven by Product Management Team, incremented on the base of feature sets. The revisions are driven by the development team, and should be increased every time you release a version. The builds...
-
-
The default behavior of Visual Studio is to increment you build number based on the pattern in assemblyinfo file. A project on Microsoft Code is build exactly for that purpose. -f.
-
-
When you want to digitally sign your application using a Strong Name, it is the combination of the SNK, the Assembly name and the public key token that make it unique. So, you can sign all your assembly using the same SNK, and use a Company wide signature...
-
-
Did you know that you can simply get the version of the application by going to Application.ProductVersion… ? And you can also get the Assembly version by using reflection, assemblyobject .GetName().Version . -f.