Resource File vs Static Class for values that will not need to be localized in C#

I overheard two of my coworkers debating this topic and I was wondering what the general thought is.

Right now in our application we use a lot of key value 开发者_开发知识库pairs and they are looking for the best way to implement a solution that would avoid us to remember the spelling for the key.

A resource file generates static class behind the scenes to access those resources so you end up basically with the same thing. It's just that 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. Looks subjective to me as both solutions are perfectly viable.