Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

VB.Net Error setting auto increment in assembly version

Posted on 2006-10-23
8
Medium Priority
?
1,739 Views
Last Modified: 2008-02-07
Hi All,

I get this error when setting the assembly version to autoincrement in vs2005.

the AssembyInfo.vb file has the following:

<Assembly: AssemblyVersion("1.0.0.*")>
<Assembly: AssemblyFileVersion("1.0.0.*")>

The error (warning) is:


Warning      3      Possible problem detected while building assembly 'ATMS': The version '1.0.0.*' specified for the 'file version' is not in the normal 'major.minor.build.revision' format      
0
Comment
Question by:nzfire
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 4
8 Comments
 
LVL 13

Expert Comment

by:newyuppie
ID: 17793497
is your assembly strong named?
0
 
LVL 1

Author Comment

by:nzfire
ID: 17799014
Hi newyuppie,

Am new to .Net and this will be my first major app in vb.net, so excuse the ignorance, but please could you give me a bit of a run-down on strongly naming an assembly. I've heard of it, but don't know how it works.

Thanks
0
 
LVL 1

Author Comment

by:nzfire
ID: 17799256
Hi Again All,

I have read up on strong assemblies, naming and signing and have signed my assembly.

I still get the error.

By the way, if I go into Sign the Assembly and create a new key from the option to create a key or browse for a key, a dialog box appears which allows you to name the key and set the password.

In that dialog box, the fields are enabled, but I cannot type anything in there, but the paste function works. ???? Any ideas?

Thanks again
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
LVL 13

Expert Comment

by:newyuppie
ID: 17799351
if you are using vb2005 its actually very easy. you need to go to project properties (rightclick on the prohect name on the SOlution Explorer to the right and select properties).

on this new window, on your left you get different panes. go to the Signing pane and check "Sign the assembly". Then on the dropdown list select <New...> and create a new key with a password you provide. then save and compile. see if this resolves the assembly version issue.
0
 
LVL 1

Author Comment

by:nzfire
ID: 17799392
Yep, done that again and this time specified one with a password, but still get the same warning.

I am wondering if it is something to do with the format of the version string.

Here is the bit of the assemblyinfo.vb file

' You can specify all the values or you can default the Build and Revision Numbers
' by using the '*' as shown below:
' <Assembly: AssemblyVersion("1.0.*")>

<Assembly: AssemblyVersion("1.0.0.*")>
<Assembly: AssemblyFileVersion("1.0.0.*")>

<Assembly: NeutralResourcesLanguageAttribute("en-NZ")>
0
 
LVL 13

Accepted Solution

by:
newyuppie earned 2000 total points
ID: 17799522
yeah apparently AssemblyFileVersion does not do well with *
nevertheless, you can use the * thing in AssemblyVersion without problems. and from what i understand, AssemblyFileVersion defaults to AssemblyVersion, so maybe you can remove the <Assembly: AssemblyFileVersion("1.0.0.*")> alltogether and only keep the <Assembly: AssemblyVersion("1.0.0.*")>.

does that help?


from MSDN documentation "Understanding and Using Assemblies and Namespaces in .NET"
Table 1. Standard assembly attributes

Attribute Meaning
AssemblyCompany Company shipping the assembly
AssemblyCopyright Copyright information
AssemblyCulture Enumeration indicating the target culture for the assembly
AssemblyDelaySign True to indicate that delayed signing is being used
AssemblyDescription Short description of the assembly
AssemblyFileVersion String specifying the Win32 file version. Defaults to the AssemblyVersion value.
AssemblyInformationalVersion Human-readable version; not used by the common language runtime
AssemblyKeyFile Name of the file containing keys for signing the assembly
AssemblyKeyName Key container containing a key pair to use for signing
AssemblyProduct Product Name
AssemblyTitle Friendly name for the assembly
AssemblyTrademark Trademark information
AssemblyVersion Version number expressed as a string.

You can also define your own custom attributes by inheriting from the System.Attribute class. These attributes will be available in the assembly manifest just like the attributes listed above.

0
 
LVL 1

Author Comment

by:nzfire
ID: 17799547
Newyuppie,

Warning is GONE!! Done by commenting out the <Assembly: AssemblyFileVersion("1.0.0.*")>

Thanks a million. I've learnt a lot from a silly little thing like that!
0
 
LVL 13

Expert Comment

by:newyuppie
ID: 17799574
glad it worked out! i learn a lot too from researching for little things too!
thanks for the grade

NY
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

Introduction While answering a recent question (http://www.experts-exchange.com/Q_27402310.html) in the VB classic zone, I wrote some VB code in the (Office) VBA environment, rather than fire up my older PC.  I didn't post completely correct code o…
Most everyone who has done any programming in VB6 knows that you can do something in code like Debug.Print MyVar and that when the program runs from the IDE, the value of MyVar will be displayed in the Immediate Window. Less well known is Debug.Asse…
Get people started with the process of using Access VBA to control Excel using automation, Microsoft Access can control other applications. An example is the ability to programmatically talk to Excel. Using automation, an Access application can laun…
Get people started with the utilization of class modules. Class modules can be a powerful tool in Microsoft Access. They allow you to create self-contained objects that encapsulate functionality. They can easily hide the complexity of a process from…
Suggested Courses

609 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