Build Version Increment Add-In Visual Studio

New Post: Not able to build the project with build number more than 65534.

Srikanthgowda — Mon, 20 May 2013 03:17:44 GMT

Hello,
I am trying to put the major version as '4', minor version as '2', Build number in the format of 'MMDDD' and revision as auto increment number which starts from '1'

But in this case i am facing the problem with Build number, MMDDD format returns the year and day name(sun,mon...) and while conversion into integer it is giving error.
I have tried with 'yymmdd' format and for current date it is greater than 65534 and hence it is also giving error. Donno how to proceed with this??? Any format which supports 'YYWeeknumberoftheyear' which will be very much helpfull i believe ....

Thanks in advance.

New Comment on "Documentation"

Srikanthgowda — Mon, 20 May 2013 03:16:43 GMT

Hello, I am trying to put the major version as '4', minor version as '2', Build number in the format of 'MMDDD' and revision as auto increment number which starts from '1' But in this case i am facing the problem with Build number, MMDDD format returns the year and day name(sun,mon...) and while conversion into integer it is giving error. I have tried with 'yymmdd' format and for current date it is greater than 65534 and hence it is also giving error. Donno how to proceed with this??? Any format which supports 'YYWeeknumberoftheyear' which will be very much helpfull i believe .... Thanks in advance.

Reviewed: Build Version Increment v2.4.11046.2045 (Apr 30, 2013)

gbmhunter — Tue, 30 Apr 2013 21:33:47 GMT

Rated 3 Stars (out of 5) - 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?

Commented Issue: [Warning] Cannot parse current item's date '1/1/0001 12:00:00 AM' [7533]

frazou — Fri, 26 Apr 2013 15:15:46 GMT

Hi

Get a lot of warning

[Warning] Cannot parse current item's date '1/1/0001 12:00:00 AM'

And nothing is incremented in VS 2011 SP1.

I'm using the latest beta.
Comments: ** Comment from web user: frazou **

I had the same problem with VS2010 SP1.But after deleting all files from previous versions of BuildVersionIncrement it worked great!

New Post: Win32 Support

ThiloL — Wed, 24 Apr 2013 14:02:01 GMT

Support for native Win32 app's, using version information in resource file, is needed.

Reviewed: Build Version Increment v2.4.11046.2045 (Apr 24, 2013)

ThiloL — Wed, 24 Apr 2013 13:58:23 GMT

Rated 5 Stars (out of 5) - I got error 80131515 on load. http://blog.tabsstudio.com/2010/06/23/running-add-ins-from-a-network-location-in-visual-studio-2010/ fixed it!

Reviewed: Build Version Increment v2.4.11046.2045 (Apr 24, 2013)

ThiloL — Wed, 24 Apr 2013 13:46:59 GMT

Rated 1 Stars (out of 5) - I got error 80131515 on load.

Commented Issue: How does this work with deployment ? [8669]

Bazzy — Sun, 07 Apr 2013 21:29:52 GMT

A couple of issues I've noticed when using it with VS 2010. In Release mode when I do a build I get two "Can't update build version without specifying an assembly info file." errors, which was not there before. The build still succeeds though, and the assembly version gets incremented.

My application solution also has a deployment project. The incremented assembly version in the application doesn't apply to the deployment project (in the same solution), which is an issue for me. This is important as it is my understanding that to create an installer that will over-write a previous install of you product, the GUID must be different from the current install, otherwise you're forced to uninstall the previous version of your app manually before installing a new one. I may be missing something here though - if anyone can tell me how to make the version increment apply to a deployment project in the same solution, while at the same time generating a new GUID, I would love to know about it !~

Thanks,

Bazzy
Comments: ** Comment from web user: Bazzy **

I poked around and it seems that if you don't use the Solution level settings, and just the Project level ones, then the errors go away. However I still see no way to use this with deployment projects in the same solution. My app increments, but the deployment project associated with it doesn't.

Created Issue: How does this work with deployment ? [8669]

Bazzy — Sun, 07 Apr 2013 20:59:29 GMT

Reviewed: Build Version Increment v2.2 Beta (Apr 07, 2013)

Bazzy — Sun, 07 Apr 2013 20:43:21 GMT

Rated 4 Stars (out of 5) - A couple of issues I've noticed when using it with VS 2010. First off, I select Release for the configuration to increment (not both), but in Debug mode a build gets incremented anyway. In Release mode when I do a build I get a "Can't update build version without specifying an assembly info file." which was not there before. The build still suceeds though, and the assembly version gets incremented

New Post: Rolling increments

spcghst440 — Fri, 05 Apr 2013 12:22:36 GMT

I wonder if you could add the ability to have rolling incrementals.

For example if we wanted to cap our increments at 999, and we had this as our version pattern:

None.None.None.Increment

When the revision passed 999, it would roll back to zero, and increment the build by 1. Then when the build passed 999 it would reset back to zero, and increment the minor by 1.

Or if the user prefers to manually manage their major and minor as sometimes we like to do, then maybe you could come up with something like this:

None.None.RollingIncrement.RollingIncrement

So that the rolling increment would only affect the parts the developer wanted to.

Lastly, the (999) max number should be configurable by the settings. I just used 999 as an example.

Commented Issue: Error in 'Project Modified' Calculation: Doesn't Traverse All Folders [8615]

grothag — Tue, 02 Apr 2013 18:13:55 GMT

The calculation of "if a project is modified" only looks at root items or items that are in a sub-folder. It does not appropriately look at items within a folder within a folder. I propose modifying the IsProjectModified function to call a recursive function CheckProjectItemsModified with the call
```
if (CheckProjectItemsModified(project.ProjectItems, project, GetCachedFileDate(outputFileName, fullPath))) return true;
```
and the function definition
```
private bool CheckProjectItemsModified(ProjectItems items, Project project, DateTime outputFileDate)
{
foreach (ProjectItem item in items)
{
// PhysicalFolder
// VirtualFolder
if (item.Kind == "{6BB5F8EF-4483-11D3-8BCF-00C04F8EC28C}" ||
item.Kind == "{6BB5F8F0-4483-11D3-8BCF-00C04F8EC28C}")
{
if (CheckProjectItemsModified(item.ProjectItems, project, outputFileDate)) return true;
}
else if (CheckProjectItem(item, outputFileDate))
{
Logger.Write(String.Format("Project's ('{0}') item '{1}' is modified. Version will be updated.", project.Name, item.Name), LogLevel.Debug);
return true;
}
}
return false;
}
```
Comments: ** Comment from web user: grothag **

Thanks. This solved my problem.

New Post: Odd Tools Menu Interaction With GIT Add-In (VS2010)

cmshawn — Mon, 01 Apr 2013 19:29:18 GMT

I also saw this behavior, but have not continued to use this product (see my other post), so don't know if it would have eventually gone away.

New Post: Be aware, this is a very different product than Versioning Controlled Build

cmshawn — Mon, 01 Apr 2013 19:27:57 GMT

I'll admit that I haven't used this add-on extensively, but I found it to have drastically different behavior than the Versioning Controlled Build add-on that inspired it.

Not that there's anything wrong with this add-on. I just want to clarify for others who, like me, may be looking for something more like VCB.

The focus of this add-on seems to be on automatically incrementing the version for projects (or solution-wide) on every build. I primarily use VCB to manually set all project versions in a solution to the same version before a QA or production release, so this add-on didn't quite meet my particular needs.

Other than that, it seems a fine product :-)

Commented Issue: VS 2012 version [8593]

avolaande — Wed, 27 Mar 2013 16:45:26 GMT

It may be neat that a 2010 version can be made to work with 2012, but isn't it time for a proper 2012 installer?

Thanks and great work so far!
Comments: ** Comment from web user: avolaande **

Here You find uploaded source that includs also VS 2012 solution that creates also VS 2012 and VS2010 compatible installer.
http://www.codeplex.com/Download?ProjectName=autobuildversion&DownloadId=646357

Patch Uploaded: #14177

avolaande — Wed, 27 Mar 2013 16:37:59 GMT

avolaande has uploaded a patch.

Description:
Made version 2.6 that includes next changes:
* Feature: Visual Studio 2012 solution file and settings there to generate VS 2012 supported plug-in.
* Feature: Now should this plug-in support also Visual Studio BizTalk 2010 project that is configured to work like ".csproj" project type. Not to much tested but currently seems works well. Maybe You accept to add these minor changes also into official source :-)

Here is full source with changes uploaded if someone intrested to try this.

Created Issue: MS BizTalk project type support = ".btproj" [8655]

avolaande — Wed, 27 Mar 2013 16:30:11 GMT

Would be nice if this tool supports also Visual Studio Microsoft BizTalk 2009/2010 project type ".btproj"
ProjectTypeGuid = "{EF7E3281-CD33-11D4-8326-00C04FA0CE8D}"

Created Issue: Error in 'Project Modified' Calculation: Doesn't Traverse All Folders [8615]

erdomke — Fri, 08 Mar 2013 21:25:11 GMT

New Post: Odd Tools Menu Interaction With GIT Add-In (VS2010)

gsokoll — Thu, 07 Mar 2013 01:31:33 GMT

Found that exiting and restarting VS a few times fixed the issue.

New Post: Odd Tools Menu Interaction With GIT Add-In (VS2010)

gsokoll — Wed, 06 Mar 2013 06:18:44 GMT

I have the same issue. VS 2010, BVI 2.5.11219.2200, Git Extensions 2.44

Here is a screenshot - you can see the top two lines are for BVI, while the remaining lines are for Git Extensions. All commands seem to work ok...