Skip to main content

VBA versus .NET

Post a Comment

Builder

Below is a fairly straightforward 'fill-in-the-blanks' example of a Builder design pattern:

 Salient Characteristic(s)

  • Defines a base type
  • Defers creation of type to derived types
Code

 using System;

 namespace DesignPatterns
{
    //the type of object to be built by the specific builders
    public class BuilderObject
    {
        public string Property1 = string.Empty;
        public string Property2 = string.Empty;
        public string Property3 = string.Empty;
    }

     abstract class Builder
    {
        //protected object to be built
        protected BuilderObject _Object;

         //method to return object
        public BuilderObject GetBuilder()
        {
            return _Object;
        }

         //method to create object
        public void BuildObject()
        {
            _Object = new BuilderObject();
        }

         //public abstract method(s) for building object
        //derived classes will implement
        public abstract void BuildMethod1();
        public abstract void BuildMethod2();
        public abstract void BuildMethod3();
    }

     //class 1 of n that inherits Builder class
    //and overrides each abstract method for building
    class Builder1 : Builder
    {
        public override void BuildMethod1()
        {
            //
        }
       
        public override void BuildMethod2()
        {
            //
        }

         public override void BuildMethod3()
        {
            //
        }
    }

     //class 2 of n that inherits Builder class
    //and overrides each abstract method for building
    class Builder2 : Builder
    {
        public override void BuildMethod1()
        {
            //
        }

         public override void BuildMethod2()
        {
            //
        }

         public override void BuildMethod3()
        {
            //
        }
    }

     //director class that accepts builder type (from inherited builder base type)
    class Director
    {
        private Builder _Builder;

         public Director(Builder builder)
        {
            _Builder = builder;
        }

         public Builder CreateBuilderObject()
        {
            _Builder.BuildMethod1();
            _Builder.BuildMethod2();
            _Builder.BuildMethod3();

             return _Builder;
        }
    }

     class Start
    {
        public Start()
        {
            Builder builderExample = new Builder1();
            builderExample.BuildObject();
            BuilderObject newBuilder1Object = builderExample.GetBuilder();
        }
    }
}

Comments

Post a Comment

Popular posts from this blog

Do Algorithms Make You a Better Developer?

Responding to a question on HashNode, Developers who practise algorithms are better at software development than people who just do development. Is it true? , I wrote the following: My feeling is that algorithms help make one a better programmer, but that is likely true of many coding concepts. I did not have algorithms as an undergraduate, so my knowledge is acquired through reading and practice, but after reading and applying Algorithm's in a Nutshell, I felt the quality of my work improved. That said, my development work increased more after understanding Design Patterns, or after consuming books on database design.  Since many types of knowledge improve developing and architecting abilities, one has to consider how it helps and to what degree. Algorithms are coding-in-the-small, often narrowly focused solutions, but which can have a great impact at scale. For many applications, a focus on algorithms would be overkill as data sets and requirements do not require it. In this ...
Post a Comment
Read more

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...
Post a Comment
Read more

How do you deal with making sure your use of new technology is correct and free from code-smells, security issues, etc.? - Hashnode

Responding to How do you deal with making sure your use of new technology is correct and free from code-smells, security issues, etc.? : Issues can be dealt with in several ways. Understanding what makes high-quality, maintainable code would be first, so knowledge of best practices regarding OOP, SOLID, design patterns, API design, etc. is important. Depending on what you mean by security, best practices in those regarding transfer protocols, coding styles, validation, storage, etc. are equally something one can learn. Planning your work is useful, as a well thought out design is easier to implement, or at least will avoid future problems, than when you are just 'winging it'. Diagramming and project plans can be useful at this stage. Self-management is part of this, so using boards and epic/stories/tasks to track work is important, and there are free tools like Visual Studio Team Services (VSTS) or Trello to help. Requirements gathering will matter so documentation and c...
Post a Comment
Read more