Quantcast
Channel: Build Version Increment Add-In Visual Studio
Viewing all 131 articles
Browse latest View live
↧

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

April 7, 2013, 1:59 pm
$
0
0
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
↧
Search

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

April 7, 2013, 2:29 pm
$
0
0
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.

↧
↧

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

April 24, 2013, 6:46 am
$
0
0
Rated 1 Stars (out of 5) - I got error 80131515 on load.
↧

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

April 24, 2013, 6:58 am
$
0
0
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!
↧

New Post: Win32 Support

April 24, 2013, 7:02 am
$
0
0
Support for native Win32 app's, using version information in resource file, is needed.
↧
↧

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

April 26, 2013, 8:15 am
$
0
0
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!

↧

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

April 30, 2013, 2:33 pm
$
0
0
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?
↧

New Comment on "Documentation"

May 19, 2013, 8:16 pm
$
0
0
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.
↧
Search

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

May 19, 2013, 8:17 pm
$
0
0
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 Post: Doesn't work with WPF and codebehind files

June 3, 2013, 9:22 am
$
0
0
I've found a bug with the current method of iterating through the project items for a WPF project, be it c# or vb. It is a well known bug with automation in visual studio for these project types. Ahhh Microsoft...

Basically when iterating only the top most file "Application.xaml" will be checked as this appears in the project items but "Application.xaml.vb" could have changed without the top file changing and wouldn't trigger the update.

Any ideas on a fix? I've included code in my own version to check for this instance, but its a bit of a hack.
↧

Patch Uploaded: #14621

June 7, 2013, 6:42 am
$
0
0

gerwulf has uploaded a patch.

Description:
As others already noted (e.g. user 'nexbit' in the Release Notes of version 2.5.11219.2200), using the date based incrementors fails if you use this add-in with an english VS on a localized OS.

I changed the code of BuildVersionIncrementor.cs in CheckProjectItem() to use CultureInfo.InstalledUICulture instead of CultureInfo.CurrentCulture. This gets the default UI language of the OS, while CurrentCulture just gets the setting for the currently running thread. Since the add-in runs inside of an english IDE, this would always return en-US (same as the invariant culture).

With InstalledUICulture, this now Works For Me (tm). I also modified the logging to a more verbose error message, making the reasons behind further errors clearly visible.

Note that this would still fail if a user is using a localized OS (say, german), works inside an english VS, but has changed his regional date/numbers settings (determining CurrentCulture) to something else (e.g. french).

↧

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

June 7, 2013, 6:49 am
$
0
0
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: gerwulf **

I uploaded a patch for BuildVersionIncrementor.cs which uses CultureInfo.InstalledUICulture instead of CurrentCulture. This way, it tries to parse the date string in the OS's culture first (even if the IDE is using en-US for its threads (and thus, its add-ins)), then defaults to the invariant culture (en-US) in case of errors.

Try it - this now works for me (english VS 2010 SP1 on german WinXP SP3).

↧

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

June 11, 2013, 3:04 am
$
0
0
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: BenXXX **

Hi everybody

I suffered this "Warning mess" also. So I solved it (at least for me) and provide the code/thoughts here.

Conditions:
Windows 7, english
Visual Studio, english (are there other versions? Dunno..)
Local Settings set to another country than englisch/us

This is a common scenario for developers outside the empire. You want english error messages with which you can extract meaningful answers from google. Error messages in suaheli will not help much. But you dont want using these old fashioned elbow and foot measurements. And also use your local datetime.


Simple test in BuildVersionIncrementor.cs
```
Logger.Write(String.Format("Parse DateTime '{0}'", itemDateString), LogLevel.Info);
Logger.Write(String.Format("CultureInfo.InstalledUICulture.Name '{0}'", CultureInfo.InstalledUICulture.Name), LogLevel.Info);
Logger.Write(String.Format("CultureInfo.CurrentCulture.Name '{0}'", CultureInfo.CurrentCulture.Name), LogLevel.Info);
Logger.Write(String.Format("CultureInfo.CurrentUICulture.Name '{0}'", CultureInfo.CurrentUICulture.Name), LogLevel.Info);
Logger.Write(String.Format("CultureInfo.InvariantCulture.Name '{0}'", CultureInfo.InvariantCulture.Name), LogLevel.Info);
```

resulted in
```
[Info] Parse DateTime '22.01.2013 13:36:58'
[Info] CultureInfo.InstalledUICulture.Name 'en-US'
[Info] CultureInfo.CurrentCulture.Name 'en-US'
[Info] CultureInfo.CurrentUICulture.Name 'en-US'
[Info] CultureInfo.InvariantCulture.Name ''
```

==> Always US, but my system has european date format configured!
I don't know why in an VS Addin CurrentCulture delivers en-US. I tested a simple Winforms app. There, CurrentCulture delivers the currently configured format.

So, the workaround is to use Pinvoke:

```
using System.Runtime.InteropServices;

[DllImport("kernel32.dll")]
static extern uint GetUserDefaultLCID();

int lcid = Convert.ToInt32(GetUserDefaultLCID());
CultureInfo formattingCultInfo = new CultureInfo(lcid);
itemFileDate = DateTime.Parse(itemDateString, formattingCultInfo );
```

↧
↧

Commented Issue: System.FormatException [7561]

July 3, 2013, 6:12 am
$
0
0
I have this error:
 
Error occured while reading BuildVersionIncrement settings from "XXX.vcxproj"
System.FormatException: String was not recognized as a valid Boolean.
at System.Boolean.Parse(String value)
at BuildVersionIncrement.SolutionItemIncrementSettings.Load()
 
The system is W7x64 (Catalan), VS2010 (English). any clue?.
 
Regards,
Comments: ** Comment from web user: kaczorck **

I have just the same issue. It is only on C++ project it does not happen on other attached in Solution .NET projects.

Error 3 Error occured while reading BuildVersionIncrement settings from "_____.vcxproj"
System.FormatException: String was not recognized as a valid Boolean.
at System.Boolean.Parse(String value)
at BuildVersionIncrement.SolutionItemIncrementSettings.Load()

If you have found solution for the issue please let me know.

Best Regards,

↧

Commented Issue: System.FormatException [7561]

July 5, 2013, 8:24 am
$
0
0
I have this error:
 
Error occured while reading BuildVersionIncrement settings from "XXX.vcxproj"
System.FormatException: String was not recognized as a valid Boolean.
at System.Boolean.Parse(String value)
at BuildVersionIncrement.SolutionItemIncrementSettings.Load()
 
The system is W7x64 (Catalan), VS2010 (English). any clue?.
 
Regards,
Comments: ** Comment from web user: kaczorck **

Hey I've got it.
of some reason this BuildVersionIncrement Add-in have saved in vcxproj settings. All settings was with null values.
You yould edit __xxxxx.vcxproj__ file it is common XML file.
the the end in __<ProjectExtensions>__ .. __<VisualStudio>__ you should edit __<UserProperties....>__
```
<ProjectExtensions>
<VisualStudio>
<UserProperties BuildVersion_UseGlobalSettings="" BuildVersion_AssemblyInfoFilename="" BuildVersion_StartDate="" BuildVersion_BuildVersioningStyle="" BuildVersion_UpdateFileVersion="" BuildVersion_UpdateAssemblyVersion="" />
</VisualStudio>
</ProjectExtensions>
```
Paste filled one: ex:
```
<ProjectExtensions>
<VisualStudio>
<UserProperties BuildVersion_UseGlobalSettings="False" BuildVersion_AssemblyInfoFilename="AssemblyInfo.cpp" BuildVersion_StartDate="2012/8/6" BuildVersion_BuildVersioningStyle="DeltaBaseYear.MonthStamp.Increment.TimeStamp" BuildVersion_UpdateFileVersion="False" BuildVersion_UpdateAssemblyVersion="True" />
</VisualStudio>
</ProjectExtensions>
```

be aware not to set ___BuildVersion_UpdateFileVersion="False"___ in standard VC++ projects common __AssemblyInfo.cpp__ does not have such variable. That might caused all the issues.

↧
Search

Created Unassigned: Visual Studios 2013 Support [8871]

July 12, 2013, 9:53 am
$
0
0
Will there be support for Visual Studio 2013?
↧

New Comment on "Documentation"

August 6, 2013, 1:11 pm
$
0
0
Is there anyway to set this utility up to increment the major version after so many minor versions?
↧
↧

New Post: HOW not auto increment a referred project

August 9, 2013, 1:40 pm
$
0
0
So do I, is there an approach to resolve this issue?
↧

New Post: Silly Question... how do I know if it's working?

August 9, 2013, 11:16 pm
$
0
0
I've installed the plugin on VS2010, and went to the tools menu and configured it for my project.

Then I built my project. There was no message or anything to suggest that anything was different.

My program's ABOUT box grabs the value from:

System.Reflection.Assembly.GetExecutingAssembly().GetName().Version.ToString();

From what I'd read about the plugin, the string in ASSEMBLYINFO.CS where this comes from is supposed to be altered on each build. Yet, the ASSEMBLYINFO.CS file is unchanged and the string in the ABOUT box does not update.

So... how do I know if it's working? How do I get the updated version number at build time?
↧

New Comment on "Documentation"

August 9, 2013, 11:17 pm
$
0
0
Is this supposed to update AssemblyInfo.cs (or language equivalent) by default? I am not seeing that happen.
↧
Viewing all 131 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>