In the last post, we have used SQL stored procedure to perform the CRUD operations. It best suits when the CRUD operations involve complex data manipulation. However, sometimes we do not have to follow this path, especially when the SQL table is simple and CRUD operations are straightforward.
The objective of this article is to explain the simplest way of designing the Data Access Layer.
Layered architectures are generally preferred for application development because of code reuse, flexibility, performance and maintainability.
In a layered architecture the Data Access is primarily responsible of communicating with the Database, whereas the business layer focuses on business logic and rules. The presentation layer concentrates on the UI.
The objective of this article is to explain the simple but an elegant way of designing the Data Access Layer of an application.
Despite IDisposable having only a single method named Dispose to implement, it is commonly implemented incorrectly. After reading this blog post it should be clear how and when to implement IDisposable, as well as how to ensure that resources are properly disposed when bad things happen (also knows as exceptions).
Data validation is quite critical when it comes to usability and data integrity of any software or application. It helps in improving the quality of the data as well as ensuring the data consistency.
Fluent Validation is a small validation library for .NET that uses a fluent interface and lambda expressions for building validation rules.