var val = $.global.parseFloat(value);

should be

var val = Globalize.parseFloat(value);

You said that validation rules can be added in the Model classes and they will be activated whenever the Model is updated or created wherever necessary. But Can i configure the model class to enforce validation rules only certain times and not all the times based on some conditions. If so, how can we configure these things.

I still have an issue. I'm french so I appreciated the dot vs comma distinction using Globalize fwk.

With [DataType(DataType.Date)] attribute within the ReleaseDate property of Movie model, it works fine with IE, but not at all with Chrome, it looks like I need to use yyyy-mm-dd format, but I want the same format dd/mm/yyy for both Index and Edit pages and for both IE and Chrome browsers.

Any idea for this ?

Regards

Generally no. See msdn.microsoft.com/

This article [updates.html5rocks.com/] by Kent Tamura (a Chrome software engineer) says the value attribute of a date field should be assigned as yyyy-mm-dd regardless of locale. Using VS2012 Express the value is being rendered as mm/dd/yyyy (en-US)

Is there a work-around?

[Range(1, 100, ErrorMessage="Price must be between $1 and $100")]

Instead i've been trying to find out why I don't get the price range error along with the $ currency in the digits end.

You might want to fix that in the tutorial, And thank you very much for the whole project.

If you load the page in chrome you will get forced datepicker that won't load edited date values etc.

When you enter invalid date like 1/1/1350 it will still pass the validation check and an out-of-range error will be thrown.

simply amazing! I really am so excited about these new cocepts, they are totally new to me, the DRY, and having validations taken care of by simply working it out in one place such as the Class Movie (the Model).

When I reached the part where you were explaing the string validation for the date and currency, I immediatly started thinking of regular expressions, now I see that we can as well benifit from the regular expressions (those have been very important to me validating prerior to form postback), of course that is in the case the scripts not disabled in the browser! (Thanks for the snapshots Rick, good to know that I could disable those scripts. :-)

Thanks once again & good luck to all the folks!

~Salman~

Hi Jeff, I had similar error too, but then I realized that I forgot to specify values for the "Rating" in the Seed method in my Configuration.cs, and since I added the "[Required]" attribute for my "rating" field in my Movie Class, then this gets reflected in my Data Table having the column "Rating" Not Null (so it has to have a value).

so what I did, is closed the connection (from Database Explorer), then Deleted the localDB, then went back to the Solution Explorer and Deleted the mdf file from the App_Data, rebuild everything, (of course prior to all that, I updated my Configuration.cs so that my "Rating" field has a value), after all that, I executed the "update-database" from the library package console! Plus all that, I applied the updates in both the Create, and Edit Views so to include the "Rating" label and editor fields.

right, I hope I haven't missed anything. But that what i did, Jeff, Give it a try.

Thanks again folks and Rick!

~Salman~

Hi Joe!

Yes, I just tried what you were pinpointing and very true, I didn't know that, waw! so Chrome renders the page differently than Internet Explorer 9 does. Very interesting to know. Thanks Joe!

so this is another issue I need to look at when developing an application with client side scripting involved, got to make sure it works in chrom too!

thanks joe and everyone!

~Salman~

[Range(typeof(DateTime), "1/1/2010", "1/1/2020")]

public DateTime ReleaseDate{ get; set; }

It turns out that the client side validation using jQuery always fails with a message saying the date must be between "1/1/2010" and "1/1/2020", no matter what I type into the date field, while the server side validation always works (passes if I pass in a valid date string, otherwise fails). Do you see this behavior?

How to solve it?Thanks!

Is there anybody having the same problem?

Thank you all.

You have =>"We will us migrations to update the scheam."

Should be => "We will use migrations to update the schema."

Great tutorial btw.