Visual Basic .net, Assembly Revision number not incrementing

What do I need to do to make the revision number change?

In my Assembly, I have <Assembly: AssemblyVersion("1.0.*")>  specified. When I right-click on the bin file, a dll, the Build number is correct (adds up to today's date) but the revision number adds up to a time around 3 am (21368). I rebuilt the dll. Same number. Deleted and recreated the dll. Same number...

How do I make the revision number increment?
Who is Participating?

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

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.

Carlos VillegasFull Stack .NET DeveloperCommented:
Hello, remove the attribute <Assembly: AssemblyFileVersion("")>  from your AssemblyInfo.vb, then try again.
MikeBroderickAuthor Commented:
I'm sorry, it is already removed.
MikeBroderickAuthor Commented:
Update: About an hour elapsed, and when I rebuild the project, I get a new revision number. This doesnt make any sense.
Learn Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

Carlos VillegasFull Stack .NET DeveloperCommented:
Well... I'm not sure if it is a VS IDE bug... but if you reopen your project, change some thing and do a build it is refreshed...
Does the Created/Modified/Accessed dates on General tab of DLL show correct compiled date? This will verify you are looking at the DLL that you recompiled.

Also, make sure assembly: AssemblyFileVersion line is commented out in assembly.vb file. using both AssemblyVersion and AssemblyFileVersion prevents autoincrement for some reason.

Is there any post build event in project properties setting assembly version number?
Carlos VillegasFull Stack .NET DeveloperCommented:
OK, well... check this article:
Controlling Assembly Version

Note   For a Microsoft Visual BasicĀ® .NET project with an AssemblyVersion set to "1.0.*", the assembly version is only updated the first time the project is rebuilt within the Visual Studio .NET integrated development environment (IDE). The version number remains constant for subsequent rebuilds within the same instance of Visual Studio .NET. This does not represent a problem because the assembly version is for information only in assemblies that do not have a strong name. For strong named assemblies, you should avoid the use of wild characters in the AssemblyVersion attribute, as explained in the following section.
For C# projects with an AssemblyVersion set to "1.0.*", the assembly version is updated every time the project is rebuilt.

This is a old article but appear still valid for your case...

Check this too:
Version numbers in a compiled assembly

I hope this can help you.

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
MikeBroderickAuthor Commented:
I closed out the IDS then reopened it, then rebuilt the solution. The revision number changed. Thanks.
Carlos VillegasFull Stack .NET DeveloperCommented:
Glad to help!
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.