WebAssembly: Missing Timezone implementation

[kumpera]

Corlib is missing a tz implementation. Our current profile tries a unix impl that probes the FS, it should be replaced by stubs or something using browser support.

[joncham]

We fallback to old time zone icall logic to support just Utc and Local time zone's on systems where tz data information is not available: Unity-Technologies@5778842

[migueldeicaza]

@joncham Would you be willing to submit a pull request with the above change, purely so we can get the CLA bot to trigger?

[mderoy]

@joncham We'll need to also get the fixes I put in after the initial PR.

[bfsmithATL]

Just curious if this issue (6368) is still going to be addressed?

[robertohein]

this is going to be fixed? there are any temporary fixes?

[bfsmithATL]

This would be quite wonderful if it could get resolved.

[jsakamoto]

[FYI] This is my workaround at this time for Blazor (client-side) browser applications.

• https://github.com/jsakamoto/Toolbelt.Blazor.TimeZoneKit/

[MichaelPeter]

Is there a fix in sight? Working with Blazor/ NetCore 3.0 Preview 5, I mean we are now in Blazor Beta and I think this is mission critical. Thank you for the toolkit jsakamoto, works great!

[chucker]

I mean we are now in Blazor Beta and I think this is mission critical.

FWIW, this is only relevant for client-side Blazor, which probably won't ship until next year (and definitely not as part of .NET Core 3.0).

[PirasannaRavi]

Do we have an update on a possible fix?

[rfcdejong]

Is this issue still open? Or fixed by now? I look at the NuGet package https://github.com/jsakamoto/Toolbelt.Blazor.TimeZoneKit/ but that one is deprecated saying that it is supported in new blazor code.

I'm using WASM in .NET 5.0 and running into an exception:

when using this code

In what should I change the code so that it will not throw an exception in Blazor?

[BiggT76]

I had a similar issue and changing the timezone on my local machine fixed it (not sure if ours wasn't standard or what). See this issue for more info: dotnet/aspnetcore#22544. Something as simple as "Eastern Standard Time" instead of "US Eastern Standard Time"....