Factory Pattern in C#: Creating Objects with Ease

In this video, you'll learn how to implement the Factory Pattern in C# and how it can help simplify your object creation process. You'll see step-by-step how to implement this design pattern in your #csharp projects and follow along with practical examples to reinforce your understanding. By the end of this video, you'll be able to create objects with ease using the Factory Pattern, making your code more maintainable, scalable, and organized. Whether you're a beginner or an experienced C# developer, this video is packed with valuable insights that will take your coding skills to the next level.
Link to code in GitHub: github.com/sea...
#designpatterns #softwareengineer #developer

[@Nobody-hs9cl]

A perfect example of the meaningful application of the Factory Design Pattern. I have seen dozens of videos. This is the only one that clearly shows the benefits of the Factory Pattern.

[@campbelltech]

Thank you!

[@unnatpandyaGhost]

May be tons of videos/articles I watched, but this explains way simpler way. Great work 👍🏼

[@campbelltech]

Thank you for the great feedback Unnat. This is our greatest goal, to simply complexity.

[@criticalthinker1123]

*for that I subscribed*

[@dipikabhagat5252]

Excellent tutorial .

[@campbelltech]

Glad you liked it!

[@edoreemmanuel4250]

The best tutorial I have seen so far. cheers mate

[@campbelltech]

Thank you!

[@akhtar4993]

Just simple and excellent. Please keep it up.

[@campbelltech]

Thank you so much. Simplicity is our greatest goal!

[@msdhonicoolcaptain]

Just loved your explanation!! more energy to you

[@campbelltech]

Thank you! The same to you!

[@souvikdatta97]

Amazing

[@campbelltech]

Thanks!

[@preslaviliev6843]

So simple . Thanks a lot !

[@campbelltech]

Thanks Preslav!

[@susanfalk2148]

Great video! I was watching one of your other videos explaining abstract factory methods in C#, but halfway through it was marked as private, so I didn't get to see the rest. Will it come back up?

[@T0g3ly]

Hi I’m learning design patterns I like your videos but can you possibly make a video of when I should maybe use factory method vs abstract. I understand there isn’t a simple answer but maybe a “Look for these signs answer”

[@campbelltech]

Thanks for the request. I will consider it.

[@GergelyCsermely]

Thanks

[@campbelltech]

You're welcome.

[@kylebrault4414]

What do you do if CreditCard has a method GetStatement that returns a CreditCardStatementModel object, but GetStatement for paypal returns a PayPalStatementModel object with different fields? Since methods have the same name but a different return type, you couldn't implement a common interface.

[@campbelltech]

Hi Kyle, you can introduce a base or abstract StatementModel. Then CreditCardStatementModel and PayPalStatementModel can inherit from or extend StatementModel. Then, let the GetStatement method return StatementModel, and through Polymorphism you can "cast" it back to the concrete types in the concrete classes.

[@abdullahbinmamun3803]

In this case we can use abstract class instead of using an interface. which can have an abstract method named "Statement" which will return a statement. other classes like GooglePay, PayPal and CreditCard will override and implement the same "Statement" method but will return different statements. I hope, I explained it correctly.

[@Benndot97]

What extension is he using to get that dropdown menu for creating new C# documents quickly?

[@sewcyde]

DOTNET DEV KIT EXTENSION

[@campbelltech]

And C# Extensions by JosKreativ

[@Guillen8606]

Great video. What font are you using on vsCode?

[@campbelltech]

I use the Material Theme on Linux Ubuntu 22.04.

[@dipanjandhar3982]

How does your code promotes open closed principle ?

[@campbelltech]

The Factory method allows you to decouple creation logic from your client code. In this way, if you add, for example, a new payment method you only need to add a new class, e.g. ApplePayPayment and add support for it in your factory method. Your client code, which could be your main service code, can then stay exactly the same. In other words, it is closed for modification, but the Factory method makes it open for extension.

[@RuanCowley]

@@campbelltech Good answer! 👌

[@scotterd]

@@campbelltech wouldn't use also need to add a new enum called ApplePay and modify the client to call the factory with the new enum?

[@NewQuietBear]

You violate the open/closed principle. Everytime u have to add a new payment method to the factory and enum.

[@campbelltech]

The client code, however, remains unchanged and follows the open-closed principle. Many would argue that adding the enums and extending the factory method only, still remain within the boundaries of the open-closed principle. If you want to comply on all levels, you will have to use reflection, possibly compromising on performance.