/explore
|
You are here 
|
www.darrenhorrocks.co.uk | ||
| | | | |
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... | |
| | | | |
www.tpeczek.com
|
|
| | | | | In this post I'm closing the circle around streaming JSON objects (NDJSON) in .NET by discussing receiving NDJSON based request in ASP.NET Core. | |
| | | | |
www.kallemarjokorpi.fi
|
|
| | | | | I gathered to this blog post a list of external libraries that I usually add to a greenfield .NET API project. | |
| | | | |
az-liftshift.com
|
|
| | | This article shows how an ASP.NET Core Razor Page application could implement an automatic sign-out when a user does not use the application for n-minutes. The application is secured using Azure AD B2C. To remove the session, the client must sign-out both on the ASP.NET Core application and the Azure AD B2C identity provider or | ||
