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
In the past, I was confronted with the situation that I re-created XAML views which included styles, e.g. a Style that was set in a Label but wasn’t actually defined anywhere in a Resource Dictionary. The style wasn’t available in the global styles.xml and also not in the local resource dictionary of the ContentPage/ContentView.
There were no compile errors, but the App just crashed for no obvious reason.
This feature request is about errors during Compile already to detect such missing things.
I say things as it can also happen that it is a binding to a property in a ViewModel or View which should be detected during Compile already as missing.
Public API Changes
Don’t know about API changes, just from a User/Developer perspective it would be great to have it.
Intended Use-Case
Early error detection for missing things like Styles, Bindings etc. that are unresolved and lead to crashes in the App when displaying a View/Page
Compile errors would already be sufficient, but maybe also a highlighting in the XAML already.
The text was updated successfully, but these errors were encountered:
Description
In the past, I was confronted with the situation that I re-created XAML views which included styles, e.g. a Style that was set in a
Label
but wasn’t actually defined anywhere in a Resource Dictionary. The style wasn’t available in the globalstyles.xml
and also not in the local resource dictionary of theContentPage
/ContentView
.There were no compile errors, but the App just crashed for no obvious reason.
This feature request is about errors during Compile already to detect such missing things.
I say things as it can also happen that it is a binding to a property in a
ViewModel
orView
which should be detected during Compile already as missing.Public API Changes
Don’t know about API changes, just from a User/Developer perspective it would be great to have it.
Intended Use-Case
Early error detection for missing things like
Styles
,Bindings
etc. that are unresolved and lead to crashes in the App when displaying aView
/Page
Compile errors would already be sufficient, but maybe also a highlighting in the XAML already.
The text was updated successfully, but these errors were encountered: