localization/globalization through sqlite

An additional thought about mixed resource usage [resx., SQLite, etc.].

Such scenario is ideal for constructing a generic resource facility inside the application:

- for a given functionality(*) of the application proper, declare an interface that contains all required property and method signatures

- implement the interface by a class that performs resource access to the resource in a more or less optimal manner

- such class can be optimized as you produce more advanced versions of your application [e.g.: with or without data caching, accessing data on a server vs. locally]



In this way, over the life of your application, you can better abstract resource access implementation/plumbing considerations from the rest of your code.

(*) access culture dependent labels; access culture dependent 'complex' text; other ...