CODEWITHSUNDEEP
c#asp.netvalidation
Félix LD
Félix LD

Reputation: 372

ASP validation client side

I've made a site web that's going to be only used by the company. I've done my validation only on server side and I tested for it to be safe. I did some meetings to teach the users how to use the site correctly. Plus, I have some ugly popups made with C# (for particular situations).

Now, I'm wondering if I should add some validation on client side?

Upvotes: 0

Views: 64

Answers (2)

Pradeep Kumar
Pradeep Kumar

Reputation: 6979

Ok, here are the answers to your questions to the best of my knowledge:

Now, I'm wondering if I should add some validation on client side?

Client side validation enhances the user experience and saves you a lot of round trips to the server. You should definately consider adding client side validation. However you should never trust what is comming to you from client side; server side validation is a must. You already have that; don't remove it.

Is it to late to add it?

No, it is never too late to correct your mistakes or make enhancements to your application.

In my case, what would be the advantages?

To name a few -- Better user experience, less load on server, a layer of added code security.

Does user should know how to use the site (instead of validation that would guide/help them)? Does client side validations can avoid me to teach to new users and to employees from other factories?

Yes, a good application should not require training to user, or only a minimal amount of training should be needed. The application itself should drive the user in right direction. Client side validations and functionality helps achieve this to a large extent.

Upvotes: 1

Pramod
Pramod

Reputation: 96

you should add client validations because it restricts multiple postback from server.

Upvotes: 1

Related Questions