While resx files have the sometimes useful ability to store different versions of files for different languages in programs with multilingual support, not only is most data we have in resx files not user-facing text, but we don't support any other languages anyway.
Everything that isn't text that might one day be localized should be pulled out of the resx files. A much simpler option is to simply mark the files as embedded resources in the solution explorer and they'll be automatically imported. However, this will require some code changes as the method to load embedded resource files isn't quite the same as loading files from resx (for an example, in the music library redesign I moved the music library files out of resx, showing the differences in code necessary to load them).
While resx files have the sometimes useful ability to store different versions of files for different languages in programs with multilingual support, not only is most data we have in resx files not user-facing text, but we don't support any other languages anyway.
Everything that isn't text that might one day be localized should be pulled out of the resx files. A much simpler option is to simply mark the files as embedded resources in the solution explorer and they'll be automatically imported. However, this will require some code changes as the method to load embedded resource files isn't quite the same as loading files from resx (for an example, in the music library redesign I moved the music library files out of resx, showing the differences in code necessary to load them).