DEV Community

Cover image for Introduction to C# constants

Introduction to C# constants

carlhugom profile image Carl-Hugo Marcotte Originally published at ・4 min read

In this article, we explore constants.
A constant is a special kind of variable.
The kind that does not vary; they are immutable.

Immutable means that it cannot change.

This article is part of a learn programming series where you need no prior knowledge of programming.
If you want to learn how to program and want to learn it using .NET/C#, this is the right place.
I suggest reading the whole series in order, starting with Creating your first .NET/C# program, but that's not mandatory.

Definition of a constant

Besides knowing that a constant's value cannot change, its value is replaced at compile-time.

On the contrary, variables are evaluated at runtime. Therefore, the program uses the value they hold at the time of their usage during the execution.

To define a constant, we use the const modifier in front of its type, followed by an identifier, an assignment operator, then its value; like this:

const string greetings = "Hello .NET Ninja!";
const int age = 102;
Enter fullscreen mode Exit fullscreen mode

Note: we can't use the var keyword for constants.

Let's look at two use-cases, one using a variable and one using a constant.

Variable flow

In the following code, the value of the greetings variable is transferred to the WriteLine method. It is then written to the console at runtime.

var greetings = "Hello .NET Ninja!";
Enter fullscreen mode Exit fullscreen mode

So if we change the value of the variable along the way, the output will be different; like this:

var greetings = "Hello .NET Ninja!";
greetings = "This is new!"
Enter fullscreen mode Exit fullscreen mode

When executing the preceding code, the program will write two lines to the console, Hello .NET Ninja! and This is new!.
That's because the evaluation is done at runtime.

Next, we look at constants.

Constant flow

In the case of a constant, its value is replaced at compile-time.
Let's take the following code as an example:

const string greetings = "Hello .NET Ninja!";
Enter fullscreen mode Exit fullscreen mode

During the compilation phase, the compiler replaces the identifier of the constant by its value.
In our case, we end up with the following code:

Console.WriteLine("Hello .NET Ninja!");
Enter fullscreen mode Exit fullscreen mode

When executing the program, the result is the same as if we wrote the preceding code ourselves.
The only difference is that the compiler did the job of replacing the value for us.

Next, we look at what we can do with this.

What to do with constants?

As a neophyte, this may sound useless, but as your level of knowledge grows, it becomes more relevant.
In general, constants are used to make your program easier to maintain.
Here are a few examples:

Case 1: you do not want hard-coded values spread throughout your program.
Doing so makes the program harder to maintain when you need to change one of those hard-coded values.
You can also make a typo when typing the value manually.
For example, you need to find the values, make sure you don't forget any, replace them, etc., leading to more risks of making a mistake in the process.
To fix that issue, you can use constants to centralize all of those values in one place, making the program easier to maintain without impact on runtime performance because the constants are replaced at compile-time.

Case 2: you want to reuse a specific value at multiple places in the code as a way to identify something (an identifier, a key, an index, a URL).
Instead of duplicating that literal value, you can use a constant, which removes the duplication by depending only on the constant.
If you need to change the value, you can update the constant, recompile, and voilà; all references to that constant now use the new updated value.

More info: There is a downside to constants, which can happen in a more advanced scenario.
When creating a project(1) that depends on a constant from another project(2), if the author of project(2) changes the value of a constant that project(1) depends on, project(1) needs to be recompiled for the change to be applied.
This could, on rare occasions, have unintended consequences, where different values are used, leading to inconsistent states.

Feel free to return to this note later as it is for more advanced scenarios.
Maybe some or all of this makes no sense to you yet, which is normal.
I decided to leave the note anyway because it is constant-related and important to know.


Unfortunately, I was not able to recreate the exercise on this platform, so please look at the exercise on the original post on my blog. I'm sorry for the inconvenience.


In this article, we learned the constants' syntax.
We covered how to create a constant and how to assign it a value.
Like declaring a variable using the var keyword, we must assign it a value when declaring it.
We cannot use the var keyword for constant and must specify its type instead.
Unlike variables, once the constant is declared, we cannot change its value.

The value of a constant is evaluated and replaced at compile-time, making it a great candidate to improve maintainability while keeping performance the same.
As a reference, variables are evaluated at runtime.

Next step

It is now time to move to the next article: Introduction to C# comments which is coming soon. Stay tuned by following me on, Twitter, or other places you can find me. You can look at my blog contact page for more info.

Discussion (0)

Editor guide