/explore
|
You are here 
|
www.tpeczek.com | ||
| | | | |
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... |
|
| | | | | ||
| | | | |
dontcodetired.com
Don't Code Tired - Jason Roberts on Software Development and .NET - This is the fifth part in a series demonstrating how to setup continuous deployment of an Azure Func |
|
| | | | | ||
| | | | |
www.darrenhorrocks.co.uk
Building APIs that handle large datasets can be a challenge. A common approach is to collect all the data into a list, convert it to JSON, and then send it all at once. But what happens when that dataset is massive? Your API might freeze up while it's building the response, and you could end up with a huge memory footprint. Fortunately, ASP.NET Core provides a great solution for this problem: IAsyncEnumerable. |
|
| | | | | ||
| | | | |
cupano.com
My Blog Posts. Contribute to joecupano/blog development by creating an account on GitHub. |
|
| | | |||
