Databases
StackOverflow2013
Postsdbo
POusing DataAnnotations to validate Model, not working
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POusing DataAnnotations to validate Model, not working
    primarykey
    data
    text
    <p>I have this code on an Entity created using EF 4:</p> <pre><code>[MetadataType(typeof(MemberMetaData))] public partial class Member { public string ConfirmPassword { get; set; } [PropertiesMustMatch("Password", "ConfirmPassword", ErrorMessage = "Password and confirm password do not match.")] public class MemberMetaData { [Required(ErrorMessage = "Email is required.")] [DataType(DataType.EmailAddress, ErrorMessage = "Email is invalid.")] //[RegularExpression(@"^([0-9a-zA-Z]([-.\w]*[0-9a-zA-Z])*@([0-9a-zA-Z][-\w]*[0-9a-zA-Z]\.)+[a-zA-Z]{2,9})$")] public object Email { get; set; } [Required] [DataType(DataType.Password)] [DisplayName("Password")] public object Password { get; set; } [Required] [DataType(DataType.Password)] [DisplayName("Confirm Password")] public object ConfirmPassword { get; set; } } } </code></pre> <p>Members properties in the Member entity are Email and Password so far.</p> <p>I'm trying to use the data annotations to return a validation message back to the view and have created a unit test like so:</p> <pre><code> [TestMethod] public void register_post_displays_error_when_email_not_entered() { // Arrange Member model = new Member() { Email = "", Password = "test123", ConfirmPassword = "test123" }; // Act var result = _controller.Register(model) as ViewResult; // Assert Assert.AreEqual("Email is required.", result.ViewData.ModelState["Email"].Errors[0].ErrorMessage); } </code></pre> <p>This is failing, when I step into the controller ModelState.IsValid is always true. Here's my controller action:</p> <pre><code> [HttpPost] public ActionResult Register(Member model) { if (ModelState.IsValid) { //register } // If we got this far, something failed, redisplay form return View("Register"); } </code></pre> <p>Why is this not working?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USlloydphillips
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POusing DataAnnotations to validate Model, not working
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POusing DataAnnotations to validate Model, not working
      1. USlucuma
      1. VTFavorite
    1. COJust an update the namespace on my partial class matches that of my entity.
      singulars
      1. POusing DataAnnotations to validate Model, not working
      1. USlloydphillips
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload