Calling out excellence in blog posts
-
I'm currently working on code that will ultimately end up as an article about using and administering Keycloak in .net core. I'm a big fan of Keycloak and find it a lot friendlier than Identity Server. Now, one of the things I wanted to do is use the Options pattern for configuring the Keycloak connection settings, and using DataAnnotations to support a better developer experience for using the code. The problem is, the settings I am using are complex objects, and using them as options becomes less than optimal because .NET Core options only support simple objects by default. I spent some time digging around this and then happened across this[^] blog post, and I have to say that it solves the problem perfectly. We don't often take the opportunity to share things that we find useful, so I just thought I'd share this one. It was well researched, well written, and solves the problem perfectly.
-
I'm currently working on code that will ultimately end up as an article about using and administering Keycloak in .net core. I'm a big fan of Keycloak and find it a lot friendlier than Identity Server. Now, one of the things I wanted to do is use the Options pattern for configuring the Keycloak connection settings, and using DataAnnotations to support a better developer experience for using the code. The problem is, the settings I am using are complex objects, and using them as options becomes less than optimal because .NET Core options only support simple objects by default. I spent some time digging around this and then happened across this[^] blog post, and I have to say that it solves the problem perfectly. We don't often take the opportunity to share things that we find useful, so I just thought I'd share this one. It was well researched, well written, and solves the problem perfectly.
Andrew Lock also has a few excellent posts on this topic. :) Adding validation to strongly typed configuration objects in ASP.NET Core[^] Adding validation to strongly typed configuration objects in .NET 6[^] Adding validation to strongly typed configuration objects using FluentValidation[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
I'm currently working on code that will ultimately end up as an article about using and administering Keycloak in .net core. I'm a big fan of Keycloak and find it a lot friendlier than Identity Server. Now, one of the things I wanted to do is use the Options pattern for configuring the Keycloak connection settings, and using DataAnnotations to support a better developer experience for using the code. The problem is, the settings I am using are complex objects, and using them as options becomes less than optimal because .NET Core options only support simple objects by default. I spent some time digging around this and then happened across this[^] blog post, and I have to say that it solves the problem perfectly. We don't often take the opportunity to share things that we find useful, so I just thought I'd share this one. It was well researched, well written, and solves the problem perfectly.
We use complex object with IOptions all the time.
"Time flies like an arrow. Fruit flies like a banana."
-
I'm currently working on code that will ultimately end up as an article about using and administering Keycloak in .net core. I'm a big fan of Keycloak and find it a lot friendlier than Identity Server. Now, one of the things I wanted to do is use the Options pattern for configuring the Keycloak connection settings, and using DataAnnotations to support a better developer experience for using the code. The problem is, the settings I am using are complex objects, and using them as options becomes less than optimal because .NET Core options only support simple objects by default. I spent some time digging around this and then happened across this[^] blog post, and I have to say that it solves the problem perfectly. We don't often take the opportunity to share things that we find useful, so I just thought I'd share this one. It was well researched, well written, and solves the problem perfectly.
-
I'm currently working on code that will ultimately end up as an article about using and administering Keycloak in .net core. I'm a big fan of Keycloak and find it a lot friendlier than Identity Server. Now, one of the things I wanted to do is use the Options pattern for configuring the Keycloak connection settings, and using DataAnnotations to support a better developer experience for using the code. The problem is, the settings I am using are complex objects, and using them as options becomes less than optimal because .NET Core options only support simple objects by default. I spent some time digging around this and then happened across this[^] blog post, and I have to say that it solves the problem perfectly. We don't often take the opportunity to share things that we find useful, so I just thought I'd share this one. It was well researched, well written, and solves the problem perfectly.
Right on man. For the JavaScript ecosystem, I don't normally get caught up in the having a PhD hoopla, but this dude does know what he's talking about. [2ality – JavaScript and more](https://2ality.com/)
Jeremy Falcon
-
I'm currently working on code that will ultimately end up as an article about using and administering Keycloak in .net core. I'm a big fan of Keycloak and find it a lot friendlier than Identity Server. Now, one of the things I wanted to do is use the Options pattern for configuring the Keycloak connection settings, and using DataAnnotations to support a better developer experience for using the code. The problem is, the settings I am using are complex objects, and using them as options becomes less than optimal because .NET Core options only support simple objects by default. I spent some time digging around this and then happened across this[^] blog post, and I have to say that it solves the problem perfectly. We don't often take the opportunity to share things that we find useful, so I just thought I'd share this one. It was well researched, well written, and solves the problem perfectly.
Pete O'Hanlon wrote:
We don't often take the opportunity to share things that we find useful,...
Because I am an optimist. I presume that many people find many things useful all the time. And only sometimes do some people find stuff that is not useful. Thus that is what should be reported on.
-
Right on man. For the JavaScript ecosystem, I don't normally get caught up in the having a PhD hoopla, but this dude does know what he's talking about. [2ality – JavaScript and more](https://2ality.com/)
Jeremy Falcon
Very nice.
-
Great ... hearing "Keycloak" and .NetCore or .Net6 I am all ears, as I got a bit discouraged by Keycloak configuration in my pet project/tryouts a few months ago.
Well, when the code is written, I will write the article with details about Keycloak configuration and how it maps back into the application.
