Resources   No resource found

• Measure Depth Of Inheritance And Class Coupling In Visual StudioApr 20, 2014. Here, we will see how to measure depth of inheritance and class coupling in the Visual Studio environment.
• Difference Between Loose Coupling and Tight CouplingDec 19, 2012. The pros and cons Loose Coupling and Tight Coupling.
• Voice Of A Developer: Decoupling Your Application - Part 35Jun 07, 2016. In this article, you will learn about decoupling your application in JavaScript.
• In Depth Look: Strategy Design Pattern, Dependency Injection (DI), Open/Closed Principle (OCP) and Loose CouplingJun 06, 2015. This article explains the Strategy Design Pattern, Dependency Injection, Open/Closed principle and Loose Coupling.
• Implement the Mediator Pattern in a .NET Web APIDec 17, 2024. Learn how to implement the Mediator Pattern in a .NET Web API using the MediatR library. This design pattern reduces tight coupling between components by centralizing communication through a mediator.
• Understanding the Interface Segregation Principle (ISP) with C#Aug 21, 2024. Explore the Interface Segregation Principle (ISP) from SOLID design principles to ensure code flexibility and maintainability. ISP advocates for breaking down large, unwieldy interfaces into smaller, client-specific ones, reducing unnecessary dependencies. Learn how to apply this principle with practical examples in C#.
• Dependency Injection in ASP.NET CoreJul 16, 2024. Dependency Injection (DI) in ASP.NET Core enhances modularity, testability, and maintainability by providing class dependencies externally via the built-in Inversion of Control (IoC) container. Configure services in Startup.cs, utilize constructor injection in controllers, and choose appropriate lifetimes (Transient, Scoped, Singleton).
• Microsoft.Extensions.DependencyInjection for Dependency InjectionApr 16, 2024. Dependency Injection (DI) is a software development design pattern that aims to achieve loose coupling between components and enhance the maintainability, testability, and scalability of applications. In the context of C#, DI is commonly implemented using frameworks like .
• Mediator Design Pattern in ASP.NET Core Web API with 3-Tier ArchitectureOct 19, 2023. The Mediator Design Pattern is a behavioral design pattern that defines an object that centralizes communication between a set of objects. It promotes loose coupling between components by preventing direct connections between them. Instead of components communicating directly, they communicate through a mediator.
• Introduction To MediatR PatternJul 29, 2020. MediatR pattern promotes loose coupling by facilitating in-process messaging, reducing dependencies between objects. It enables one-way broadcast communication, allowing objects to communicate solely through MediatR. Advantages include message processing, easy installation via NuGet, and support for request/response and notification.
• Builder Design Pattern Using C#Apr 18, 2019. In this article, we will understand the Builder Design Pattern, when we should actually use it, and a practical example along with the disadvantages and advantages of it.
• Observer Design Pattern Using C#Mar 29, 2019. In this article, we will understand what Observer Pattern is and when we actually need to use it, along with a practical example and real life use case.
• Adapter Design Pattern Explained SimplyMar 22, 2019. This article will explain the adapter design pattern , its practical use case with its benefits and drawbacks.
• Dependency Injection - Part Four -Embracing AbstractionAug 18, 2017. Dependency Injection (DI) is a technique that helps us achieve loose coupling between objects and their collaborators. In this post, we will use constructor based dependency injection, however, we are not going to use any DI container for now.
• Dependency Injection - Part Two - Five Reasons To Write Loosely Coupled CodeAug 09, 2017. A loosely coupled application has good isolation among its classes, modules and assemblies. Therefore, if we make a change to one part of the application, we only need to update the relevant modules. We do not need to make changes throughout the application.
• Dependency Injection - Part One -Tightly Coupled ApplicationAug 07, 2017. It is a best practice to use interfaces instead of concrete classes. These interfaces can then be mocked at the time of unit testing, which will prevent any call to the actual database. Also, it is a good practice to stop "newing-up" objects in classes.
• Onion Architecture Using MVC and Database First ApproachMay 05, 2015. The main purpose of this article is try to explain the Onion Architecture and provide sample sample code that is loosely coupled and easily maintainable.
• Basics of Dependency InjectionApr 27, 2015. In this article we will learn about Dependency Injection.
• Dependency Injection In Software EngineeringApr 02, 2015. In this article we will learn about Dependency Injection which is a software design pattern that implements inversion of control.
• Constructor Dependency Injection Pattern Implementation in C#May 25, 2014. This article is about the Constructor Dependency Injection Pattern Implementation in C#.
• Demystify SOLID: D For “Dependency Inversion Principal”May 10, 2014. In this article we will discuss the last principal called “Dependency Inversion Principal”. This is one of the important principals to develop de-coupled architecture.
• Dynamic WCF Usage in ClientJun 13, 2013. I have decided to show a Channel Factory usage in the client side.The Channel Factory will be created in a generic ServiceFactory according to ServiceContract type. It will provide us full isolated usage WCF service more dynamically than adding a service into the service references. Also I would like to show us proxy and channelFactory usage differences.
• Implement Concrete Factory Design Pattern using Reflection in VB.NETNov 10, 2012. Reflection is used to dynamically create an instance of a type, bind the type to an existing object, or get the type from an existing object. In this example, we implement Concrete Factory Pattern using Reflection to fetch records from MS-Access and MS-SQL Database.
• S.O.L.I.D Design Principles Explained : Part 2Aug 12, 2012. Here we will discuss the second letter in the word SOLID i.e., O. O stands for OCP (Open Closed Principle).
• S.O.L.I.D Design Principles Explained : Part 1Aug 12, 2012. This article will cover the acronyms for SOLID and a brief introduction to Cohesion and Coupling is provided to understand the SOLID principles.
• Introduction to Structure MapSep 01, 2010. This article provides an introduction to the concepts of the Dependency Injection Principle (DIP) and Inversion of Control (IOC), explaining their significance in software development.
• Introduction to Loosely Coupled CollectionsFeb 16, 2009. This article explains about Implementation of Loosely Coupled Collections in C#.
• DI and IOCJan 19, 2009. In this article we will discuss about how IOC and DI can help us build loosely coupled software architecture.
• Design pattern -Inversion of control and Dependency injectionNov 04, 2008. In this section we will discuss about how IOC and DI can help us build loosely coupled software architecture.
• Object Instantiation in C#: Part II - Factory MethodsJun 24, 2007. There are many ways to approach object instantiation. In this article we’ll cover a few of the patterns used to instantiate objects. We'll look at different instantiation patterns used to control how objects are instantiated.
• A Better Solution for Enterprise Architects - SOA : Part IFeb 06, 2007. I would like to begin to determine what SOA (service-oriented architecture) is technically meaning. We can clearly say SOA is a methodology for designing software architectures to utilize and organize distributed systems using loosely coupled software services.