I found this article really a very important for developer. So I would like to share this with you. Hope that it may help you for better development.
The SOLID acronym describes five object-oriented design principles that, when followed, produce code that is cleaner and more maintainable. The last principle, the Dependency Inversion Principle, suggests that details depend upon abstractions. Unfortunately, typical project relationships in .NET applications can make this principle difficult to follow.
In this article, describe how one can structure a set of projects in a Visual Studio solution such that DIP can be followed, allowing for the creation of a SOLID solution......
For more details please visits: Creating a SOLID Visual Studio Solution
Sharing real-world experiences about C#, Dynamics CRM, Dynamics 365, Dynamics NAV/Business Central, SharePoint,PowerBI,ASP.net and more...
Subscribe to:
Comments (Atom)
Method 'StartWorkflowOnListItem' in type 'Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider'
Exception: Method 'StartWorkflowOnListItem' in type 'Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider'...
-
Very recently I get some request about ASCII code generate. So that I share with this code... using System; using System.Web.UI; public part...
-
Few days ago I have posted an article " How To Access One UserControl from Another UserControl Using ASP.NET ". When I try to find...
-
Sometimes I face some problem with single web form(only aspx page no code behind page) page. I am used to work in code-behind page,so that I...
