Last post Dec 08, 2013 02:41 AM by Angie xu - MSFT
Nov 28, 2013 06:15 AM|sandeepmgupta|LINK
I am confused in between the behavior of AssemblyVersion and AssemblyFileVersion. I know that the AssemblyFileVersion is optional. If not given, the AssemblyVersion is used.
I have a product installed with a class library with AssemblyFileVersion 188.8.131.52 When I create next version of the product which has some changes in the library then it fails to show the changes in the upgraded product.
If I change the AssemblyFileVersion to greater than current then it successfully replaces the file and shows me all the changes after product upgrade in next release.
Upgrade of the assembly in the product also works fine when I set the version number with * for example 1.0.0.*
The Class library (1.0.0.* ) is shared through SVN. On my machine the instead of * it shows me some number greater that 5000. For same project on another dev pc it generates number in 2000 series. Due to this the new release of the product created from other
PC fails replace the assembly of older product having version >5000.
I know the basic thing that it failed becuase the installer found a newer version already deployed so ignored the assemlby from current setup.
We will have to increment version number manually for each release of the class library.
We can keep 1.0.*.* which we create a new number every time but I will have to make sure that I create release from that same PC. I will not be able to create further release from other PC.
Please correct me if I am wrong.
Help me to understand the behavior and best practice to create product release where it is shared in team. I want to keep the version number generation automated to avoid human mistakes while creating release.
Nov 28, 2013 10:42 PM|chetan.sarode|LINK
Nov 28, 2013 11:04 PM|sandeepmgupta|LINK
I have already gone through the above links and then only I posted my question here.
Precisely I want to know if there is any way to set the AssemlyVersion as automatically which will be in sync with other team members. I have 11 class libraries in my website project. If we miss to change the version number for any class library then the
installer fails to replace the file while upgrade.
Seems like this tool http://autobuildversion.codeplex.com/ can help me.
Dec 08, 2013 02:41 AM|Angie xu - MSFT|LINK
For this issue, you could try this add-in on your side, an addin for Visual Studio 2005/2008, build Version Increment v2.4.11046.2045 for Visual Studio 2010.