You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is caused by the hardcoding of the version numbers in the CommonAssemblyInfo.cs file.
We're now using Cake.MinVer to generate the correct versionnumber, and sending that through MSBuild.
This doesn't work for the assemblies (, but it works for the package), since we don't generate the assembly info (GenerateAssebmlyInfo=false). If we set this to true, MSBuild can't override them. We can't set it all from Cake since some information there is target framework dependent. We can't roll that out by compiling for each frameworks, because our projects have different target frameworks.
So the resolution is to generate an AssemblyInfo.g.cs file in the build.cake script, and run that before the build starts. This file is then added to the framework, framework.legacy and the nunitlite projects. The others don't need any version.
This is caused by the hardcoding of the version numbers in the CommonAssemblyInfo.cs file.
We're now using Cake.MinVer to generate the correct versionnumber, and sending that through MSBuild.
This doesn't work for the assemblies (, but it works for the package), since we don't generate the assembly info (GenerateAssebmlyInfo=false). If we set this to true, MSBuild can't override them. We can't set it all from Cake since some information there is target framework dependent. We can't roll that out by compiling for each frameworks, because our projects have different target frameworks.
So the resolution is to generate an AssemblyInfo.g.cs file in the build.cake script, and run that before the build starts. This file is then added to the framework, framework.legacy and the nunitlite projects. The others don't need any version.
Thanks to @CharliePoole for finding this!
The text was updated successfully, but these errors were encountered: