Reesult of ToString("C") is incomatible in Blazor WebAssembly

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

In ja-JP culture of .NET F/W and . NET5 in desktop, 123.ToString("C") is "\123", but in Blazor WebAssembly, 123.ToString("C") is "￥123".

System.Threading.Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo("ja-JP");
Console.WriteLine(123.ToString("C"));

---

Original Comments

Feedback Bot on 1/10/2021, 07:23 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

---

Original Solutions

(no solutions)

Tagging subscribers to this area: @tarekgh, @safern, @krwq
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This issue has been moved from a ticket on Developer Community.

---

In ja-JP culture of .NET F/W and . NET5 in desktop, 123.ToString("C") is "\123", but in Blazor WebAssembly, 123.ToString("C") is "￥123".

System.Threading.Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo("ja-JP");
Console.WriteLine(123.ToString("C"));

---

Original Comments

Feedback Bot on 1/10/2021, 07:23 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

---

Original Solutions

(no solutions)

Author:	vsfeedback
Assignees:	-
Labels:	area-System.Globalization, untriaged
Milestone:	-

[mkArtakMSFT]

@lewing FYI.

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This issue has been moved from a ticket on Developer Community.

---

In ja-JP culture of .NET F/W and . NET5 in desktop, 123.ToString("C") is "\123", but in Blazor WebAssembly, 123.ToString("C") is "￥123".

System.Threading.Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo("ja-JP");
Console.WriteLine(123.ToString("C"));

---

Original Comments

Feedback Bot on 1/10/2021, 07:23 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

---

Original Solutions

(no solutions)

Author:	vsfeedback
Assignees:	-
Labels:	arch-wasm, area-System.Globalization, untriaged
Milestone:	-

[tarekgh]

In ja-JP culture of .NET F/W and . NET5 in desktop, 123.ToString("C") is "\123", but in Blazor WebAssembly, 123.ToString("C") is "￥123".

I assume this is flipped statement. I am seeing .NET 5.0 is successfully returning ￥123 which is the expected result.

[lewing]

@tarekgh yeah I assume it was just reversed in the explanation.

This looks like is is probably an example of loading in a specific culture that doesn't exist in the default icu data. I think following the instructions at https://docs.microsoft.com/en-us/aspnet/core/blazor/globalization-localization?view=aspnetcore-5.0#blazor-webassembly

@tqiu8 can you add this to the work you're doing to fail when trying to load an unsupported culture.