Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebAssembly: Missing Timezone implementation #6368

Open
kumpera opened this issue Jan 2, 2018 · 12 comments
Open

WebAssembly: Missing Timezone implementation #6368

kumpera opened this issue Jan 2, 2018 · 12 comments

Comments

@kumpera
Copy link
Contributor

kumpera commented Jan 2, 2018

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
Copy link
Contributor

joncham commented Jan 2, 2018

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
Copy link
Contributor

@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
Copy link
Contributor

mderoy commented Apr 30, 2018

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

@bfsmithATL
Copy link

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

@robertohein
Copy link

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

@bfsmithATL
Copy link

bfsmithATL commented Apr 7, 2019

This would be quite wonderful if it could get resolved.

@jsakamoto
Copy link

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

@MichaelPeter
Copy link

MichaelPeter commented May 28, 2019

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
Copy link

chucker commented May 28, 2019

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
Copy link

Do we have an update on a possible fix?

@rfcdejong
Copy link

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:

image

when using this code

image

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

@BiggT76
Copy link

BiggT76 commented Feb 4, 2021

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"....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests