I suggest you ...

Detect a maximum XAML errors at compile time

Currently, some XAML syntax errors are caught at compile time. But most errors are only caught at design time or worse, at run-time.

Some examples :
- Wrong StaticResource key
- A non numeric value in a numeric property like Width or Height. If I write <Grid Width="ruru" />, the compiler detects nothing !!!

It would be great too to provide strongly typed bindings with something like lambda expressions in ASP.NET MVC. With this syntax, you could also add support for refactoring in XAML, find all references, etc.

18 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Nicolas Séveno shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base