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.
Generated partial classes can trigger FxCop warnings; for example, if you reference an element in a constraint expression but don't otherwise reference that element in your codebehind, you will trigger CA1823, avoid unused private fields. Generated files should be marked with the GeneratedCode attribute so FxCop can easily be told to ignore those files when doing analysis.
I'm working around it right now with a bash script that executes whenever I build, and fixes the import statement; but it kind of sucks, especially seeing as the only way I can get Xamarin to run it, is in an external window, so I need to close a terminal window on each build... hmmph
resolved it - by using a custom namespace.
xmlns:page="clr-namespace:TwinEvents.Core.App.View ; assembly=TwinEvents"
please ignore this issue - perhaps it might help others if they find the ticket though :)
oh.. how very embarrasing. sorry people - comment 1 and 2 were intended for a completely different bug!!
the shame!! sorry sorry!
Marking the type with GeneratedCodeAttribute is incorrect for a partial class: http://blogs.msdn.com/b/codeanalysis/archive/2007/04/27/correct-usage-of-the-compilergeneratedattribute-and-the-generatedcodeattribute.aspx
Generated fields and methods should be attributed instead.
Should be fixed in the next release.