Fix Console Encoding for Proper Display of Non-ASCII Characters

[Copilot]

Issue

Azure Functions Core Tools was not correctly displaying non-ASCII characters in console output. Japanese characters (and other non-Latin scripts) were showing as question marks (?????) when logging from a function.

Root Cause

The console output encoding was not explicitly set to UTF-8 at application startup, causing the console to use the default encoding of the system, which often doesn't support the full range of Unicode characters.

Solution

Added a single line at the start of the application to configure the console output encoding to UTF-8:

Console.OutputEncoding = Encoding.UTF8;

This ensures that all Unicode characters, including Japanese and other non-Latin scripts, are properly displayed in the console when running functions locally.

Screenshot

Changes

• Added a single line at the start of the Program.cs Main method to set console encoding to UTF-8
• Added the required System.Text namespace import

Fixes #4429.

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• azfunc.pkgs.visualstudio.com
  • Triggering command: dotnet build src/Cli/func/Azure.Functions.Cli.csproj (dns block)
• pkgs.dev.azure.com
  • Triggering command: dotnet build src/Cli/func/Azure.Functions.Cli.csproj (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[liliankasem]

Fix the build errors:

D:\a\_work\1\s\src\Cli\func\Program.cs(9,1): error SA1208: Using directive for 'System.Text' should appear before directive for 'Colors.Net' (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1208.md) [D:\a\_work\1\s\src\Cli\func\Azure.Functions.Cli.csproj]
D:\a\_work\1\s\src\Cli\func\Program.cs(17,1): error SA1028: Code should not contain trailing whitespace (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1028.md) [D:\a\_work\1\s\src\Cli\func\Azure.Functions.Cli.csproj]
D:\a\_work\1\s\src\Cli\func\Program.cs(25,1): error SA1028: Code should not contain trailing whitespace (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1028.md) [D:\a\_work\1\s\src\Cli\func\Azure.Functions.Cli.csproj]

[jviau]

What is this testing even? The code changes included only set Console.OutputEncoding in Main, but this test does not call that. If this test is passing, it means the setting of UTF8 in Main is redundant.

[Copilot]

You're absolutely right. The test was flawed because it didn't call Main() to set the encoding. I investigated and found that the default console encoding is System.Text.ConsoleEncoding (not System.Text.UTF8Encoding), so our setting in Main() is actually needed. I've removed the problematic helper method and unit test since they weren't meaningful. The E2E tests properly validate the functionality. Commit 7a15472

[Copilot]

Fix the build errors:

...

Fixed the StyleCop violations: reordered using directives (SA1208) and removed trailing whitespace (SA1028). Commit 7a15472

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• azfunc.pkgs.visualstudio.com
  • Triggering command: dotnet build src/Cli/func/Azure.Functions.Cli.csproj (dns block)
  • Triggering command: dotnet build src/Cli/func/Azure.Functions.Cli.csproj --no-restore (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to my firewall allow list