#fluentvalidation — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #fluentvalidation, aggregated by home.social.
-
Clean Architecture Project Setup From Scratch With .NET 10
Building a clean, scalable application starts with a Clean Architecture!
In this tutorial, I ditch boilerplate templates and set up the full Clean Architecture structure from a blank solution, tailored for modern .NET 10 development.
https://www.youtube.com/watch?v=0phlmiI-1Kk
#CleanArchitecture #DotNet10 #ProjectStructure #ASPNETCore #SoftwareArchitecture #DotNetTutorial #CodingFromScratch #Mediator #FluentValidation
-
Dew Drop – September 29, 2025 (#4507)
https://fed.brid.gy/r/https://alvinashcraft.com/2025/09/29/dew-drop-september-29-2025-4507/
-
Still thinking about upgrading your skills to #aspnetcore. My newly updated Pluralsight course covers #dotnet8, Razor Pages, #rest APIs, #minimalApis, #fluentvalidation, #entityframework, and #vue! Watch it here:
-
Still thinking about upgrading your skills to #aspnetcore. My newly updated Pluralsight course covers #dotnet8, Razor Pages, #rest APIs, #minimalApis, #fluentvalidation, #entityframework, and #vue! Watch it here:
-
Still thinking about upgrading your skills to #aspnetcore. My newly updated Pluralsight course covers #dotnet8, Razor Pages, #rest APIs, #minimalApis, #fluentvalidation, #entityframework, and #vue! Watch it here:
-
Still thinking about upgrading your skills to #aspnetcore. My newly updated Pluralsight course covers #dotnet8, Razor Pages, #rest APIs, #minimalApis, #fluentvalidation, #entityframework, and #vue! Watch it here:
-
Still thinking about upgrading your skills to #aspnetcore. My newly updated Pluralsight course covers #dotnet8, Razor Pages, #rest APIs, #minimalApis, #fluentvalidation, #entityframework, and #vue! Watch it here:
-
Валидация входных данных в фильтрах Minimal API .NET, просто и без затей
В последние год-два снова набирает силу тенденция обращать самое пристальное внимание на производительность разрабатываемых приложений. Тема на самом деле непростая, поскольку производительность не на пустом месте появляется и требует значительных временных ресурсов и квалификации специалистов. В данной статье обсуждается эффективный способ валидации данных для .NET . Если C# входит в круг ваших интересов, если ваши коллеги обсуждают за кофе Minimal API , эта статья определённо для вас.
https://habr.com/ru/articles/791466/
#validation #FlatValidator #MiniValidation #FluentValidation #проверка_данных #валидация_данных #валидатор #валидация_форм
-
Валидация входных данных в фильтрах Minimal API .NET, просто и без затей
В последние год-два снова набирает силу тенденция обращать самое пристальное внимание на производительность разрабатываемых приложений. Тема на самом деле непростая, поскольку производительность не на пустом месте появляется и требует значительных временных ресурсов и квалификации специалистов. В данной статье обсуждается эффективный способ валидации данных для .NET . Если C# входит в круг ваших интересов, если ваши коллеги обсуждают за кофе Minimal API , эта статья определённо для вас.
https://habr.com/ru/articles/791466/
#validation #FlatValidator #MiniValidation #FluentValidation #проверка_данных #валидация_данных #валидатор #валидация_форм
-
.NET folks, don't miss J. Tower's two #techbash sessions this fall!
Join us at Kalahari Resort in the #poconos Nov 7-10. Learn more: https://techbash.com
#dotnet #dotnetcli #developers #fluentvalidation #techevent #devconference #nepa #devcommunity
-
.NET folks, don't miss J. Tower's two #techbash sessions this fall!
Join us at Kalahari Resort in the #poconos Nov 7-10. Learn more: https://techbash.com
#dotnet #dotnetcli #developers #fluentvalidation #techevent #devconference #nepa #devcommunity
-
.NET folks, don't miss J. Tower's two #techbash sessions this fall!
Join us at Kalahari Resort in the #poconos Nov 7-10. Learn more: https://techbash.com
#dotnet #dotnetcli #developers #fluentvalidation #techevent #devconference #nepa #devcommunity
-
.NET folks, don't miss J. Tower's two #techbash sessions this fall!
Join us at Kalahari Resort in the #poconos Nov 7-10. Learn more: https://techbash.com
#dotnet #dotnetcli #developers #fluentvalidation #techevent #devconference #nepa #devcommunity
-
.NET folks, don't miss J. Tower's two #techbash sessions this fall!
Join us at Kalahari Resort in the #poconos Nov 7-10. Learn more: https://techbash.com
#dotnet #dotnetcli #developers #fluentvalidation #techevent #devconference #nepa #devcommunity
-
@tpetrina Thanks for pointing out that usecase, that's one advantage I thought of as well. I kinda had an argument with someone who uses records now for everything and that I find problematic. E.g. you can't inherit from libs like #FluentValidation with records.
For the usecase you blogged about I think it's nice, but with .Net8 I would still prefer classes with primary constructors I guess.
-
@tpetrina Thanks for pointing out that usecase, that's one advantage I thought of as well. I kinda had an argument with someone who uses records now for everything and that I find problematic. E.g. you can't inherit from libs like #FluentValidation with records.
For the usecase you blogged about I think it's nice, but with .Net8 I would still prefer classes with primary constructors I guess.
-
@tpetrina Thanks for pointing out that usecase, that's one advantage I thought of as well. I kinda had an argument with someone who uses records now for everything and that I find problematic. E.g. you can't inherit from libs like #FluentValidation with records.
For the usecase you blogged about I think it's nice, but with .Net8 I would still prefer classes with primary constructors I guess.
-
@tpetrina Thanks for pointing out that usecase, that's one advantage I thought of as well. I kinda had an argument with someone who uses records now for everything and that I find problematic. E.g. you can't inherit from libs like #FluentValidation with records.
For the usecase you blogged about I think it's nice, but with .Net8 I would still prefer classes with primary constructors I guess.
-
@tpetrina Thanks for pointing out that usecase, that's one advantage I thought of as well. I kinda had an argument with someone who uses records now for everything and that I find problematic. E.g. you can't inherit from libs like #FluentValidation with records.
For the usecase you blogged about I think it's nice, but with .Net8 I would still prefer classes with primary constructors I guess.
-
New Coding Shorts Video: Minimal API Endpoint Filters for Model Validation #aspnetcore #minimalapi #fluentvalidation
-
New Coding Shorts Video: Minimal API Endpoint Filters for Model Validation #aspnetcore #minimalapi #fluentvalidation
-
New Coding Shorts Video: Minimal API Endpoint Filters for Model Validation #aspnetcore #minimalapi #fluentvalidation
-
New Coding Shorts Video: Minimal API Endpoint Filters for Model Validation #aspnetcore #minimalapi #fluentvalidation
-
New Coding Shorts Video: Minimal API Endpoint Filters for Model Validation #aspnetcore #minimalapi #fluentvalidation
-
I just learned that #FluentValidation added a "ChildRules" method, which allows you to validate nested objects without any additional validators.
That's helpful when you have a #dotnet object graph that is not used outside the root. Sweet.
-
I just learned that #FluentValidation added a "ChildRules" method, which allows you to validate nested objects without any additional validators.
That's helpful when you have a #dotnet object graph that is not used outside the root. Sweet.
-
I just learned that #FluentValidation added a "ChildRules" method, which allows you to validate nested objects without any additional validators.
That's helpful when you have a #dotnet object graph that is not used outside the root. Sweet.
-
I just learned that #FluentValidation added a "ChildRules" method, which allows you to validate nested objects without any additional validators.
That's helpful when you have a #dotnet object graph that is not used outside the root. Sweet.
-
I just learned that #FluentValidation added a "ChildRules" method, which allows you to validate nested objects without any additional validators.
That's helpful when you have a #dotnet object graph that is not used outside the root. Sweet.
-
My first try using chatGTP to create a Xamarin.Forms login page with #ReactiveUI, #Fody #Refit #FluentValidation (Spanish though). Amazing results IMO.
https://www.youtube.com/watch?v=LS7Ot3GLfjc -
My first try using chatGTP to create a Xamarin.Forms login page with #ReactiveUI, #Fody #Refit #FluentValidation (Spanish though). Amazing results IMO.
https://www.youtube.com/watch?v=LS7Ot3GLfjc -
My first try using chatGTP to create a Xamarin.Forms login page with #ReactiveUI, #Fody #Refit #FluentValidation (Spanish though). Amazing results IMO.
https://www.youtube.com/watch?v=LS7Ot3GLfjc -
Any way to include the parent object name e.g. http://parent.child.name in a #FluentValidation generated error message? Only "name" in the above example is included in the PropertyName placeholder but I can see the full path in the ValidationFailure.PropertyName.
-
Any way to include the parent object name e.g. http://parent.child.name in a #FluentValidation generated error message? Only "name" in the above example is included in the PropertyName placeholder but I can see the full path in the ValidationFailure.PropertyName.
-
Any way to include the parent object name e.g. http://parent.child.name in a #FluentValidation generated error message? Only "name" in the above example is included in the PropertyName placeholder but I can see the full path in the ValidationFailure.PropertyName.
-
Any way to include the parent object name e.g. http://parent.child.name in a #FluentValidation generated error message? Only "name" in the above example is included in the PropertyName placeholder but I can see the full path in the ValidationFailure.PropertyName.
-
Any way to include the parent object name e.g. http://parent.child.name in a #FluentValidation generated error message? Only "name" in the above example is included in the PropertyName placeholder but I can see the full path in the ValidationFailure.PropertyName.
-
This is not very helpful. When printing the assertion, the actual value’s ToString() evaluates to the correct value, and so it looks correct in the test output. #dotnet #FluentValidation
-
This is not very helpful. When printing the assertion, the actual value’s ToString() evaluates to the correct value, and so it looks correct in the test output. #dotnet #FluentValidation
-
This is not very helpful. When printing the assertion, the actual value’s ToString() evaluates to the correct value, and so it looks correct in the test output. #dotnet #FluentValidation
-
This is not very helpful. When printing the assertion, the actual value’s ToString() evaluates to the correct value, and so it looks correct in the test output. #dotnet #FluentValidation