VS.NET action version fails with multiple AssemblyInfo files

[nanotech]

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?

[kinook]

The Make VS.NET action will only update assembly attributes in the AssemblyInfo.* file of the project, adding the specified attributes if missing or updating if found. If you keep some of the attributes in a different file in the project, do not set those attributes on the Versions/Properties tab of the Make VS.NET action, as it will only update/create them in the AssemblyInfo.* file. You will need to update the attributes in the other file some other way, since the Make VS.NET action will not change them there (one way would be to use a Replace in File action).