data-annotations

I've got a view model like this: public class SignUpViewModel { [Required(ErrorMessage = "Bitte lesen und akzeptieren Sie die AGB.")] [DisplayName("Ich habe die AGB gelesen und akzeptiere diese.")] public bool AgreesWithTerms { get; set; } } The view markup code: <%= Html.CheckBoxFor(m => m.AgreesWithTerms) %> <%= Html.LabelFor(m => m.AgreesWithTerms)%> The result: No validation is executed. That's okay so far because bool is a value type and never null. But even if I make AgreesWithTerms nullable it won't work because the compiler shouts "Templates can be used only with field access, property

I have the following code in my Model class: [Range(1, 100)] public decimal Price { get; set; } After recent upgrade (I assume) of jquery.validate to 1.11.0, I am getting an error even if I enter valid value. If I turn off client validation in web.config - works fine. All other attributes (StringLength, Required) work fine. Generated HTML is the following (line breaks added for clarity): <input class="text-box single-line" data-val="true" data-val-number="The field Price must be a number." data-val-range="The field Price must be between 1 and 100." data-val-range-max="100" data-val-range-min=

What is the opposite/negate of [Compare(" ")] data annotation" in ASP.NET? i.e: two properties must hold different values. public string UserName { get; set; } [Something["UserName"]] public string Password { get; set; } Leniel Maccaferri You can use the [NotEqualTo] data annotation operator included in MVC Foolproof Validation . I used it right now and it works great! MVC Foolproof is an open source library created by @nick-riggs and has a lot of available validators. Besides doing server side validation it also does client side unobtrusive validation. Full list of built in validators you get

As far as I know the System.ComponentModel.DataAnnotations.DataTypeAttribute not works in model validation in MVC v1. For example, public class Model { [DataType("EmailAddress")] public string Email {get; set;} } In the codes above, the Email property will not be validated in MVC v1. Is it working in MVC v2? LukLed [DataType("EmailAddress")] doesn't influence validation by default. This is IsValid method of this attribute (from reflector): public override bool IsValid(object value) { return true; } This is example of custom DataTypeAttribute to validate Emails (taken from this site http:/

How would I go about writing a custom ValidationAttribute that compares two fields? This is the common "enter password", "confirm password" scenario. I need to be sure the two fields are equal and to keep things consistent, I want to implement the validation via DataAnnotations. So in pseudo-code, I'm looking for a way to implement something like the following: public class SignUpModel { [Required] [Display(Name = "Password")] public string Password { get; set; } [Required] [Display(Name = "Re-type Password")] [Compare(CompareField = Password, ErrorMessage = "Passwords do not match")] public

Can you use Data Annotations / Validation with an AJAX / jQuery call? If so, please provide an example or a post which shows an example. Basically I have seen an example of how to use Data Annotations, however it was with a full post back. Is there a way to do with an AJAX / jQuery call? Not sure how you would do this since I am not sure how you would construct the Model object on the client side. (I assume this is what you would have to do.) Someone told me this can be done, but I just don't understand how it can be. Thanks for your help. If you use Html.AjaxForm (instead of Html.BeginForm)

I've a ViewModel which has some DataAnnotations validations and then for more complex validations implements IValidatableObject and uses Validate method. The behavior I was expecting was this one : first all the DataAnnotations and then, only if there were no errors, the Validate method. How ever I find out that this isn't always true. My ViewModel (a demo one) has three fileds one string , one decimal and one decimal? . All the three properties have only Required attribute. For the string and the decimal? the behavior is the expected one, but for the decimal , when empty, Required validation