Aprende Understanding Static Members | Static Classes and Members

When you want certain data or behavior to belong to a class itself, rather than to any individual object created from that class, you use static fields and static methods. Static members are shared across all instances of a class. This means there is only one copy of a static field or method, regardless of how many objects you create. You typically use static members for utility functions, constants, or shared data that should not vary from one object to another. For example, mathematical operations or configuration settings often make sense as static members, since they do not depend on the state of a particular object.

Definition

A static member is a field, property, or method that belongs to the class itself, not to any specific object. Use static members for data or behavior that should be shared across all instances, such as utility functions, constants, or class-wide counters.

MathHelper.cs


              12345678910111213141516171819202122232425262728293031
            
using System;

namespace ConsoleApp
{
    public class MathHelper
    {
        public static int Square(int number)
        {
            return number * number;
        }

        public static double CircleArea(double radius)
        {
            return Math.PI * radius * radius;
        }
    }

    public class Program
    {
        public static void Main(string[] args)
        {
            int value = 5;
            int squared = MathHelper.Square(value);
            double area = MathHelper.CircleArea(3);

            Console.WriteLine("Square of " + value + ": " + squared);
            Console.WriteLine("Area of circle with radius 3: " + area);
        }
    }
}

Notice how the methods in MathHelper are declared as static. You do not need to create an object of MathHelper to use these methods. Instead, you call them directly on the class itself, like MathHelper.Square(5). This is a defining feature of static methods: they are invoked using the class name, not an instance. This makes them ideal for utility operations that do not require any object state.

Counter.cs


              12345678910111213141516
            
// Example: Class with static and instance members (not runnable as a single file)
public class Counter
{
    public static int TotalCount = 0; // Static field
    public int InstanceCount = 0;     // Instance field

    public static void IncrementTotal()
    {
        TotalCount++;
    }

    public void IncrementInstance()
    {
        InstanceCount++;
    }
}

Pros and cons of static members

Pros:

Provide a single shared value or behavior for all instances;
Useful for utility methods or constants that do not require object state;
Can improve performance by avoiding the need to create unnecessary objects.

Cons:

Cannot access instance fields or methods directly;
Overuse can make code less flexible and harder to test;
Shared state can lead to unintended side effects if not managed carefully.

¿Todo estuvo claro?

¡Gracias por tus comentarios!

Sección 3. Capítulo 1

Pregunte a AI

Pregunte lo que quiera o pruebe una de las preguntas sugeridas para comenzar nuestra charla

Suggested prompts:

Can you give more examples of when to use static members?

What are some best practices for using static fields and methods?

How do static members differ from instance members in practice?

Desliza para mostrar el menú

Definition

MathHelper.cs


              12345678910111213141516171819202122232425262728293031
            
using System;

namespace ConsoleApp
{
    public class MathHelper
    {
        public static int Square(int number)
        {
            return number * number;
        }

        public static double CircleArea(double radius)
        {
            return Math.PI * radius * radius;
        }
    }

    public class Program
    {
        public static void Main(string[] args)
        {
            int value = 5;
            int squared = MathHelper.Square(value);
            double area = MathHelper.CircleArea(3);

            Console.WriteLine("Square of " + value + ": " + squared);
            Console.WriteLine("Area of circle with radius 3: " + area);
        }
    }
}

Counter.cs


              12345678910111213141516
            
// Example: Class with static and instance members (not runnable as a single file)
public class Counter
{
    public static int TotalCount = 0; // Static field
    public int InstanceCount = 0;     // Instance field

    public static void IncrementTotal()
    {
        TotalCount++;
    }

    public void IncrementInstance()
    {
        InstanceCount++;
    }
}

Pros and cons of static members

Pros:

Provide a single shared value or behavior for all instances;
Useful for utility methods or constants that do not require object state;
Can improve performance by avoiding the need to create unnecessary objects.

Cons:

Cannot access instance fields or methods directly;
Overuse can make code less flexible and harder to test;
Shared state can lead to unintended side effects if not managed carefully.

¿Todo estuvo claro?

¡Gracias por tus comentarios!

Sección 3. Capítulo 1

Understanding Static Members

Pros and cons of static members

1. What is a static method?

2. How do you call a static method in C#?

3. Can static methods access instance fields?

Understanding Static Members

Pros and cons of static members

1. What is a static method?

2. How do you call a static method in C#?

3. Can static methods access instance fields?