data-annotations

I have something like this: [DisplayName("First Name")] [Required(ErrorMessage="{0} is required.")] [StringLength(50, MinimumLength = 10, ErrorMessage="{0}'s length should be between {2} and {1}.")] public string Name { get; set; } I want to have the following output: First Name is required. First Name's length should be between 10 and 50. It is working when using ASP.NET MVC2 Error Summary , but when I try to validate it manually, like this: ValidationContext context = new ValidationContext(myModel, null, null); List<ValidationResult> results = new List<ValidationResult>(); bool valid =

In the world of MVC I have this view model... public class MyViewModel{ [Required] public string FirstName{ get; set; } } ...and this sort of thing in my view... <%= Html.ValidationSummary("Please correct the errors and try again.") %> <%= Html.TextBox("FirstName") %> <%= Html.ValidationMessage("FirstName", "*") %> My question: If I submit this form without supplying a name, I get the following message "The FirstName field is required" OK. So, I go and change my property to... [DisplayName("First Name")] [Required] public string FirstName{ get; set; } ..and now get "The First Name field is

I thought this would be a quick search on google but maybe I'm missing something. Is there a way, using Data Annotations, to set a ViewModel property to create a HiddenInput when the markup get rendered? The only annotations I've found were to hide the property from the view entirely, I still want the property rendered but as a hidden input. This property: [System.Web.Mvc.HiddenInput(DisplayValue = false)] public int Id { get; set; } will be rendered as i.e. <input id="Id" name="Id" type="hidden" value="21" /> when using Html.EditorForModel() or Html.EditorFor(m => m.Id) 来源： https:/

I'm using the Data Annotation validation extensively in ASP.NET MVC 2. This new feature has been a huge time saver, as I'm now able to define both client-side validation and server-side validation in one place. However, while I was doing some detailed testing, I realized that it's quite easy for someone to bypass the server-side validation if I relied on Data Annotation validation alone. For example, if I defined a required field by annotating the property with the [Required] attribute and placed a textbox for that required field in a form, a user could simply remove the textbox from the DOM

I have a class like this: public class Document { public int DocumentType{get;set;} [Required] public string Name{get;set;} [Required] public string Name2{get;set;} } Now if I put a [Required] data annotation on the Name and Name2 properties, then everything is ok and if Name or Name2 are empty, validation will throw an error. But I want Name field only to be required if DocumentType is equal to 1 and Name2 only required if DocumentType is equal to 2 . public class Document { public int DocumentType{get;set;} [Required(Expression<Func<object, bool>>)] public string Name{get;set;} [Required

I have developed a custom validator Attribute class for checking Integer values in my model classes. But the problem is this class is not working. I have debugged my code but the breakpoint is not hit during debugging the code. Here is my code: public class ValidateIntegerValueAttribute : ValidationAttribute { protected override ValidationResult IsValid(object value, ValidationContext validationContext) { if (value != null) { int output; var isInteger = int.TryParse(value.ToString(), out output); if (!isInteger) { return new ValidationResult("Must be a Integer number"); } } return

I have created a custom validation attribute by subclassing ValidationAttribute. The attribute is applied to my viewmodel at the class level as it needs to validate more than one property. I am overriding protected override ValidationResult IsValid(object value, ValidationContext validationContext) and returning: new ValidationResult("Always Fail", new List<string> { "DateOfBirth" }); in all cases where DateOfBirth is one of the properties on my view model. When I run my application, I can see this getting hit. ModelState.IsValid is set to false correctly but when I inspect the ModelState