Learn Design Patterns - Factory Method Pattern

Sign in to leave a comment.

• 

  Prasad Makkena13y agoPosted Dec 21, 2012, 4:33 AM

  Nice,Thank's A Lot
• FM

  Former member13y agoPosted Nov 20, 2012, 2:14 AM

  Thanks a lot
• 

  Nikhil Shekhar14y agoPosted Oct 31, 2012, 3:04 PM

  Nicely written !! Very easy to understand.
• R

  rameshk14y agoPosted Oct 10, 2012, 3:36 PM

  Nice article !!!
• RR

  Raja R14y agoeditedPosted Sep 26, 2012, 8:34 AMEdited Sep 26, 2012, 8:35 AM

  it Was One of the Wonder full Example
• 

  Sukesh Marla14y agoPosted Sep 11, 2012, 2:30 PM

  Thanks Satya
• SP

  Satya Prakash14y agoPosted Sep 11, 2012, 9:30 AM

  good article for understand about design pattern.
• 

  Sukesh Marla14y agoPosted Sep 11, 2012, 7:15 AM

  my pleasure Goyal
• MG

  Megha Goyal14y agoPosted Sep 11, 2012, 4:00 AM

  Good article for the beginners...
• 

  Sukesh Marla14y agoPosted Sep 10, 2012, 11:46 PM

  My thought is as you move towards dynamic things performance reduces, so i prefer switch rather using reflection. Appreciate the suggestion :)
  • 

    Shivanand Arur11y agoPosted Mar 13, 2015, 5:18 AM

    I think using Switch cases as you did in this example is good for small apps or POC's. Whereas in real world enterprise apps, I would suggest to use Reflection instead of using Switch cases. Reason: Using Switch cases in big apps (especially for object creation using Factory Pattern) can violate OCP. According to this example if we add 2 more classes called Grade4 and Grade5 Customers in the Factory, that would require us to add 2 more switch cases and recompile the existing code. And that means we are modifying the existing logic which actually violates OCP. I understand that the intent of your using Switch in this example is for explanation purpose but I am writing this comment so that readers do not get confused. Good luck Sukesh ;)
• AW

  Anson Woo14y agoPosted Sep 10, 2012, 10:41 PM

  Great article! I have one suggestion use Activator.CreateInstance() to replace the switch case for returning the class. So, you don't have to do any modification when you have more kind of Customer(Type). Like: return (IBaseCustomer)Activator.CreateInstance(App.ResourceAssembly.GetName().Name, App.ResourceAssembly.GetName().Name + "." + CustomerType)).Unwrap();