Don't worry. Not everyone knows it...

Grabbed the award from Microsoft Technet. This time it's Silver medal :)

Generally, whenever something is to be saved to the database or to any other place, as a best practice almost everyone use to validate the state of the model. So, if state of model is valid, we proceed and if model state is invalid, we handle it as a bad request. This looks something like this: If(!ModelState.IsValid) { // create bad request object } So, all these were done by using the IsValid property. Problem Now what if we have to perform the same validation for all the models. Are we going to write the same validation in each and every controller? Of course, No. Solution Rather than duplicating the same code in each and every controller, we can create a global filter. This global filter has few methods, but for our purpose we can go with OnActionExecuting . public class ValidateModelStateFilter : ActionFilterAttribute { public override void OnActionExecuting(ActionExecutingContext context) { if (!context.ModelState.Is...

Another amazing news received this week. MVP award is in my hand for the 3rd time.

Once again grabbed the award from Microsoft Technet. This time it's Silver medal :)

Background When you are in between of writing your logic and by mistake you pressed F5, what will happen? Boom… you will lend up with below dialog due to compilation errors: Now think about it. If we are writing a code it means we need that to be executed whenever we are running the application. Isn’t it? It’s very-very rare case when someone still would like to execute previous logic. At least for me, I never ever want this to happen. Solution So, how to get rid of this rarely used prompt. There are two ways: First, Simply check the checkbox ‘ Do not show this dialog again’ . But for me, on one of my machines this checkbox has not even appeared. Hence, I opted for second option. Second, go to Tools >> Options… >> Projects and Solutions >> Build and Run. On right side panel, just change the value in dropdown displayed under ‘ On Run, when build or deployment errors occur: ’ to  ‘ Do not Launch ’  and we are done. ...

This article will walk you through the creation of ASP.NET Core application using ASP.NET Core 2.2 from scratch, by utilizing the capabilities of package manager, EF Core, Identity API, Razor Class Library, etc. So, rather than being more theoretical, this article will focus mainly on the implementation part. Wherever required, I’ll throw some light on the conceptual part too. To know more, you can either go here or here .

After publishing my previous article on ' Understanding concepts - OpenId, OAuth and SAML'  , I received a general question from a few of my colleagues and that is ‘Why OpenID arrived? What is the need of it’? By now, most of us are already aware that OAuth 2.0 is an authorization protocol and it really did a great job by providing information, which facilitated its user to take some prodigious authorization decisions. But what about exchanging this information? How to do that? Is that exchange done in a secure manner? Bla bla bla… All such sorts of questions are dealt in different- different manner as every authentication provider have their own mean of exchanging this OAuth information. As not all the providers have provided an equivalent level of security, led to some buzzes. Here OpenID Connect came for rescue. It fixes all the common problems by providing an authentication protocol with a standardized way of exchanging messages between a provider and subs...