Design Pattern Training using C# - Day 2 | Builder | Fluent Interface | Prototype Design Pattern скачать в хорошем качестве

Design Pattern Training using C# - Day 2 | Builder | Fluent Interface | Prototype Design Pattern

Design Pattern Training using C# - Day 2 | Builder Design Pattern | Fluent Interface | Prototype Design Pattern | Deep Copy vs Shallow Copy What is the Builder Design Pattern in C#? According to GoF, the Builder Design Pattern builds a complex object using many simple objects and using a step-by-step approach. The Process of constructing a complex object should be generic so that the same construction process can be used to create different representations of the same complex object. So, the Builder Design Pattern is all about separating the construction process from its representation. When the construction process of your object is very complex then only you need to use to Builder Design Pattern. If this is not clear at the moment then don’t worry, we will try to understand this with an example. What is the Fluent Interface Design Pattern in C#? The main objective of the Fluent Interface Design Pattern is that we can apply multiple properties (or methods) to an object by connecting them with dots (.) without having to re-specify the object name each time. What is the Prototype Design Pattern in C#? As per the GoF Definition, Prototype Design Pattern specifies the kind of objects to create using a prototypical instance, and creating new objects by copying this prototype. To simplify the above definition, we can say that, the Prototype Design Pattern gives us a way to create a new or cloned object from the existing object of a class. That means it clones the existing object with its data into a new object. If we do any changes to the cloned object (i.e. new object) then it does not affect the original object. What is Object Cloning in C#? When we talk about Object Cloning in C#, it means it is all about the Call by Value. So, if we do any changes to one object then it will not affect the other object. Shallow Copy vs Deep Copy in C# In the case of Shallow copy, it will create the new object from the existing object and then copy the value type fields of the current object to the new object. But in the case of reference type, it will only copy the reference, not the referred object itself. Therefore, the original and clone refer to the same object in the case of reference type. In the case of deep copy, it will create a new object from the existing object and then copy the fields of the current object to the newly created object. If the field is a value type, then a bit-by-bit copy of the field will be performed. If the field is a reference type, then a new copy of the referred object is going to be created. Text Documents of the Video: Builder Design Pattern in C#: https://dotnettutorials.net/lesson/bu... Fluent Interface Design Pattern in C#: https://dotnettutorials.net/lesson/fl... Prototype Design Pattern in C#: https://dotnettutorials.net/lesson/pr... Shallow Copy vs Deep Copy in C#: https://dotnettutorials.net/lesson/sh... #designpattern #csharpdesignpattern #dotnettutorials #designpatterntraining #BuilderDesignPattern #FluentInterfaceDesignPattern #PrototypeDesignPattern #ShallowCopyCSharp #DeepCopyCSharp #designpatterncsharp #pranaya