Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Please find the solution demonstrating this problem here:
Using the latest 1.3.5 (released today) I am able to build this solution, even though I have defined an object in Xaml that is invalid. Specifically, I have defined a property that does not exist starting at this line:
If you run the solution (real simple WPF application to keep things light), you will see that the program errors out while trying to load the file here:
You can see in the line above the breaking line that a ContentPage defined using well-formed/valid Xaml was serialized as expected.
Please let me know if you have any questions around this and I will do my best to answer them.
Using XamlC with solve this. By having compile time info about your Xaml files.