Pscx Resource strings

Topics: Developer Forum
Jan 17, 2007 at 4:58 PM
If we really want to be successful, I think we need to make a big effort with "resourcing" our public string literals. On this note, I think maybe we should split our resx into a few different resx files. I'm not sure if they should be split by component category, or by purpose - perhaps a mix of the two would work.

For generic messages (could be contentious):
  • Warnings.resx
  • Errors.resx

For component specific:
  • IO.resx
  • NET.resx
  • Drawing.resx

etc etc.

Ideally, Verbose, Warning, Error and Informational messages should be resourced for futural localization. WriteDebug is excluded for obvious reasons.


Jan 18, 2007 at 6:02 AM
I could go for the namespace oriented approach. It seems more cohesive than breaking it up warnings, errors, etc.