Comments on: ASP.NET MVC Tip #3: Client-side form validation made easy – Part 1

By: Parminder

Parminder — Tue, 13 Apr 2010 13:40:26 +0000

Hi Adrian,

Thanks a lot for your help and support. As I was working on this project just for learning and not for doing any major development and not in the situation to hire you. But definately if I need your furthur help, I will hire you.

thanks again for the codes and the mails.

Regards
Parminder

By: Adrian Grigore

Adrian Grigore — Tue, 13 Apr 2010 11:16:03 +0000

@Parminder: I’m sorry, but my schedule does not permit debugging your project. The demo project provided with this article worked fine at the time I released it (namely with ASP.NET MVC which was still the standard then). I am using the same approach in my current project with ASP.NET MVC 2, so the basic principle shown here is still working. But unless you would like to hire me to help you, I’m afraid you will have to figure out the details yourself.

By: Parminder

Parminder — Tue, 13 Apr 2010 10:49:00 +0000

Hi Adrian,
I sent you and email with the test project. The project doesnt even compile. I also updated xVal version to the latest one. I was reading the RTM doc which say.

Changes in ASP.NET MVC 2 Beta
The IValueProvider interface replaces all uses of IDictionary
Every property or method argument that accepted IDictionary now accepts IValueProvider. This change affects only applications that include custom value providers or custom model binders.

This might be the reason.
Error 6 The type arguments for method ‘System.Linq.Enumerable.Count(System.Collections.Generic.IEnumerable)’ cannot be inferred from the usage. Try specifying the type arguments explicitly. D:\Development\SellYourOldBooks\source\SellYourOldBooksWeb\SellYourOldBooksWeb\Models\DataAnnotationsModelBinder\DataAnnotationsModelBinder.cs 73 41 SellYourOldBooksWeb

Thanks
Parminder

By: Adrian Grigore

Adrian Grigore — Tue, 13 Apr 2010 08:35:28 +0000

@Parminder: You might also have to remove the model binder with from the demo project so that the default model binder from MVC 2 becomes active. If that does not work, try updating the xVal version.

By: Parminder

Parminder — Tue, 13 Apr 2010 03:07:10 +0000

Hi Adrian,

It shows problem with the extension methods (DoesAnyKeyHavePrefix,FindKeysWithPrefix
here are the lines whre problem exists.

if (bindingContext.ValueProvider.DoesAnyKeyHavePrefix(fullPropertyKey))
var keys = bindingContext.ValueProvider.FindKeysWithPrefix(fullPropertyKey);
if (keys != null && keys.Count() > 0)
modelState = bindingContext.ModelState[keys.First().Key];

I updated your project to mvc2 and then even that was not working.
Your help will be appreciated.

Regards
Parminder

By: Adrian Grigore

Adrian Grigore — Mon, 12 Apr 2010 18:05:04 +0000

@Parminder: Basically it works fine with MVC2 (I’ve been using it that way for 2 months now), you just need to recompile the solution with the new system.web.mvc.dll.

By: Parminder

Parminder — Mon, 12 Apr 2010 17:52:00 +0000

Hi Adrian,

Nice work. I tried to use your code with asp.net mvc 2. But it doesnt work coz differnent version of system.web.mvc. Is there any fix for it.

Regards
Parminder

By: ASP.NET MVC Tip #4: Client-side form validation made easy – Part 2 | devermind.com

Mon, 11 Jan 2010 13:00:55 +0000

[...] my previous article about ASP.NET MVC Client-Side validation, I showed how to set up your project so that you [...]

By: Adrian Grigore

Adrian Grigore — Sat, 12 Dec 2009 09:29:32 +0000

@Olivier: Yes, that’s what I mean by entity-based validation. I am going to show this in the next article. I had planned to write this MUCH earlier, but lately I am very busy at work…

By: Olivier

Olivier — Fri, 11 Dec 2009 22:09:59 +0000

Hi Adrian,
it is a good one too . Did you manage to solve this issue: when a user change some of his information but not is email, the validation return an error because the email is already used (email value display on form = email stored in the repository). so basically if we take the assumption that the username cannot change once a user is created, any update operation could validate against it. So if a user update his profile, 2 pieces of information need to be sent over the server email + username when the email field validation occurs. So if the email value sent for uniqueness validation match the current username no error message should be triggered.