Validation is one of the key components in any web app. After all, we should never trust any input to our applications, ever [http://stackoverflow.com/a/2794089/106356]. Up until now, my group has been building MVC-based web apps, in those apps we've been content to use built-in or
Regular expressions [https://en.wikipedia.org/wiki/Regular_expression] are quite possibly the least enjoyable thing about programming, mostly because I can't read them they're terrible. They're supposed to be used to search for and match within text, but the more often I encounter them, the more often I lament
One of the new features from ASP.NET Core 1.0 [http://www.hanselman.com/blog/ASPNET5IsDeadIntroducingASPNETCore10AndNETCore10.aspx] is the idea of Middleware [https://docs.asp.net/en/latest/fundamentals/middleware.html]. Middleware are components of an application that examine the requests responses coming in to and going out from
This is the final part of a four-part series describing how to build an application in .NET using the Command-Query Responsibility Segregation (CQRS) [http://martinfowler.com/bliki/CQRS.html] and Event Sourcing (ES) [http://martinfowler.com/eaaDev/EventSourcing.html] patterns, as well as the SimpleCQRS [https://github.com/tyronegroves/SimpleCQRS]
This is Part 3 of a four-part series describing how to build an application in .NET using the Command-Query Responsibility Segregation (CQRS) [http://martinfowler.com/bliki/CQRS.html] and Event Sourcing (ES) [http://martinfowler.com/eaaDev/EventSourcing.html] patterns, as well as the SimpleCQRS [https://github.com/tyronegroves/SimpleCQRS] NuGet