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
Is your feature request related to a problem? Please describe.
Particularly as there is more than one Sharpnado package, any UI elements that would be referenced from XAML should be easily available with a single xmlns.
This helps to keep XAML cleaner particularly as you use an aggregate of types across your project as you do not have to remember which assembly something was in or what the clr namespace is.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Particularly as there is more than one Sharpnado package, any UI elements that would be referenced from XAML should be easily available with a single xmlns.
Describe the solution you'd like
Describe alternatives you've considered
n/a
Additional context
Add a XmlnsDefinitionAttribute to all Sharpnado packages like:
This helps to keep XAML cleaner particularly as you use an aggregate of types across your project as you do not have to remember which assembly something was in or what the clr namespace is.
The text was updated successfully, but these errors were encountered: