What is the difference between using asp.net vs jQuery validator validation elements to check front end

Could you tell me the difference between using asp.net vs jQuery validator validation elements to check front end? What happens if a user disables javascript in their browser?

Thanks..

+4
source share
3 answers

The difference is that the “front end” check itself has nothing to provide for security or a real check. This is a complete performance optimization — a client validation failure saves the circuit on your server, helps to scale, and reduces response time for your users. But the real verification work has to be done on the server side.

ASP.Net validation validation elements help automate server-side validation and synchronize it with the client, while jQuery still requires separate writing of the server logic.

+5
source

ASP.NET validators will also check the server. You can check the boolean to see if there were any violations. If JavaScript is disabled, jQuery will not do anything, but ASP.NET can still validate.

Of course, you can combine jquery with your own server-side validation, but it is not built-in.

+4
source

ASP.NET validation elements are much simpler for the average asp.net developer. I think using jquery is probably a lot of “cleaner” and more flexible.

+1
source

All Articles