Update-Metdata should not change file encoding

[lipkau]

Current behavior

Metadata is hardcoded to use -Encoding UTF8.
UTF8 is UTF-8 with BOM.

Configuration/Source/Metadata.psm1

Line 595 in 244a7cb

Set-Content -Encoding UTF8 -Path $Path -Value $ManifestContent -NoNewline

Expected behavior

Metadata should not change the file encoding of the manifest.

Eg: I have my manifest files in UTF-8 without BOM

[Jaykul]

Not sure I agree, in principle. I rather think the Metadata module should force UTF8 without BOM (but that wasn't an option on Set-Content at the time, so I settled for UTF8).

Having said that -- for this one command, I agree that it shouldn't mess with the encoding if it's possible to avoid doing so.

[lipkau]

Suggestion

• use a logic like this to determine if the manifest had BOM before
• use a logic like this to be able to write without BOM