#1
|
|||
|
|||
VS.NET action version fails with multiple AssemblyInfo files
We have an architecture with the [assembly] directives placed in two different files, one which is common across our entire product line, and one which is specific to a particular project.
When using the VS.NET action, and setting version to a specific value, the action updates both of these files to contain the AssemblyFileVersionAttribute, AssemblyInformationalVersionAttribute, and AssemblyVersionAttribute attributes. This results in the build failing. Any suggestions? |
|
|