Why can't Avalonia bind to internal
members?
#16906
Closed
colejohnson66
started this conversation in
General
Replies: 1 comment 1 reply
-
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For our application, we want to use ResX localization in our DLL. Everything works fine until we want to bind to resources in XAML. For some reason, our resources class must be
public
for this to work (see the guide). If we don't, the error message claims the member just doesn't exist:Which is bad (it should say it exists, but has wrong accessibility), but that's a different discussion. Why can't Avalonia bind to internal members? Especially because the lowered XAML is just
target2.Text = MyNamespace.Resources.CancelText
. Besides, IL can ignore accessibility modifiers, so they shouldn't matter. Why must I expose my internalResources
type to DLL users just so Avalonia can work?Beta Was this translation helpful? Give feedback.
All reactions