How to update Application Version Number in VB.net created programs.

In my add/remove program list I see that all my information I inputted into the Application >> Assembly Window. I have a splash screen active with the following code:
Version.Text = System.String.format(Version.Text, MyApplication.Info.Version.Major,  MyApplication.Info.Version.Minor,  MyApplication.Info.Version.Build, MyApplication.Info.Version.revision)

Open in new window


In my splash screen the information comes up correctly. However in the add remove program screen under the version column it is listed as 1.0.0

Any Ideas what could be going on?
cmdolcetAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Fernando SotoRetiredCommented:
Hi cmdolcet;

Assuming that when you say "However in the add remove program screen under the version column it is listed as 1.0.0". If this information is from a page in your application and not some other application then the question is how are you accessing the version number for that page? Please note that in the projects Assembly Information dialog page there are two version numbers first one is called Assembly Version and the second is File Version. Is it possible you are using File Version in the "add remove program screen" and not Assembly Version?

From Documentation
.NET framework provides opportunity to set two different types of version numbers to each assembly.
 
Assembly Version : This is the version number used by framework during build and at runtime to locate, link and load the assemblies. When you add reference to any assembly in your project, it is this version number which gets embedded. At runtime, CLR looks for assembly with this version number to load. But remember this version is used along with name, public key token and culture information only if the assemblies are strong-named signed. If assemblies are not strong-named signed, only file names are used for loading.
 
Assembly File Version : This is the version number given to file as in file system. It is displayed by Windows Explorer. Its never used by .NET framework or runtime for referencing.
 
Attributes in AssemblyInfo.cs
// Version information for an assembly consists of the following four values:
//
//      Major Version
//      Minor Version
//      Build Number
//      Revision
//
[assembly: AssemblyVersion("1.0.0.0")]
[assembly: AssemblyFileVersion("1.0.0.0")]
 
Providing a (*) in place of absolute number makes compiler increase the number by one every time you build.
 
Suppose you are building a framework assembly for your project which is used by lot of developers while building the application assemblies. If you release new version of assembly very frequently, say once every day, and if assemblies are strong named, Developers will have to change the reference every time you release new assembly. This can be quite cumbersome and may lead to wrong references also. A better option in such closed group and volatile scenarios would be to fix he 'Assembly Version' and change only the 'Assembly File Version'. Use the assembly file version number to communicate the latest release of assembly. In this case, developers will not have to change the references and they can simply overwrite the assembly in reference path. In central/final release builds it makes more sense to change the 'Assembly Version' and most keep the 'Assembly File Version' same as assembly version.
If my assumption is incorrect please post more detail information on your needs.
cmdolcetAuthor Commented:
Please see the attached assembly information screen shot.
Application-Assembly-Information.PNG
Fernando SotoRetiredCommented:
Details please.
Become a Microsoft Certified Solutions Expert

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

cmdolcetAuthor Commented:
All I do is enter the assembly info under the application tab and enter in the Assembly version and file version as the same number. Then on the splash page I call the code above.

Usually I make a build at least once per week to fix various issues with the program.
cmdolcetAuthor Commented:
What I am looking for is that Assembly version to make the version number listed in the version of the add/remove page.
Fernando SotoRetiredCommented:
And where is this located, “What I am looking for is that Assembly version to make the version number listed in the version of the add/remove page.”, is this part of your app? Or some other app?
cmdolcetAuthor Commented:
No this is part of my app. Do you think because the Assembly Version and File Version are the same that could be causing the issue?
Fernando SotoRetiredCommented:
Please post the code that you use where it is not giving you the correct results.
it_saigeDeveloperCommented:
In Add/Remove Programs you are seeing the version of the Installer, not your application.  You will need to update the installer's version to match your applications version.

-saige-

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
cmdolcetAuthor Commented:
it_saige, ok that would make sense Where in the installer would I change this number?

Fernando Soto the only code I have in reference to this was posted on the initial questions. I am thinking it_saige is down the right path, however I dont see anywhere in to update the installer version.
cmdolcetAuthor Commented:
Wait I believe I see it I will change the version number out.

Thank you. Is there a better way to do this to always change this number manually?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic.NET

From novice to tech pro — start learning today.