.NET bundle may be built with non-utf8 but always execute with utf8.

[CreateAndInject]

中文.7z

Create a project with Chinese chars, publish as a single bundle, the target is longer runnable.
The issue is: The bundle is built with non-utf8 encoding(Maybe default encoding of Windows on my PC), but when executing, system always parses it as utf8 encoding.

[dotnet-policy-service]

Tagging subscribers to this area: @agocke, @vitek-karas, @VSadov
See info in area-owners.md if you want to be subscribed.

[elinor-fung]

@CreateAndInject what version of the .NET SDK are you using to publish? Would you be able to try the latest .NET 10 preview? @jtschuster has made a number of changes around bundling in the latest release.

Would you also be able to share (ideally as just an attachment on github - the file hosting site in the description is blocked for me):

• a binlog of the publish
• a host trace of running the application

[CreateAndInject]

@CreateAndInject what version of the .NET SDK are you using to publish? Would you be able to try the latest .NET 10 preview?

You can see from my uploaded project. I try .NET 5-10.

I think you can reproduce it from the PC which default encoding is Chinese chars(eg. gbk).

[agocke]

@jtschuster could you take a look?

[jtschuster]

@CreateAndInject Was this published in Visual Studio, or on the command line? And which .NET 10 preview sdk are you using? The bundler at one point used Encoding.Default which would use the active code page in .NET Framework / when building in VS. With the latest changes in main (and in preview 6), no strings should be written in anything but UTF-8.

[CreateAndInject]

Was this published in Visual Studio, or on the command line?

In Visual Studio

And which .NET 10 preview sdk are you using?

What do you mean? The target framework in my uploaded project is .NET 5. My PC install all .NET 5 - .NET 10 SDK

[jtschuster]

Ah, it looks like the fix for this didn't make it into .NET 10 preview 6. In the meantime, you should be able to work around the issue using dotnet publish from the command line. Preview 7 should fix the issue within Visual Studio as well once it's released.