Bug 12053 - Support for System.ComponentModel.DataAnnotations
Summary: Support for System.ComponentModel.DataAnnotations
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 4.8.x
Hardware: PC Windows
: Normal enhancement
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-05-01 09:01 UTC by Mike
Modified: 2017-07-06 16:11 UTC (History)
4 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 Mike 2013-05-01 09:01:39 UTC
Please add support for System.ComponentModel.DataAnnotations.

My models rely on datannotations for model validation and I'd like to share the same model classes with my xamarin mobile projects without having to go in and remove the annotations.
Comment 1 baramuse 2013-07-09 22:36:53 UTC
Upvote for this enhancement request ! 
I personally would need it for being able to compile ServiceStack.OrmLite.

Comment 2 Mike 2013-08-20 07:46:06 UTC
Hi, any movement on this bug request?  I think I saw something online that Miguel did for mono, is that applicable?

Comment 3 Cody Beyer (MSFT) 2017-07-06 16:11:12 UTC
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Android. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.