Explore >> Select a destination
|
You are here 
|
nodogmablog.bryanhogan.net | ||
| | | | |
stenbrinke.nl
|
|
| | | | | Using Bogus to generate realistic fake data together with Entity Framework Core to set up your testing data in seconds! | |
| | | | |
michaelscodingspot.com
|
|
| | | | | Michael Shpilt's Blog on .NET software development, C#, performance, debugging, and programming productivity | |
| | | | |
rrees.me
|
|
| | | | | If you've ever read a piece of advice about using Postgres Enums you've probably read not to use them and to use a peer table with foreign key constraints instead. If you've ever seen a Typescript codebase in the wild recently chances are that this advice has absolutely been ignored and enums are all over... | |
| | | | |
blog.codefarm.me
|
|
| | | Model validation is a crucial aspect of building robust ASP.NET Core applications, ensuring data integrity and providing a smooth user experience. This post explores the various mechanisms for validating data, from built-in attributes and custom validation logic to handling non-nullable reference types and top-level node validation. 1. Model state 2. Validation 3. Validation attributes 4. Error messages 5. Non-nullable reference types and [Required] attribute 6. Custom attributes 7. Refereces 1. Model state Model state represents data binding and validation errors that occur before action execution, which web apps typically handle by redisplaying pages, while ApiController-decorated Web APIs automatically return a 400 response. [ApiController] [Route("api/[c... | ||
