Resource File vs Static Class for values ​​that should not be localized in C #

Question

I overheard my two colleagues discussing this topic, and I was wondering what a general idea is.

Currently, in our application we use many pairs of key values, and they are looking for the best way to implement a solution that will allow us not to forget about writing the key.

Answer 1

The resource file generates a static class behind the scenes to access these resources, so you end up with the same thing. It's simple if you use a resource file, and one day you decide to localize, you are good to go. Of course, there is no definite answer to this question. It looks like subjective to me, since both solutions are quite viable.