Home/ Questions/Q 7686869
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-31T19:34:39+00:00

I adh some constants in my project. private const int refercePosition = 0.3; I

  • 0

I adh some constants in my project.

private const int refercePosition = 0.3;

I shifted the constants to the Settings file of my project (i.e into App.config) and using now in my project as.

private static int refPos = Properties.Settings.Default.referencePosition;

Is this a good practice to decalre the variable as static instead of constant?
There are approximately 10 other constants in my project which which I did the same.

BTW, since App.config variables are runtime configurable but does declaring a variable as static defeat that purpose?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It is not a drop in replacement since now refPos can be modified during runtime. If that is your purpose that is fine, otherwise 

    private static readonly int refPos = Properties.Settings.Default.referencePosition;

    makes refPos readonly during runtime. More close to the nature of a const.

    You may also want to look at the singleton pattern.

    • 0