Auto Version Incrementer


Each build project or solution, increase selected project assembly and file version +1. Or simple version++ v1.5 -- vs 2015 support v1.4 -- project state saved registry add menu item : Get All Project Status from Registry enabled c# web applications v1.0.0.3 -- each projec...

(8) Review
Visual Studio
2015, 2013, 2012
Download (5,344)
E-mail Twitter Digg Facebook
Add to favorites
Reviews (8)
Q and A (11)
Sign in to write a review
Sort by:

by NormD | September 16 2015

Please ignore - my test was with PrecisionInfinity.AutomaticVersions.vsix

Can anyone help. The tool installed OK and "Automatic Version Settings" shows on my Tools menu.
But, no versions change after a clean build.
No menu entries for "Enable Version Incrementor" or "Manual Version++"
solution explorer does include a section for "GlobalSection(AutomaticVersions) = postSolution.

If this can be fixed, I will significantly raise my rating.


by blugnier | September 12 2015

Not working with this config :
- Windows 10
- VS 2013 Ultimate Update 5
- Universal apps project

It doesn't auto increment. Only manual incrementation working

too bad

by PeterFnet | September 11 2015

Works great! Simple and easy to use. I opted to use this plugin instead of [assembly: AssemblyVersion("1.0.*")]. The asterisk method does not save the final assembly version anywhere other than the build output. This makes it difficult to track revisions in source control.

With Auto Version Incrementer, it modifies the actual version in source files. Now, when another user of my applications say they have a problem with version, I know exactly what build it is.

by Artem Gorbatuk | July 30 2015

Hello, I used it in VS2013. It was very nice tool, but it's not working in VS2015 right now.

by wtjones | May 02 2014

This is great. It even updates the info in the file details, unlike using something like "0.0.*"

The only issue is that it must be enabled every time you launch visual studio.

by Kay Haefker | March 17 2014

Works perfectly on VS 2012 Premium.
I just missing the increment on a rebuild too.

by -PaulB- | March 04 2014

Nice little tool, works very well. Has saved me a lot of time doing busy-work. Cheers!

by Boris Gligich | December 30 2013

Sign in to start a discussion

  • v1.5 - Stopped working on 2013
    3 Posts | Last post September 01, 2015
    • Installed the new version 1.5...It no longer works on VS 2013...The main reason for installing the new version, I had to re-enable every time I started VS. Is there a fix or a workaround for this issue? Thanks. 
    • ok, fixed.
    • It's now working in 2013...Thanks.
  • it's not working in VS2015 right now.
    3 Posts | Last post September 01, 2015
    • will you fix this extension for Visual Studio 2015?
    • its now working VS2015.
    • Huge thanks!!!
  • Auto Version and MSBUILD
    2 Posts | Last post April 07, 2015
    • Hi I wanted to know if this work with Msbuild commands as well.
      I am using Visual Studio 2013 professional edition.
      If I build the solution after enabling the auto version increment property from my solution explorer it asks to modify the source code and builds the stuff. Thus, this generates the new exe with a new version.
      I tried to build the solution with msbuild command but it never changed the version number.
      wondering if I need to specify the auto increment property in msbuild command as well. If yes HOW ?
    • Hi, thx for download and using this extension.
      This extension works on VS events (i think its not hook all MsBuild event)
      I dont explore Msbuild event as well.
  • English Spelling
    2 Posts | Last post February 21, 2015
    • Just a quick observation, the English phrase should be:
      "Manual Version++"
      "Manuel Version++"
    • Agreed. This looks pretty silly.
  • Can AssemblyVersion be prevented from updating?
    1 Posts | Last post January 28, 2015
    • Can AssemblyVersion be prevented from updating? If a class library changes this number, then any project depending on it cannot use it anymore unless it is recompiled. So there has got to be a way to exclude this number from changing. Typically you only update the AssemblyFileVersion and never update the AssemblyVersion unless there is a major release change. If I went changing this number around every time I did a build, a lot of people would be mad at me. Could an option be added to opt whether or not to also change this number? Thanks!
  • for exe file; change file name also?
    1 Posts | Last post December 09, 2014
    • for exe file; change file name also?
  • increase AssemblyInformationalVersion as well
    1 Posts | Last post September 19, 2014
    • Hi, awesome tool. But it would be fantastic if you could increase the number on the AssemblyInformationalVersion as well.
  • Manual increment exception
    5 Posts | Last post August 06, 2014
    • Hi
      When I try to manual increment versions on some of my projects in VS2013 I receive exception
      "Length cannot be less than zero.
      Parameter name length"
      What can be an issue ?
    • I forgot to add, that AssemblyInfo files for working and not working projects are identical
    • hmmm. I'll check as soon as possible.
    • I figured out what is the problem.
      This exception happen when there was no empty line at the end of AssemblyInfo.cs. In my case the last line was AssemblyFileVersion. By adding enter everything worked fine.
      Another issue that I found is an exception which is thrown when only one of AssemblyVersion/AssemblyFileVersion entries is provided in file.
      Your extension is really cool and I will be really grateful for providing an update.
    • solved new version.
  • Solution Re-Opening
    6 Posts | Last post August 06, 2014
    • When you close the solution and re-open, the auto-numbering feature switches off, I then need to right-click each project to switch it back on again.
      Is this correct behaviour or is this a bug?
    • I was not sure so I did it that way
    • Could this be changed to save the setting? I just noticed this problem today and had to re-enable in all my projects.
    • Your extension is great but it would be very useful if you will add option to automatic re-enable in all projects in solution.
    • It would be very helpful if the enable auto increment option would persist when the project is re-opened in Visual Studio.  It would also be very helpful to have a global option that would turn it on for all current and future VS projects.  For #2, there would also need to be a global disable option as well.   This is very helpful, thank you for what you do!
    • this discussion solved new version.
  • VS2013 Visual Basic and Auto Version Incrementer
    2 Posts | Last post February 06, 2014
    • Hi,
      Why does it not work with Visual Basic projects/solutions?
    • actually i have no time
1 - 10 of 11 Items