Skip to content

Conversation

lvmajor
Copy link

@lvmajor lvmajor commented Nov 7, 2019

Not 100% sure that this covers every possible problem with updating to .net core 3.0, but after doing so in a local copy of the project I linked to in my own project, it seems to work as before.

This is to fix #181 and #183 (dupe)

Not 100% sure that this covers every possible problem with updating to .net core 3.0, but after doing so in a local copy of the project I linked to in my own project, it seems to work as before.
@lvmajor
Copy link
Author

lvmajor commented Nov 7, 2019

This implements the recommended approach in official MS migration docs

@m2git
Copy link

m2git commented Jan 2, 2020

Hi, this is very critical fix. Can this be looked into urgently please. Our project is in core 3.0 and I need it badly.

@lvmajor
Copy link
Author

lvmajor commented Jan 2, 2020

@m2git you can temporarily use this package which includes the fix Westwind.Globalization.AspNetCore3 (on Nuget)

@lvmajor
Copy link
Author

lvmajor commented Jan 7, 2020

TBN, it should be updated to target 3.1 now that it's been released and is LTS.

@twenzel
Copy link
Contributor

twenzel commented Feb 17, 2020

@os1r1s110 You can use the Package Westwind.Globalization.AspnetCore31. It was built from PR source #190

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

Successfully merging this pull request may close these issues.

Not working with Asp.Net Core 3.0
4 participants