Skip to main content

Design Patterns - Abstract Factory Pattern

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace DesignPattern_AbstractFactoryApp
{
   class Program
   {
      static void Main(string[] args)
      {
         /* ABSTRACT FACTORY PATTERN:
          * The abstract factory pattern provides a way to 
          * encapsulate a group of individual factories 
          * that have a common theme without 
          * specifying their concrete classes.
          * Use of this pattern makes it possible to 
          * interchange concrete implementations 
          * without changing the code 
          * that uses them, even at runtime. 
          * However, employment of this pattern, 
          * as with similar design patterns, 
          * may result in unnecessary complexity 
          * and extra work in the initial writing of code
          */

         var samsungSmartPhone = new GenericFactory<SamsungSmartPhone>();
         SmartPhone smartPhone1 = new SamsungSmartPhone();
         samsungSmartPhone.CreateInstance().TestSmartPhone(smartPhone1);

         var appleSmartPhone = new GenericFactory<AppleSmartPhone>();
         SmartPhone smartPhone2 = new SamsungSmartPhone();
         appleSmartPhone.CreateInstance().TestSmartPhone(smartPhone2);

         Console.ReadKey();
      }
   }
}

**************
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace DesignPattern_AbstractFactoryApp
{
   public class GenericFactory<T>
      where T : new()
   {
      public T CreateInstance()
      {
         return new T();
      }
   }
}


**************
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace DesignPattern_AbstractFactoryApp
{
   public abstract class PhoneFactory
   {
      public abstract SmartPhone CreateSmartPhone();
      public abstract DummyPhone CreateDummyPhone();
   }
}

**************
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;

namespace DesignPattern_AbstractFactoryApp
{
   public abstract class SmartPhone
   {
      public abstract void TestSmartPhone(SmartPhone phone);
   }
}

**************

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;

namespace DesignPattern_AbstractFactoryApp
{
   public abstract class DummyPhone
   {
      public abstract void TestDummyPhone(DummyPhone phone);
   }
}

**************
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace DesignPattern_AbstractFactoryApp
{
   public class AppleFactory : PhoneFactory
   {
      public override SmartPhone CreateSmartPhone()
      {
         return new AppleSmartPhone();
      }

      public override DummyPhone CreateDummyPhone()
      {
         return new AppleDummyPhone();
      }
   }
}

**************
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;

namespace DesignPattern_AbstractFactoryApp
{
   class AppleSmartPhone : SmartPhone
   {
      public override void TestSmartPhone(SmartPhone phone)
      {
         Console.WriteLine("Apple Smart: " + phone.GetType().Name);
      }
   }
}

**************
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;

namespace DesignPattern_AbstractFactoryApp
{
   class AppleDummyPhone : DummyPhone
   {
      public override void TestDummyPhone(DummyPhone phone)
      {
         Console.WriteLine("Apple Dummy: " + phone.GetType().Name);
      }
   }
}

**************
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace DesignPattern_AbstractFactoryApp
{
   class SamsungFactory:PhoneFactory
   {
      public override SmartPhone CreateSmartPhone()
      {
         return new SamsungSmartPhone();
      }

      public override DummyPhone CreateDummyPhone()
      {
         return new SamsungDummyPhone();
      }
   }
}

**************
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;

namespace DesignPattern_AbstractFactoryApp
{
   class SamsungSmartPhone : SmartPhone
   {
      public override void TestSmartPhone(SmartPhone phone)
      {
         Console.WriteLine("Samsung Smart: " + phone.GetType().Name);
      }
   }
}

**************
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;

namespace DesignPattern_AbstractFactoryApp
{
   class SamsungDummyPhone:DummyPhone
   {
      public override void TestDummyPhone(DummyPhone phone)
      {
         Console.WriteLine("Samsung Dummy: " + phone.GetType().Name);
      }
   }
}


Comments

Popular posts from this blog

How to fix Git push error: "RPC failed; curl 56 HTTP/2 stream 7 was reset send-pack: unexpected disconnect while reading sideband packet fatal: the remote end hung up unexpectedly"

Problem Today I saw the following problem when I tried to push my changes to a Git server after doing some work for upgrading an Umbraco v7 project to v8.18.8.  Possible reasons After some investigations, it seems like this could be because of the following reasons; Git is not happy with the amount of changes that are being pushed into the server.  There are possible limitations on the server about the size/amount of files that you can push. Your internet connection is not good and stable enough. Your Git client's version is old. Solution options For me, the easiest option was connecting to another Wifi and trying again. Apparently, this option helped quite a few people, so it is worth giving it a try. Unfortunately, it didn't work for me. A bad internet connection wasn't an option for me either, as my internet is pretty fast (500 Mbps). Similarly, my Git client version was the latest version (git version 2.41.0.windows.3).  On StackOverflow, there were a lot of recommendat

How to use JQuery Ajax Methods for Async ASP.NET MVC Action Methods

Making repeatedly calls to async methods can be a nightmare. In this case, it makes sense to use 2 ajax methods, instead of one. Here is a simple solution to overcome this problem. See that  ajaxcalls   is emptied after the success response for the first ajax call and then the second ajax method is used to make one single call to the async action method. Hope it helps. View: @section Scripts{     < script type ="text/javascript">         var smartDebitObject = new Object();         smartDebitObject.MembershipNumber = $( "#MembershipNumber" ).val();         smartDebitObject.ProfileId = $( "#ProfileId" ).val();         smartDebitObject.FirstName = $( "#FirstName" ).val();         smartDebitObject.LastName = $( "#LastName" ).val();         smartDebitObject.AddressLine1 = $( "#AddressLine1" ).val();         smartDebitObject.Postcode = $( "#Postcode" ).val();         smartDebitObject

How to fix "Microsoft SQL Error SQL71564: Error validating element [USERNAME]: The element [USERNAME] has been orphaned from its login and cannot be deployed."

I needed to export a database in BACPAC format today in order to restore it somewhere else, and I encountered the following error. To resolve this issue, I deleted all of the users mentioned in the error log. After successfully creating the BACPAC file, I used it to create a new database with no problems. Error: TITLE: Microsoft SQL Server Management Studio ------------------------------ One or more unsupported elements were found in the schema used as part of a data package. Error SQL71564: Error validating element [USER1]: The element [USER1] has been orphaned from its login and cannot be deployed. Error SQL71564: Error validating element [USER2]: The element [USER2] has been orphaned from its login and cannot be deployed. Error SQL71564: Error validating element [USER3]: The element [USER3] has been orphaned from its login and cannot be deployed. Error SQL71564: Error validating element [USER4]: The element [USER4] has been orphaned from its login and cannot be deployed. Error SQL71