Awesome! thanks for this video, if you try to register like scoped or Transient there are this error: "Cannot implicitly convert type string to system.IServiceProvider"
The way you implemented is very similar to strategy pattern, practically is the same. Can you please clarify me the difference? because here you selected a particular behavior on runtime based on the type, that's the definition for strategy pattern instead of factory pattern. Thanks in advance
Is this is factory design pattern? The name in the heading is factory method design pattern. Can you say difference between factory and factory method design pattern or can you please make video of factory method in .net core
@Noufal P, I have covered both in my channel, if you watch both of them it should be clear the difference. After watching both if you still have confusion, please let me know, I will be more than happy to explain.
Thanks for the reply. I didn't found factory design pattern in .net core in your channel. Can you give link of factory design pattern in .net core in your channel.
Appreciate your efforts but this is not Factory method design pattern, rather this implementation is of a Simple Factory Design pattern. Factory method design pattern states that "It provides an interface for creating objects in a superclass, but allows subclasses to alter the type of objects that will be created." In the video, we are just returning instances of the subclasses based upon the type - this is simple factory design pattern implementation.
Maybe for some one this can be useful: In first aproach minute 2.50, into Startup.ConfigureServices sadd: services.AddSingleton(); services.AddSingleton(); services.AddSingleton(); . And inside LawnMowerCatalogController create a constructor with this sign: IEnumerable lawnmowerCatalog then you can test this aproach.
![Abstract Factory Design Pattern (An Introduction for .NET Developers [C# and .NET 5])](http://i.ytimg.com/vi/NZLk__ZR5ww/mqdefault.jpg)
![Abstract Factory Design Pattern (An Introduction for .NET Developers [C# and .NET 5])](/img/tr.png)
![Builder Design Pattern (An Introduction for .NET Developers [.NET 5 and C#])](/img/n.gif)
Awesome! thanks for this video, if you try to register like scoped or Transient there are this error: "Cannot implicitly convert type string to system.IServiceProvider"
The way you implemented is very similar to strategy pattern, practically is the same. Can you please clarify me the difference? because here you selected a particular behavior on runtime based on the type, that's the definition for strategy pattern instead of factory pattern.
Thanks in advance
Awesome! it just answered the question in my brain!
@William Liu,
thanks for watching!
Please make a video on Abstract factory design pattern
@Dilip Gautam, sure!
Nice video, in my opinion lambda looks disgusting in line rather in a it's on class hahah, I know it was just a demo! :P
Is this is factory design pattern? The name in the heading is factory method design pattern. Can you say difference between factory and factory method design pattern or can you please make video of factory method in .net core
@Noufal P, I have covered both in my channel, if you watch both of them it should be clear the difference. After watching both if you still have confusion, please let me know, I will be more than happy to explain.
Thanks for the reply. I didn't found factory design pattern in .net core in your channel. Can you give link of factory design pattern in .net core in your channel.
@@noufalp3464 This is the url for the Abstract factory design pattern: th-cam.com/video/NZLk__ZR5ww/w-d-xo.html
@DotNet Core Central, thank you
Appreciate your efforts but this is not Factory method design pattern, rather this implementation is of a Simple Factory Design pattern.
Factory method design pattern states that "It provides an interface for creating objects in a superclass, but allows subclasses to alter the type of objects that will be created."
In the video, we are just returning instances of the subclasses based upon the type - this is simple factory design pattern implementation.
It's amazing 😍😍😍
@ShahRukh Khan, thanks!
Why have you registered as singleton?
@Vivek Tiwary, since there is no state maintained, singleton just fits the bill. I will not use singleton if I have a complex state inside the object.
question is not allowed. comments are welcome
Muy bueno
@hector, thanks for watching!
Maybe for some one this can be useful: In first aproach minute 2.50, into Startup.ConfigureServices sadd: services.AddSingleton(); services.AddSingleton(); services.AddSingleton(); . And inside LawnMowerCatalogController create a constructor with this sign: IEnumerable lawnmowerCatalog then you can test this aproach.