Bug 27690 - Visual Studio Extensions: Invalid File Allowed to Build
Summary: Visual Studio Extensions: Invalid File Allowed to Build
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.4.3
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-03-05 09:16 UTC by Michael
Modified: 2016-08-09 13:46 UTC (History)
8 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Michael 2015-03-05 09:16:50 UTC

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.

Thank you,
Comment 1 Rui Marinho 2016-08-09 13:46:54 UTC
Using XamlC with solve this. By having compile time info about your Xaml files.