Use the built in Settings classes, you just need to upgrade the settings anytime you change the application version. Here’s how to do it: In the Settings.settings file, create a new setting UpdateSettings type=bool Scope=User Value=True Include the following code before you use any Settings (it can run every time the app runs, as this … Read more
My strategy is to let your VCS tags do it for you (git shown here). Add this to your application.rb: # Only attempt update on local machine if Rails.env.development? # Update version file from latest git tag File.open(‘config/version’, ‘w’) do |file| file.write `git describe –tags –always` # or equivalent end end config.version = File.read(‘config/version’) You … Read more
I chose to just use the date of the executing assembly. The way I publish the files, this works fine. lblVersion.Text = String.Format(“Version: {0}<br>Dated: {1}”, System.Reflection.Assembly.GetExecutingAssembly().GetName().Version.ToString(), System.IO.File.GetLastWriteTime(System.Reflection.Assembly.GetExecutingAssembly().Location).ToShortDateString());
One simple way I did it previously is by reading the current version and increasing it by one, so you get the current version and increment by one using the command line. With that said, it is possible to do the following for the .net core project: In your .csproj file, you add the following: … Read more
I’ve getting through this same problem. My solution which is opinionated and may not respond to your criterias: When I package my front-app and my server-app, I share a configuration file containing the current version of the front-app. Front side: 75% of my routes change implicitly call a Webservice (route change resolve). SO each time … Read more
I’ve achieved the same results using the GAC in the past, but you should question your reasons for having to reference more than one version and try to avoid it if possible. If you must do it, a binding redirect may help in your case. Also, have you read this yet?
Subsequent versions of an assembly that differ only by build or revision numbers are considered to be Hotfix updates of the prior version. This section explains the difference. The Revision is used when your product has shipped and you need to make fixes to a shipped version while you are already progressing with updates. For … Read more
For normal releases, just do the snapshot version bump after merging the release branch: Create the release branch off develop and remove the snapshot from the version Merge it into master Merge it into develop Change the version on develop to the next snapshot version Push both master and develop As you push all the … Read more