Solved

.exe version in VB6 and Visual Studio 2005

Posted on 2010-08-17
6
331 Views
Last Modified: 2013-11-27
HI,
have a few apps compiled in VB6 with .exe version format 0.00.0000, now when I create winforms app in VS2005 or 2008 .exe version format is 0.0.0.0 . How can I set version format like in VB6, is it posibble and how?

Thanks
0
Comment
Question by:kahvedzic
  • 3
  • 2
6 Comments
 
LVL 53

Expert Comment

by:Dhaest
ID: 33453332
You can set this in your assemby-file

[assembly: AssemblyVersion("0.00.0000")]


Managing assembly version numbers using Visual Studio .NET and Visual SourceSafe
http://www.codeproject.com/KB/dotnet/ManagingAssemblyVersions.aspx
0
 
LVL 1

Author Comment

by:kahvedzic
ID: 33453502
I did this

[assembly: AssemblyVersion("1.01.0000")]

and again after I have builded .exe version it was 1.0.0.1 which is not OK with me.
0
 
LVL 17

Expert Comment

by:Zhaolai
ID: 33454440
It seems that you can not format assembly version, but only file version and product version.

Add this line to AssemblyInfo.vb file:

<Assembly: AssemblyVersion("1.01.0000")>
<Assembly: AssemblyFileVersion("1.01.0000")>



0
Master Your Team's Linux and Cloud Stack

Come see why top tech companies like Mailchimp and Media Temple use Linux Academy to build their employee training programs.

 
LVL 1

Author Comment

by:kahvedzic
ID: 33461731
I have both of those lines in my assemblyinfo.vb and I try just like this first time, but still have same issue.
0
 
LVL 53

Accepted Solution

by:
Dhaest earned 500 total points
ID: 33461888
The following table lists Visual Basic 6.0 version-number properties and their Visual Basic 2005 equivalents.

Visual Basic 6.0                 Visual Basic 2005  
No equivalent                    My.Application.AppInfo.Version.Build
 Major                                My.Application.AppInfo.Version.Major
 Minor                                My.Application.AppInfo.Version.Minor
 Revision                           My.Application.AppInfo.Version.Revision

Note  
In Visual Basic 6.0, Revision is the fourth part of the version number; in Visual Basic 2005, it is the third part

In .NET, the version number convention is:

(Major version).(Minor version).(Revision number).(Build number)
0
 
LVL 1

Author Closing Comment

by:kahvedzic
ID: 33464689
Thanks a lot this was really helpful.

Cheers
0

Featured Post

Announcing the Most Valuable Experts of 2016

MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Many of us here at EE write code. Many of us write exceptional code; just as many of us write exception-prone code. As we all should know, exceptions are a mechanism for handling errors which are typically out of our control. From database errors, t…
More often than not, we developers are confronted with a need: a need to make some kind of magic happen via code. Whether it is for a client, for the boss, or for our own personal projects, the need must be satisfied. Most of the time, the Framework…
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…

808 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question