Richard Bennett
A software developer in the payments and point-of-sale industry/// <reference path="./jquery-1.10.2-vsdoc.js" />
/// <reference path="./jquery-ui-1.10.3.js" />
/// <reference path="./jquery.jqGrid.src.js" />
window.jqGridSettings = {};
function bindConfiguration(key, options) {
var p = window.jqGridSettings[options.idPrefix];
if (p === null || p === undefined) {
// do init work here.
p = $ …As I’ve been deep-diving further into ASP.Net MVC 3, I ran into an issue where I needed to arbitrarily show an indicator against a label that would tell me which fields are required. We were initially doing this by hand, but have been using a ton of inheritance to set [Required] attributes on fields. In order to overcome this pain, we decided to create a helper method that we now use …
Just a note so mostly, I remember.
I’ve been working with Nick Riggs’ Foolproof validation in MVC3, trying to get more complex scenarios in place, and needed to write the client validation. He has a great post for MVC2 at http://www.nickriggs.com/posts/client-side-model-aware-validation/, but it doesn’t cover MVC3.
After some research, etc., here is what I came up with for …
So, another great quirk with ASP.NET MVC 3. When you implement a controller with two methods, one being for the initial load of the page, and the other being for the subsequent form post to process the data… if your intention is to re-render the page to do another ‘Add Item’ scenario, you must issue a ModelState.Clear(); command before you render the new view… otherwise, …
http://aspnet.codeplex.com/workitem/7629
Ack! Seems like this shouldn’t have happened.
To correct, you have to do the following:
Give your select list the “Required” attribute. Once the page loads, in jQuery, assign the data-val attribute and the data-val-message attributes.
Microsoft, this is not good!