FluentValidation 7.6.100Prefix Reserved
See the version list below for details.
dotnet add package FluentValidation --version 7.6.100
NuGet\Install-Package FluentValidation -Version 7.6.100
<PackageReference Include="FluentValidation" Version="7.6.100" />
paket add FluentValidation --version 7.6.100
#r "nuget: FluentValidation, 7.6.100"
// Install FluentValidation as a Cake Addin #addin nuget:?package=FluentValidation&version=7.6.100 // Install FluentValidation as a Cake Tool #tool nuget:?package=FluentValidation&version=7.6.100
A validation library for .NET that uses a fluent interface to construct strongly-typed validation rules.
|Product||Versions Compatible and additional computed target framework versions.|
|.NET||net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed.|
|.NET Core||netcoreapp1.0 was computed. netcoreapp1.1 was computed. netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed.|
|.NET Standard||netstandard1.1 is compatible. netstandard1.2 was computed. netstandard1.3 was computed. netstandard1.4 was computed. netstandard1.5 was computed. netstandard1.6 is compatible. netstandard2.0 is compatible. netstandard2.1 was computed.|
|.NET Framework||net45 is compatible. net451 was computed. net452 was computed. net46 was computed. net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed.|
|MonoAndroid||monoandroid was computed.|
|MonoMac||monomac was computed.|
|MonoTouch||monotouch was computed.|
|Tizen||tizen30 was computed. tizen40 was computed. tizen60 was computed.|
|Universal Windows Platform||uap was computed. uap10.0 was computed.|
|Windows Phone||wpa81 was computed.|
|Windows Store||netcore was computed. netcore45 was computed. netcore451 was computed.|
|Xamarin.iOS||xamarinios was computed.|
|Xamarin.Mac||xamarinmac was computed.|
|Xamarin.TVOS||xamarintvos was computed.|
|Xamarin.WatchOS||xamarinwatchos was computed.|
NuGet packages (1.7K)
Showing the top 5 NuGet packages that depend on FluentValidation:
Dependency injection extensions for FluentValidation
AspNetCore integration for FluentValidation
Swagger ISchemaFilter that uses FluentValidation validators instead System.ComponentModel based attributes.
Ocelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.
ASP.NET WebApi integration for FluentValidation
GitHub repositories (174)
Showing the top 5 popular GitHub repositories that depend on FluentValidation:
ASP.NET Boilerplate - Web Application Framework
Open Source Web Application Framework for ASP.NET Core. Offers an opinionated architecture to build enterprise software solutions with best practices on top of the .NET and the ASP.NET Core platforms. Provides the fundamental infrastructure, production-ready startup templates, application modules, UI themes, tooling, guides and documentation.
Sample ASP.NET Core 7.0 reference application, powered by Microsoft, demonstrating a layered application architecture with monolithic deployment model. Download the eBook PDF from docs folder.
Smart PVR for newsgroup and bittorrent users.
Full Modular Monolith application with Domain-Driven Design approach.
Changes in 7.6:
* WhenAsync now works correctly when calling the non-async Validate method.
* ASP.NET Core integration has been updated to ASP.NET Core 2.1.
* Include statement now works when explicitly selecting properties to validate.
* Added Ukranian language support.
* Added Arabic language support.
* Added caching when instantiating validators to obtain clientside metadata.
Changes in 7.5.2:
* RuleSet method can now take multiple ruleset names by usinga comma-separated string.
* Make setters on ValidationFailure's properties public to allow for easier deserialization.
* Additional overload for OverridePropertyName that takes an expression.
* Add overload of Include that takes a func to lazily create the inner validator.
* Make error code resolution pluggable using ValidatorOptions.ErrorCodeResolver
Changes in 7.5.1:
* Resolved issues with referencing FluentValidation from legacy PCLs.
* Added support for CustomizeValidatorAttribute to the legacy WebApi integration for consistency with MVC5 and AspNetCore.
Changes in 7.5:
* Better handling of clientside messages when using custom overriden language resources
* Added flag in the ValidationContext's RootDataContext when a validator is invoked by the automatic MVC/WebApi integration
* Improvements to some of the validation tester's messages
* Added Transform method to transform property values prior to validation
* Improve support for DisplayAttribute / DisplayNameAttribute when inferring property display name
* New language translations (Slovak/Hebrew/Brazilian Portuguese)
* Cache display names by default
* Ensure ShouldHaveChildValidator test method works with model-level rules
* Removed netstandard1.0 support. Supported platforms are now netstandard1.1, netstandard2.0 and net45.
Changes in 7.4:
* Improved syntax for DependentRules
* ValidationException serialization support when running on full framework
* Added ComparisonProperty placeholder to some validators
* The Test Helper now correctly handles read-only properties
* Add CancellationToken support to ValidateAndThrowAsync and various ValidateAsync overloads
* Improved functionality for custom MessageBuilders
* Updated AspNetCore integration to MVC version 2.0.2
* Update MVC5 AddToModelState extension not to overwrite existing attempted values
* Added SetRulesetForClientsideMessages method for MVC5/AspNetCore as an alternative to using the RulesetForClientSideMessagesAttribute
Changes in 7.3:
* Major changes to AspNetCore integration including better support for collections and implicit validation (opt-in)
* Fix - Updated EnumValidator's Flags support to handle the ~0 value
* Fix - TestHelper checking for child validator would respond with the wrong type
* Fix - Updated translations for some validators
* Fix - Overload of WithName that takes a lambda generated an exception
* Added versions of WhenAsync and UnlessAsync that support CancellationTokens
* Simplify calls to DependentRules
* Add Skip property to CustomizeValidatorAttribute in the ASP.NET Core integration
Changes in 7.2:
* Updated AspNetCore integration to support IValidatableObject
* Updated AspNetCore integration to allow mixing multiple validation strategies in the same model
* Updated AspNetCore integration to support RulesetForClientsideMessagesAttribute
* Fix - Property names were not generated properly for nested types when using AddFailure inside a Custom validator
* Fix - NullReferenceException when using CustomAsync but the validator is invoked synchronously
* Fix - Clientside integration in AspNetCore being resolved from the root-level service provider
* Fix - Allow empty string to be passed to OverridePropertyName
Changes in 7.1.1:
* Fix - Incorrect property name was generated when using RuleForEach combined with SetValidator
* Fix - Nesting async validators inside DependentRules didn't wait for completion
Changes in 7.1:
* New RuleFor().Custom() method as a replacement for the old, deprecated Custom method
* Improved messages in the ShouldHaveChildValidator test extension
* Test helper works with nested properties
* Additional overload of WithState allows access to collection item when used with RuleForEach
* Fix - Wrong values were generated as part of the MVC5 clientside integration for MinLength and MaxLength validators
* Fix - AssemblyScanner now excludes abstract and generic types
* Fix - InvalidCastException when using lazy WithMessage combined with RuleForEach
* WithState enhanced to allow access to the ValidationContext
Changes in 7.0:
7.0 is a major release that contains several breaking changes, especially with Localization. If you use FluentValidation's support for localization please read the updated documentation: https://github.com/JeremySkinner/FluentValidation/wiki/f.-Localization
* Localization rewrite to not require satellite assemblies
* New 'Custom' rule method replaces the root-level Custom method
* Switch to Netstandard based build process
* Assemblies are now signed / strongly named - see https://github.com/JeremySkinner/FluentValidation/wiki/l.-Strong-naming-and-signed-packages
* Fix - Possible NullReferenceException in the AspNetCore clientside integration for length validators
* Fix - Don't clear the ModelValidatorProviders collection by default in the AspNetCore integration (added new ClearValidatorProviders property to control this behaviour)
* Fix - Ensure IValidatorFactory is resolved from request scope in asp.net core integration
* Fix - Property getter that throws an exception causes validation to fail in WebApi integration
* Fix - Issue in AspNetCore integration where we tried to resolve a collection validator in some situations where a class validator should be used
* Fix - Incorrect clientside validation attributes generated for email validator and credit card validator in the asp.net core integration
* Fix - Child model validation now works in webapi integration
* Improve splitting of PascalCased property names to support uppercase character sequences
* ValidationResult.ErrorCode property now always returns the type of the PropertyValidator that generated the message, unless it's been explicitly overriden
Full release notes can be found at https://github.com/JeremySkinner/FluentValidation/blob/master/Changelog.txt