ASP.NET Core Blazor | How to create custom validation attribute

[@ashajyothi06]

Venkat you sounds awesome....happy to hear you🤩

[@tetley3737]

Another option for custom validation is to implement the IValidateObject interface on the model, but I think your implementation is a cleaner solution in most cases.

[@shaikmuzeeb6026]

Sir you are doing great job

[@VeereshPatel15]

Hi, if u dont mine please do videos on 1. Why / when/ what actually frontend/ backend devoloper need for software industry 2. What actually frontend developers do in realtime Scinorio Or when project assigned 3... Realtime frontend development tasks 4.. If project started what are the different tasks need to do--))by the frontend devoloper.. 5..Easy way to to crack any angular/ reactjs interviews with 3+ experience/10lack package ------) )) 6..Top 20 program's to cover entire angular / reactjs syllabus.----)) 7...Top 10 angular // reactjs concepts Please explain by taking one example/project 8...what type of skills (soft/technical)really need for industry 9... 4+ experience of frontend devoloper need to update what type of skills. ....

[@DaniLearnsIT]

I think I read in the Microsoft documentation that these are checked on the server, you know if there is a way to check them on the client side?

[@psadlkfpsk]

Can’t we use both this attribute and the existing [EmailAddress] attribute together, so that the latter handles all the default email validation logic (no spaces or special characters, one @ symbol, etc) and our attribute only handles validating the domain part of the email? I know it compiles fine since you used both in the video, but if it works like I want it to then I’m not sure why we had to include the logic for checking for an @ symbol inside our attribute, [EmailAddress] should already be handling this. Sorry for the wall of text, thanks in advance.