Skip to main content

VBA versus .NET

Factory Method

Following is an example of the Factory Method.  In this case, a method call sets and returns the type.  Also, pardon the values set as field, rather than as properties, but this is a simple example, rather than a full implementation.


Salient Point(s)


  • A hidden constructor
  • Each class method instantiates the class differently.


Code




using System;


namespace DesignPatterns
{   
    //primary class for factory method
    public class FactoryObject
    {
        //public fields, set as part of method and return
        public int X;
        public int Y;
        public int Result;


        //factory method
        public FactoryObject Addition(int x, int y)
        {
            return new FactoryObject(x, y, x + y);
        }


        //factory method
        public FactoryObject Subtaction(int x, int y)
        {
            return new FactoryObject(x, y, x - y);
        }


        //factory method
        public FactoryObject Multiplication(int x, int y)
        {
            return new FactoryObject(x, y, x * y);
        }


        //factory method
        public FactoryObject Division(int x, int y)
        {
            return new FactoryObject(x, y, (y == 0) ? 0 : (x / y));
        }


        //constructor is private
        //object is returned via factory methods
        private FactoryObject(int x, int y, int result)
        {
            this.X = x;
            this.Y = y;
            this.Result = result;
        }
    }
}

Comments

Popular posts from this blog

Decorator Pattern

This is an example of the Decorator pattern, in this case a decorator for ObservableCollection.  Working with WPF and ObservableCollection using threads, one will run into the problem whereby the ObservableCollection cannot be updated from outside the owning thread; Delegates and Invoke will not work. A solution is to contain and expand the class, as is done in this example on michIG's Blog . This linked file contains the original code in C#, as well as the same code converted to VB.NET. Salient Characteristic(s) Sets an internal pointer to the decorated object, sending method calls and property actions to the internal object Extends the object by wrapping it and adding some aspect handled by the decorator Code using System; using System.Collections.ObjectModel; using System.Windows.Threading; using System.Collections.Specialized; using System.ComponentModel; namespace DesignPatterns {     /// <summary>       /// This class is an...

James Igoe's Reviews > Thinking Architecturally

Thinking Architecturally by Nathaniel Schutta My rating: 4 of 5 stars An overview of architectural decisions, the politics and persuasion involved, and the needs to balance competing measures and attributes. A fairly easy read, but full of great suggestions, and, for many, reminders of how to handle being a senior developer or architect. View all my reviews

VBA versus .NET

I was recently messaged by someone on LinkedIn, and since my response seemed full enough, I thought I'd share. Question I see that you also program in VBA but you have made the jump to .NET. Unfortunately, I have found C#/Excel coding to be quite slow and just wanted to hear about your experiences. Responses Slow? It depends on what you mean. Honest, I have had to make the pitch when building apps that it should be in .NET rather than VBA for speed. One particular app had a form that needed to fill about 20 dropdowns on load, so using async operations was essential. That same app, while executing one SQL statement in the foreground, also executed 2 background statements that filled panels. It wouldn't have performed well if done in VBA. If you mean that it takes longer, then yes, but that is a necessity for good code anyway. If you only need a local operation, non-threaded, that doesn't need to be used across the enterprise, VBA can make sense, but with .NET comes n...