Explore >> Select a destination
|
You are here 
|
www.darrenhorrocks.co.uk | ||
| | | | |
www.kallemarjokorpi.fi
|
|
| | | | | I gathered to this blog post a list of external libraries that I usually add to a greenfield .NET API project. | |
| | | | |
nodogmablog.bryanhogan.net
|
|
| | | | | If you serialize an already serialized string, the serializer will replace double quotes with \\u0022. Here is a way to get back the familiar \\". | |
| | | | |
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.kallemarjokorpi.fi
|
|
| | | The .NET Aspire Dashboard is a centralized view into distributed application insights, environment variables, logs, traces, and monitoring capabilities. The .NET Aspire Dashboard isn't just a traditional insights dashboard; it also allows developers to manage applications to some extent. For example, resources can be started and stopped directly from the | ||
