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.
There appears to be a discrepancy between how Xamarin.Forms Xaml treats ResourceDictionaries, and how WPF/Silverlight treats them.
Please see this line (WindowsPhone/Silverlight):
And this one:
You can see that both resources are defined the same way. However, in Xamarin.Forms, the property is serialized as a string and attempts to assign this to the Resources property, and throws an exception.
Launching the Windows Phone project will throw the exception here:
Please let me know if you have any questions around this, or if I can assist in any additional way.
In Xamarin.Forms, ContentPage.Resources is null by default, and you have to create the ResourceDictionary before being able to add items to it.
<x:String x:Key="KeyName">Hello World!</x:String>