Each build project or solution, increase selected project assembly and file version +1.
Or simple version++
vs 2015 support
project state saved registry
add menu item : Get All Project Status from Registry
enabled c# web applications
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.
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 ?
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!
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.
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!