Updating Assembly Info writes file with incorrect encoding

[robv8r]

When you create a file in Visual Studio, it defaults to UTF-8 with BOM. According to StyleCop Rule SA1412:

Storing files in this encoding ensures that the files are always treated the same way by the compiler, even when compiled on systems with varying default system encodings. In addition, this encoding is the most widely supported encoding for features like visual diffs on GitHub and other tooling. This encoding is also the default encoding used when creating new C# source files within Visual Studio.

The AssemblyInfo Activity incorrectly writes a new AssemblyInfo.cs file using UTF-8 without BOM.

The correct behavior would be to either write a new AssemblyInfo.cs file the same encoding as the original file.

Alternatively, the new AssemblyInfo.cs file could always be written using UTF-8 with BOM.

[ThierryBrun]

Hello, i downloaded the zip, added the assemblies to my project to edit the templates, but i don't see AssemblyInfo Activity nor do i see TFSVersion. I'm using TFS 2013 and VS 2013. am i loading the wrong dlls? but i don't see any others in the zip?