Got the same result here, when i tried what you have. Looks like a genuine bug, if your existing assemblyinfo file has 1.0.* in it. Strange, anything that is not a valid version number causes the same problem. Works a treat if you remove the 1.0.* though. Id just make it 1.0.0.0 and replace via the task.
MSBuild extensions AssemblyInfo fails with version number not valid
-
29-11-2021 - |
Question
I am using the 64 bit msbuild extensions and I have this in my build file
<AssemblyInfo AssemblyInfoFiles="$(MSBuildProjectDirectory)\DesktopAgent\properties\AssemblyInfo.cs"
AssemblyCopyright="Copyright 2012 Alpine Access"
AssemblyVersion="1.0.0.0"
AssemblyFileVersion="1.0.0.0"
>
</AssemblyInfo>
I have this in my assemblyInfo.cs if it matters
[assembly: AssemblyVersion("1.0.*")]
//[assembly: AssemblyFileVersion("2.1.0.0")]
second line is commented out as I read that in another post but it didn't help.
I get the following error
C:\AAROOT\csharpprojects\toolbar\project.build(17,5): error MSB4018: System.Arg
umentException: The specified string is not a valid version number\r
2 questions
- why do I get this error
- Will this task overwrite/modify my previous AssemblyInfo.cs file? (I don't know whether AssemblyInfoFiles is the input/output or both)
On a side note, the property $(MSBuildExtensionsPath) gets set to the 32 bit path for some odd reason(I only installed the 64 bit tools so that path doesn't work and I have to set the property manually....is this some kind of bug in their installer that they didn't set that property correctly?
thanks, Dean
Solution
Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow