Open Botan626 opened 3 days ago
maybe updating logic from @Rudokhvist will help you to solve this
Not an issue with ASFE - ASF for compatibility reasons will update the plugin to the same version if more than one zip asset is found, since new ASF version could decide to use different asset than the one used in the previous run.
I have no clue why ASFE provides a zip asset per language though :slightly_smiling_face:
I have no clue why ASFE provides a zip asset per language though 🙂
So having only single ASFEnhance.zip archive in ASFE releases would fix it?
Yes, although what you're describing is not an issue, plugin can force itself to be updated to the same version at any time it wants, and it should never cause you issues.
plugin can force itself to be updated to the same version at any time it wants
I'm pretty sure @chr233 never intended this.
since new ASF version could decide to use different asset
And if the asset ASF decided to update to is the same as current one?
In this case ASFE is in the ASFEnhance-en-US
directory (asset name?), version is the same (2.2.3.3), why updating?
Not an issue with ASFE - ASF for compatibility reasons will update the plugin to the same version if more than one zip asset is found, since new ASF version could decide to use different asset than the one used in the previous run.
I have no clue why ASFE provides a zip asset per language though 🙂
tried use resx for multiple language support, and it will output resource dlls like zh-hans/ASFEnhance.resources.dll
, and the plugin will always use the default language, even if define a linguage in String.Format method (tested in ASF 5.x.x.x), so I decide to use this way, not elegant enough, but it works
All ASF plugins are shipped with multi-lang support and they work fine, so it seems ASFE does something different which is why it doesn't load. You definitely should not have a real need for that.
All ASF plugins are shipped with multi-lang support and they work fine, so it seems ASFE does something different which is why it doesn't load. You definitely should not have a real need for that.
You are right, this's a "historical issues"
During updating ASF from v6.0.7.5 to v6.0.8.0 ASFEnhance was updated from v2.2.3.3 to v2.2.3.3.