Some enhancements and additions to DataAnnotations, incluiding implementation of a few missing pieces of Sys.ComponentModel.DataAnnotations v4.5, like:

[pruiz]

Some enhancements and additions to DataAnnotations, incluiding implementation of a few missing pieces of Sys.ComponentModel.DataAnnotations v4.5, like:
- CompareAttribute
- CreditCardAttribute
- EmailAddressAttribute
- FileExtensionsAttribute
- PhoneAttribute
- Implemented IsValid() methods of Min/MaxLengthAttribute.
- Fixed all existing Validation attributes so they take into account current's locale when composing ErrorMessage.

This code is provided under MIT/X11 license.

[marek-safar]

I am not sure what is the string.Format (CultureInfo.CurrentCulture change for.
Could you also use correct author for all your test files.

[pruiz]

Hi Marek,

When using error messages from localized resources, AFAIK the way to call string.Format() is passing the current cuture as IFormatProvider so it formats parameters acording to the currently defined locale. This way the format string's arguments are formated as expected (i.e. a DateTime value would be formated on the expected format). This is the way I am used to work with string.Format() when possibly passing it localized strings, and thought it was the standar way on .Net. However, I will revert the change if that's not acceptable by mono. ;)

Regarding the test files, I just forgot about it. I will submit a fix right now.

[alexrp]

By the way, for a change this large, you should state (in your pull request description) that the code is provided under the MIT/X11 license.

[pruiz]

Ouch, I forgot about the MIT/X11 comment, I've just updated the pull-request description stating the license.

[marek-safar]

DateTime or any other non-string value will be converted to string using ToString() operation which uses current-culture. Unless you need to overwrite this behaviour there is no need to pass CurrentCulture to string.Format

[pruiz]

Hi Marek,

I've just reverted this change. ;)