The problem with your request is that you haven't defined what "all over the
place" means. You're looking for a tool that does exactly what? You have
stated that "the powers that be decided to simply throw static strings in
the .Net code." That doesn't tell us much. A tool to extract static strings
from code and put them into resource files would have to know how to
identify what these "static strings" you're talking about are, what
identifies these from any other strings defined in your code. And I don't
think you're going to find one ready-made.
I would suggest that you figure out for yourself how an application could
identify all these "static strings" and write your own solution, or do the
work by hand if you figure it will take more time to automate (since this is
a one-time change).
--
HTH,
Kevin Spencer
Microsoft MVP
Chicken Salad Surgery
It takes a tough man to make a tender chicken salad.
"Sam Carleton" <sc*******@gmail.comwrote in message
news:11**********************@75g2000cwc.googlegro ups.com...
>
AMercer wrote:
I am now many months into a project where the powers that be decided to
simply throw static strings in the .Net code. Does anyone know of a
tool that will pull out the strings, and put them into some type of
resource file and ultimately assist us in managing all the strings?
I don't know of any such tool. Why do the strings in your project need
managing? Maybe your objectives can be met by something other than
centralization.
We have static strings all over the place that are going to be
displayed. It would be nice if they where centralized so that the
documentation department can get a simple list of all the string and
word smith them for development. It would also making going
international much easier, too.