G
Guest
I see from my searches that this has be discussed before.
However I can find no satisfactory answer or any reference to this problem
being a bug.
From the MSDN documentation for this attribute:-
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.
However when I build an assembly with this assembly version I get the error:-
The version specified is invalid.
I like the daily build based build number and want to use it. I don't like
the crazy milliseconds since midnight revision number and want to control the
revision number myself.
Am I doing something wrong or is the documentation wrong? If the
documentation is wrong how useful do MS think this automatic system is in the
real world?
Thanks In advanced,
Anthony.
However I can find no satisfactory answer or any reference to this problem
being a bug.
From the MSDN documentation for this attribute:-
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.
However when I build an assembly with this assembly version I get the error:-
The version specified is invalid.
I like the daily build based build number and want to use it. I don't like
the crazy milliseconds since midnight revision number and want to control the
revision number myself.
Am I doing something wrong or is the documentation wrong? If the
documentation is wrong how useful do MS think this automatic system is in the
real world?
Thanks In advanced,
Anthony.