You can disable this implicit validation by setting the [`AddImplicitRequiredAttributeForValueTypes`][1] option on the [`DataAnnotationsModelValidatorProvider`][2] by adding the following to your `Application_Start`:
  


    DataAnnotationsModelValidatorProvider.AddImplicitRequiredAttributeForValueTypes = false;

**Further Reading**:

* [Unrequired property keeps getting data-val-required attribute][3]
* [ASP.NET MVC optional field being treated as required][4]
* [Why MVC Model Binder set required for int, long values?][5]






[1]:https://msdn.microsoft.com/en-us/library/system.web.mvc.DataAnnotationsModelValidatorProvider.AddImplicitRequiredAttributeForValueTypes
[2]:https://msdn.microsoft.com/en-us/library/system.web.mvc.DataAnnotationsModelValidatorProvider
[3]: https://stackoverflow.com/q/4700172/1366033
[4]: https://stackoverflow.com/q/13293207/1366033
[5]: https://stackoverflow.com/q/17143001/1366033

This is happening when I try to create the entity using a Create style action in Asp.Net MVC 2.


The POCO has the following properties:

    public int Id {get;set;}

    [Required]
    public string Message {get; set}

On the creation of the entity, the Id is set automatically, so there is no need for it on the Create action.

The ModelState says that "The Id field is required", but I haven't set that to be so. 
Is there something automatic going on here?

**EDIT - Reason Revealed**

The reason for the issue is answered by Brad Wilson via Paul Speranza in one of the comments below where he says (cheers Paul): 

> You're providing a value for
> ID, you just didn't know you were.
> It's in the route data of the default
> route ("{controller}/{action}/{id}"),
> and its default value is the empty
> string, which isn't valid for an int.
> Use the [Bind] attribute on your
> action parameter to exclude ID. My
> default route was: new { controller =
> "Customer", action = "Edit", id = " "
> } // Parameter defaults

**EDIT - Update Model technique**

I actually changed the way I did this again by using TryUpdateModel and the exclude parameter array asscoiated with that. 

        [HttpPost]
        public ActionResult Add(Venue collection)
        {
            Venue venue = new Venue();
            if (TryUpdateModel(venue, null, null, new[] { "Id" }))
            {
                _service.Add(venue);
                return RedirectToAction("Index", "Manage");
            }
            return View(collection);
        }


"The Id field is required" validation message on Create; Id not set to [Required]

To expand on the link to [Scott Guthrie's article][5], starting with MVC 3, you can perform class level validation by implementing the [`IValidatableObject`][1] Interface.  

This will work inside the context of the current validation pipeline so it can be nested on as many custom classes and properties as you like and continue to return the full array of possible error messages.

For your class, ditch the class level attributes, and add a method called `Validate` like this:

    public class EditSiteUser : IValidatableObject
    {
        public int UserId { get; set; }

        [Required(ErrorMessage = "Du skal indtaste et brugernavn")]
        public string Username { get; set; }
    
        [Required(ErrorMessage = "Du skal indtaste en adgangskode")]
        public string Password { get; set; }

        [Required(ErrorMessage="Du skal bekræfte adgangskode")]
        public string PasswordConfirm { get; set; }
    
        [Required(ErrorMessage = "Du skal indtaste en e-mailadresse")]
        [Email(ErrorMessage = "Ugyldig e-mailadresse")]
        public string Email { get; set; }

        [Required(ErrorMessage="Du skal bekræfte e-mailadressen")]
        [Email(ErrorMessage="Ugyldig e-mailadresse")]
        public string EmailConfirm { get; set; }

    
        public IEnumerable<ValidationResult> Validate(ValidationContext validationContext)
        { 
          // put whatever class level validation you want here

          if (Email !== EmailConfirm)
          {
              yield return new ValidationResult("E-mailadresserne skal være ens", new[] {"EmailConfirm"})
          }

          if (Password !== PasswordConfirm)
          {
              yield return new ValidationResult("Adgangskoderne skal være ens", new[] {"PasswordConfirm"})
          }
        }

    }


You can continue to `yield return` as many validation messages as you'd like.

And you can display them all on the client with [`@Html.ValidationSummary`][3]

If you'd like the message to appear alongside a particular control, the [`ValidationResult`][2] constructor takes an overload with the `memberNames` of the affected properties, and you can provide the validation message for that particular property with the [`ValidationMessageFor`][4] HTML helper like this:

    @Html.ValidationMessageFor(Function(model) model.TestOne )

----

Also, it's worth mentioning that you can use the [**`CompareValidator`**][7] to easily ensure the values of two different properties are equal.  The upside to using this annotation is that it automatically knows how to enforce this on the client as well as the server, whereas adding `IValidatableObject` will only run on the server.

    [DataType(DataType.Password)]
    public string Password { get; set; }
 
    [Compare("Password")]
    [DataType(DataType.Password)]
    public string ConfirmPassword { get; set; }

---

For further reading, Scott Guthrie another post with more detail on [class level validation][6].

 
[1]: https://msdn.microsoft.com/en-us/library/system.componentmodel.dataannotations.ivalidatableobject%28v=vs.110%29.aspx
[2]: https://msdn.microsoft.com/en-us/library/dd411880(v=vs.110).aspx
[3]: https://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.validationsummary%28v=vs.110%29.aspx
[4]: https://msdn.microsoft.com/en-us/library/system.web.mvc.html.validationextensions.validationmessagefor%28v=vs.118%29.aspx
[5]: http://weblogs.asp.net/scottgu/introducing-asp-net-mvc-3-preview-1
[6]: http://weblogs.asp.net/scottgu/class-level-model-validation-with-ef-code-first-and-asp-net-mvc-3
[7]: https://msdn.microsoft.com/en-us/library/system.web.ui.webcontrols.comparevalidator(v=vs.110).aspx

**Update after Bounty was awarded**

A new solution is coming up to this problem. Please refer to ASP.NET MVC 3 Preview 1 here: http://weblogs.asp.net/scottgu/archive/2010/07/27/introducing-asp-net-mvc-3-preview-1.aspx

Look in the section **Model Validation Improvements**, where you will see the solution to my problem.


----------

**Original Post**

Referring to my earlier post https://stackoverflow.com/questions/2450198/how-to-validate-two-properties-with-asp-net-mvc-2 where I asked how I could compare two properties for Model validation.

I did find the answer useful, but I was left with an entirely different problem:

**Problem**: If a Property-level ValidationAttribute contains an error, then the Class-level ValidationAttributes are NOT validated.

Please consider the following:

    [EqualTo("Email", "EmailConfirm", ErrorMessage = "E-mailadresserne skal være ens")]
    [EqualTo("Password", "PasswordConfirm", ErrorMessage = "Adgangskoderne skal være ens")]
    [Bind(Exclude="UserId")]
    public class EditSiteUser
    {
        [Required(ErrorMessage="Du skal bekræfte adgangskode")]
        public string PasswordConfirm { get; set; }

        [Required(ErrorMessage="Du skal bekræfte e-mailadressen")]
        [Email(ErrorMessage="Ugyldig e-mailadresse")]
        public string EmailConfirm { get; set; }
        public int UserId { get; set; }

        [Required(ErrorMessage = "Du skal indtaste et brugernavn")]
        public string Username { get; set; }

        [Required(ErrorMessage = "Du skal indtaste en adgangskode")]
        public string Password { get; set; }

        [Required(ErrorMessage = "Du skal indtaste en e-mailadresse")]
        [Email(ErrorMessage = "Ugyldig e-mailadresse")]
        public string Email { get; set; }
    }

Here I have two Class-level attibutes that validate EmailConfirm and PasswordConfirm.

If a field like Username is empty, and thus yields an error, then the two EqualTo Attributes are never validated.

Does anyone have a suggestion to overcome this problem?

EDIT: If you need anymore information about this problem, please ask in comments and I will be very happy to give you any additional information you need.

Questions:
-------------------
Q: "Why is it important that the class-level checks get validated if a property-level check fails?".

A: "Because this is part of a form, where a user enters information into a form that posts back via AJAX. When the form returns it should show all current problems."

Q: "What exactly is the EqualTo attribute you have placed on the class? Is it a custom validation attribute? If so, how does it work? what does it do?"

A: EqualTo is a class-level ValidationAttribute that compares the value of two Properties of the class-instance. Look up "PropertiesMustMatchAttribute" for a similar implementation.

Property-level validation errors hinder the validation of Class-level validation

Just to put the answer in the answer section for clarity...

You'll need to add `Area` to the `RouteValues` anytime you use `UrlHelper.Action` to generate a link path.  

If you're in the Controller, you can [stub a UrlHelper][1] like this:



    var httpContext = new HttpContextWrapper(System.Web.HttpContext.Current);
    var requestContext = new RequestContext(httpContext, new RouteData());
    var urlHelper = new UrlHelper(requestContext);

You can always [get the current area][2] like this:



    HttpContext.Current.Request.RequestContext.RouteData.DataTokens["area"]

Finally, when using `UrlHelper` [pass the area in the RouteValues object][3] like this:



    var url = urlHelper.Action("Index", "Home", new { area = "Pages" }));


[1]: https://stackoverflow.com/a/8331086/1366033
[2]: https://stackoverflow.com/q/2723689/1366033
[3]: https://stackoverflow.com/a/8385136/1366033

**UPDATE 2**

Ok - So it looks like my question is changing again slightly :-)

I've realised now that UrlHelper.Action doesn't seem to correctly resolve the URL in any Area unless the area name is explicitly specified. If it's not specified it seems to return whatever area name we're currently in which makes it look like it's working from one part of the site but then the same link in another area resolves to the wrong Area name.

Either I've done something funky to make it do this or I'm not quite understanding how this Action method is meant to work.

**UPDATE 1**

I can make this work by doing the following:

    return helper.Action("add", "product",new {area = "storemanagement"});

which changes my question slightly.

How come the MVC routing doesn't disambiguate the controllers with the same name and resolve to the one with the action method specified?

**Origional post**

Hey everyone,

I've created a helper method on the UrlHelper class and am having a small problem with one of the routes.

Here's the code for the helper method in question:

    public static string AddProduct(this UrlHelper helper)
            {
                return helper.Action("add", "product");
            }

I basically have two controllers named "product" which are in different areas of the site. One of them in used for browsing of products and the other for management of products. Only one of the product controllers contains an action method "Add".

When I output the value of AddProduct

    <%: Url.AddProduct() %>
The area name is resolved to the current area I'm browsing and not the correct area for the product controller containing the Add action method.

Is there something I need to set up in the routes? I'm not exactly sure how the routing works with UrlHelper.Action so I dunno if it's possible to do what I'm trying.

Cheers for any help.

UrlHelper.Action doesn't map to the area that the controller is in correctly

One possible issue is that jQuery Validate does [run any rules if the value of an element is empty][1]. 

You can get around this by [retriggering the validation][2] when the user loses focus:



    // select statements not firing null validation automatically
    $("select").blur(function () { $(this).valid() });

[1]: https://stackoverflow.com/a/14759805/1366033
[2]: https://stackoverflow.com/a/12195091/1366033

My view model defines property which has to be displayed as combo box. Property definition is:

    [Required]
    public int Processor { get; set; }

I'm using `DropDownListFor` to render combo box:

    <%=Html.DropDownListFor(r => r.Processor, Model.Processors, Model.Processor)%>

`Model.Processors` contains `IEnumerable<SelectListItem>` with one special item defined as:

    var noSelection = new SelectListItem
      {
        Text = String.Empty,
        Value = "0"
      };

Now I need to add validation to my combo box so that user must select different value then 'noSelection'. I hoped for some configuration of `RequiredAttribute` but it doesn't have default value setting.

Validating required selection in DropDownList

Here are a couple solutions.  Number two is much better as it doesn't require needlessly duplicating your assemblies.

### Solution 1 <sup>(okay)</sup>

As added to the question itself and described in the post [Visual Studio 2010 Report Viewer - Object Datasource][1], just create a separate library for the project and add the rdlc file there.  This appears to be a bug with the MVC Web Application project type itself so any other project type (like a Class Library) should work.  The data source configuration wizard should now look like this:

![data source configuration wizard][3]

### Solution 2 <sup>(better)</sup>

As figured out in [Can't see or add Website Data Sources in RDLC report in ASP.NET MVC][2], you can just add an **.aspx** page anywhere to the MVC project in order to trick Visual Studio into pulling in the right design time libraries. 

Just do the following:

* Close all windows
* Clean & Rebuild Solution
* Add WebForm1.aspx to the Project
* Open up the RDLC file and choose a DataSource from the dropdown:

  ![DataSource Dropdown][4]


[1]: http://wraithnath.blogspot.com/2011/02/visual-studio-2010-report-viewer-object.html
[2]: https://stackoverflow.com/q/2923569/1366033
[3]: http://i.imgur.com/n44iRKu.png
[4]: http://i.imgur.com/qGkHTNu.png

I've created more projects using ReportViewer 2005 and 2008 in local processing mode than I can count on my hands. All Visual Studio 2005 or 2008 ASP.NET web forms projects. I always used some flavor of Object data source for the reports.

Tonight, I attempted to add the same functionality to a Visual Studio 2010 MVC 2 project and am failing miserably. First, the Add New Item > Reporting > Report is now a 2008 RDLC and not a 2005 RDLC report. Secondly, when trying to add a DataSet, my usual method of create a data proxy class with static methods that return `IEnumerables(Of Stuff)` will not show up as sources in the DataSources drop down

![Empty Data Source][1]

Thirdly, my *only* option is to add a Database connection. There is no "Object Data Source" to pick from:

![Database connections only][2]

I'm stumped. Like I kind of alluded to, I have no problems whatsoever actually rendering a report using the ReportViewer control. What I can't do is figure out how set up a Data Source in these new-fangled 2008 reports with Visual Studio 2010 so that I can pump a list of domain objects into the ReportViewer and display the report.

**UPDATE**

With some more research, I've found that MVC projects do not allow object data sources to be used within them. One solution for my issue is to create a separate project in the solution -- a web application, a service, or even just a class library, to add the report to and design it accordingly.

I'm still looking for alternatives here.

  [1]: https://i.stack.imgur.com/0fLnN.png
  [2]: https://i.stack.imgur.com/7cptm.png

Visual Studio 2010 Local SSRS Report (.rdlc) with Object Data Source

You can set the timeout in [`sessionState`][1] in the `web.config`:



    <system.web>
        <sessionState mode="InProc" timeout="30"  />
    </system.web>

But changes to this value will also get deployed with your application.  Another option would be to use a [conditional compilation preprocessor directive][2] and override the session timeout on session start in `global.asax`:



    void Session_onStart(object sender, EventArgs e)
    {
        #if DEBUG
            Session.Timeout = 6 * 60; // 6 hours
        #endif
    }


[1]: https://msdn.microsoft.com/en-us/library/system.web.sessionstate.httpsessionstate.timeout.aspx
[2]: https://msdn.microsoft.com/en-us/library/4y6tbswk.aspx

Does the visual studio development server have an equivalent IIS app pool idle timeout setting? If so, how do I change it? I'm having trouble keeping my user's session open while running in a development environment and wonder if this could be the problem.