You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am new to Humanizer and loving it. However I am using it for an extension on a larger system, and other 3rd party vendors might also be using Humanizer potentially with different versions. We have a system in place where binding redirects get automatically created if 2 different vendors have the same dependency on different versions.
This works usually fine with 1 or a handful of libraries but with Humanizer having all it's localization in satellite assemblies, that would be massive to deal with. The host system also already has support for .resx localization so the people can translate my own extension.
I was wondering about 2 possible options.
1: Did anyone else run into a similar situation and maybe there is some Humanizer.Full.dll or something out there?
2: Is there a way to configure Humanizer to do the localization lookup from a path that would have .resx files instead of using the localization assemblies?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am new to Humanizer and loving it. However I am using it for an extension on a larger system, and other 3rd party vendors might also be using Humanizer potentially with different versions. We have a system in place where binding redirects get automatically created if 2 different vendors have the same dependency on different versions.
This works usually fine with 1 or a handful of libraries but with Humanizer having all it's localization in satellite assemblies, that would be massive to deal with. The host system also already has support for .resx localization so the people can translate my own extension.
I was wondering about 2 possible options.
1: Did anyone else run into a similar situation and maybe there is some Humanizer.Full.dll or something out there?
2: Is there a way to configure Humanizer to do the localization lookup from a path that would have .resx files instead of using the localization assemblies?
Beta Was this translation helpful? Give feedback.
All reactions