Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
NETCoreApp 1.0 #65
I could surely use a hand with getting this library working on .NET Core. Even some initial guidance and recommendations on the approach to take would be great.
It looks like, at the very least, we are going to need to rework some of the i18n support as .NET Core does not support the CurrentCulture properties.
Also, I am not sure if we should try to get the existing NuGet package to be multi platform or if we should just cut ties and create a new .NET Core compatible library that is not backwards compatible with the existing one. I am leaning in this direction.
Indeed, and because .NET core doesn't support currentculture, why don't you let the consumer of your library set a culture property als configuration (with possibility to override this configuration with a setter like SetCurrentLocale(string locale = "en-US") ) which changes the current culture info. Because for my example I'll be using this in an ASP.NET core application, which gets the culture from either the browsersetting or a culture chosen by the user.