AssemblyVersion not accepting 1.0.*.1

  • Thread starter Thread starter D. Appel
  • Start date Start date
D

D. Appel

Hi all,

According to the documentation of the AssemblyVersionAttribute, it should
accept version strings like '1.0.*.0'
However, when I use that format I get an error:
(29): Error emitting System.Reflection.AssemblyVersionAttribute'
attribute -- 'The version specified '1.0.*.0' is invalid'

The line in my AssemblyInfo.cs reads:
[assembly: AssemblyVersion("1.0.*.1")]

I would like to be able to specify Major,Minor and Revision but use the
automatic Build number... am I doing something wrong, is this a bug, or is
the documentation incorrect?

TIA
Dick Appel
 
-- Whoops, ofcourse the version number in the error messages and the version
number in the AssemblyInfo.cs do match ... ;-)
 
The documentation I have says you can use an asterisk for Build if you
specify Major and Minor, but it doesn't say you can specify Revision if you
use an asterisk for Build. It shows the following examples of valid version
numbers:

1
1.1
1.1.*
1.1.1
1.1.1.*
1.1.1.1

Which documentation are you looking at?

D. Appel said:
-- Whoops, ofcourse the version number in the error messages and the version
number in the AssemblyInfo.cs do match ... ;-)

D. Appel said:
Hi all,

According to the documentation of the AssemblyVersionAttribute, it should
accept version strings like '1.0.*.0'
However, when I use that format I get an error:
(29): Error emitting System.Reflection.AssemblyVersionAttribute'
attribute -- 'The version specified '1.0.*.0' is invalid'

The line in my AssemblyInfo.cs reads:
[assembly: AssemblyVersion("1.0.*.1")]

I would like to be able to specify Major,Minor and Revision but use the
automatic Build number... am I doing something wrong, is this a bug, or is
the documentation incorrect?

TIA
Dick Appel
Click to expand...
Click to expand...
 
I've seen that list as well... but the documentation I'm referring to is the
'About the AssemblyVersionAttribute class' documentation, which states:

"A version number such as [assembly:AssemblyVersion("1.2.*.6")] specifies 1
as the major version, 2 as the minor version, accepts the default build
number, and specifies 6 as the revision number."

That's what gave me the idea that this should be possible... but I'm really
hoping that documentation is correct, because I would like it to work like
that...



Bret Mulvey said:
The documentation I have says you can use an asterisk for Build if you
specify Major and Minor, but it doesn't say you can specify Revision if you
use an asterisk for Build. It shows the following examples of valid version
numbers:

1
1.1
1.1.*
1.1.1
1.1.1.*
1.1.1.1

Which documentation are you looking at?

D. Appel said:
-- Whoops, ofcourse the version number in the error messages and the version
number in the AssemblyInfo.cs do match ... ;-)

D. Appel said:
Hi all,

According to the documentation of the AssemblyVersionAttribute, it should
accept version strings like '1.0.*.0'
However, when I use that format I get an error:
(29): Error emitting System.Reflection.AssemblyVersionAttribute'
attribute -- 'The version specified '1.0.*.0' is invalid'

The line in my AssemblyInfo.cs reads:
[assembly: AssemblyVersion("1.0.*.1")]

I would like to be able to specify Major,Minor and Revision but use the
automatic Build number... am I doing something wrong, is this a bug,
Click to expand...
Click to expand...
or
is
Click to expand...
Click to expand...
 
Back
Top