Build Version Increment v2.4.11046.2045

Rating:        Based on 31 ratings
Reviewed:  30 reviews
Downloads: 25845
Change Set: 62392
Released: Feb 15, 2011
Updated: Feb 15, 2011 by yjagota
Dev status: Beta Help Icon


Application BuildVersionIncrement v2.4.11046.2045
application, 152K, uploaded Feb 15, 2011 - 25845 downloads

Release Notes


Fixes and/or Improvements:

  • Major:
    • Added complete support for VC projects including .vcxproj & .vcproj.
    • All padding issues fixed.
    • A project's assembly versions are only changed if the project has been modified.
  • Minor
    • Order of versioning style values is now according to their respective positions in the attributes i.e. Major, Minor, Build, Revision.
    • Fixed issue with global variable storage with some projects.
    • Fixed issue where if a project item's file does not exist, a exception is thrown.
    • Fixed a typo due to which the ProjectFilename was not set correctly in the IncrementorContext Constructor.

Reason for 3 changes in beta versions in span of two days
VCProjectEngine's versions are not backward compatible (which is by design). Every new Visual Studio comes with it's own VCProjectEngine.dll which is the same as VS's version i.e. VS2005 with v8, VS2008 with v9 and VS2010 with v10. If I build BuildVersionIncrement on my system using VS2010, and I reference VCProjectEngine.dll in my project, the resulting VSI will install successfully on any VS version but will only work if VS2010 is installed. This will happen (in this example) because the version of VCProjectEngine.dll referenced in BuildVersionIncrement.dll will be v10 which only comes with VS2010.

Due to this, the only solution was to build three separate dlls, referencing the specific version of VCProjectEngine.dll for the target Visual Studio version. I didn't wanted this. To solve the issue, the final solution I came up with was:
I have removed VCProjectEngine.dll reference and have instead used late binding (by using reflection) to get the required property of the VCProject i.e. PrimaryOutput which fixed the problem.

I apologize for the inconvenience. :)

Reviews for this release

Briiliant addin, with excellent configuration options. Now, if it would work with VS2013, I would give it 5 stars!
by jdlaw75 on Jan 8, 2016 at 7:15 PM
Good idea! But modify check not work for code behind aspx files. It increment version only when I modify in aspx file, but not when mdify in aspx.cs file. For simply projects it is ok. --- In version 2.5 works good.
by brzezinol on May 28, 2014 at 1:12 PM
Am I just being blind or after install did no "Build Version Increment Settings" option appear in the tool's menu? I am using VS2012, so maybe that's why?
by gbmhunter on Apr 30, 2013 at 10:33 PM
I got error 80131515 on load. fixed it!
by ThiloL on Apr 24, 2013 at 2:58 PM
To install, open Windows Explorer as Administrator, and then installed the .VSI.
by phearce on Oct 10, 2012 at 10:07 PM
I think I am the lucky one; it works great for me. Mine is C# solution in VS 2010 10.0.40219.1 SP1Rel. I like the fact that the author makes default actions to be false so I can setup one project at a time. I manually specified the assembly filename for each project, clear the build, and make sure all AssemblyVersion("x.x.*"). Thanks for making this tool.
by hoppyfrog on Jun 4, 2012 at 11:32 PM
This release did not work for me. I was able to install it without problems but when I compiled my master solution (125 projects) it threw errors.
by sedotakj on May 23, 2012 at 2:53 PM
Установить бета версию на VS2010, работает прекрасно! Одобряю!
by catterpiler on May 21, 2012 at 4:29 AM
I installed buil 2045 for VS2010 and it threw an error. 'BuildVersionIncrement' failed to load. Error number: 80131515. I have VS2010 with SP1 installed.
by ravinns on May 3, 2012 at 4:32 PM
Great addin!!
by savekiller on Apr 2, 2012 at 9:43 AM
I installed 2045, ran vs 2010, opened a solution, set an incremental build, and tried to build it, but it threw errors. I took out the incremental build and it continued to throw errors upon building. The error messages were no help so I found every instance of the files installed, removed them, and now my solution builds fine. Looks like 2045 needs work.
by kfishman on Feb 27, 2012 at 8:59 PM
I haven't used previous versions of this add-in, but this is a great add-in. I am very happy that it took a simple approach of limiting scope and focusing on quality. Thanks. Hopefully this will pressure MS to include something like this in the IDE instead of the date time stamp that is difficult to read, track, and maintain.
by ryanvgates on Dec 12, 2011 at 11:53 PM
Look nice, missing the revision of SVN at version.
by Vovaf on Nov 21, 2011 at 1:15 PM
I like the intent, but it doesn't seem to work with Silverlight Applications. Can anyone confirm that it does NOT work with Silverlight?
by abowne on Sep 15, 2011 at 1:17 PM
The feature that prevent assembly versions to be modified when the projet has not been modified is wonderful. Nice work!
by mystcreater on Sep 8, 2011 at 2:51 PM
BRAVO! Nice work, this really helps when your working with a dev team that spans multiple countries \ time zones.
by MMind on Aug 12, 2011 at 12:40 AM
Why this is not built into VS from MS is a total mystery to me. One issue. The increment sometimes does not update if the AssemblyInfo.vb file is not open and has been modified. Kind of a pain. Other then that this is a GREAT application, and should be a required part of ANY developers VS instalation. THANKS!!!
by LearnToday on Jul 19, 2011 at 5:45 PM
So far seems to be very good. Well done.
by Dangerous on Jul 17, 2011 at 5:58 AM
Very nice to use in my application.
by jrmcr9999 on Jul 14, 2011 at 10:08 PM
EXCELLENT!!!! As of 6/02/11 this version seems to work great with VisualStudio 2010 SP1. One thing that I had t do though was specify the location of my assemblyinfo file, even though it is in the default location. Once I did that, everything worked great! This is such a wonderful add-in! Visual Studio should have this kind of robust versioning support built in, but alas it does not. Thanks!
by JoshSommers on Jun 2, 2011 at 9:27 PM
With VS2010 don't work: error 80070057 (Wrong parameter value) at VS startup
by vmghost on May 27, 2011 at 7:58 AM
Tried this in VS2010 and it threw an exception at startup
by rupertdadey on May 26, 2011 at 10:42 AM
Unbelievably easy to use, flexible, and will make my life so much easier. I always forget to increment the version.
by Deadder on May 19, 2011 at 9:07 PM
This project makes incrementing my builds much easier. I hope it continues to be supported, but in any event after a few modifications it works like a charm exactly how I wanted. For those of you who this stopped working for after SP1, try the recompiled version care of Creadoo:
by Crucial on May 6, 2011 at 11:27 PM
It worked great before SP1. It's a great addon I really miss it now. Please update it to work with SP1.
by eric_w on May 4, 2011 at 11:47 AM
Excellent work, thanks for your hard work. Saves me so many time. :) ***************** ( 5 stars are not enough)
by Gordon2001 on Mar 18, 2011 at 2:23 PM
This is a great tool. ;). BTW, I have a suggestion: Could you please add a new versioning styles for DateTime with format string? Example: None.None.DateTime(YYYYMMDD).TimeStamp Then the result should be 1.0.20110317.1530. Anyway, thanks a lot for your hard word. Regards.
by nomercy on Mar 17, 2011 at 9:09 AM
It doesnt work. Only changes in xaml file is noticed for the incrementer to work. increment when rebuilt also doesnt work. In all, this add in is problematic and useless.
by publicENEMY on Mar 8, 2011 at 9:37 AM
I love your plugin but there's an error. It seems it cannot parse the project's date when verifies if it is changed. Maybe it's a problem only in non english systems like mine, and it's related to international settings. The DateTimeParse.Parse() method fails with the error "String was not recognized as a valid DateTime." at every build, as I see in addin's log...
by edibile on Mar 4, 2011 at 7:11 PM
Great tool.
by Shcherbachev on Feb 19, 2011 at 2:15 PM