How does the ResMe
string extractor make it easy to use a resource file in my project?
ResMe searches for all the hard-coded strings in a project's source code, creates
a .RES file containing all the program's strings, and modifies the source code by
replacing the string with a LoadResString() reference to the correct string in the
Will my source code be
No, your original project will not be modified. A copy of your project will be
made and its source code will be modified. You will be able to compare the new resource
based version of your project against the original project with hard-coded strings.
What about strings that
don't belong in a resource file?
There are pre-defined and user-defined keywords and
phrases that are used to prevent special strings from being relocated to the resource
file. In addition, there are syntax checks that are also used to prevent inappropriate
usage of resource strings.
Can I manually decide which
strings should or should be moved into the resource file?
In most cases, yes, you can specify how each
string should be treated. There are some contexts that will force a string into or out
of a resource file.
Are there other reasons why
a string would be forced into the resource file?
If a string was imported from an existing .RES file, then the ResMe String
Extractor will not allow the string to be removed from the resource file. Removing an
existing string would cause a compiler error unless the programmer modifies the program.
Why would a string be
forced out of the resource file?
If a string is used in certain programmatic ways, then the ResMe String Extractor
will not allow the string to be moved to the resource file. Placing some certain programmatically used strings in the resource file would cause a compiler error. Some DLL,
PropertyBag commands, and Err.Raise are a few examples.
Can I edit the strings to
make corrections during the string extraction process?
Yes, it is possible to edit any resource string
and you can view how the string is used throughout the project.
What versions of Visual
BasicÒ are supported by the ResMe String Extractor?
All 32-bit versions of Visual BasicÒ are supported. This includes versions 4.0, 5.0 and
6.0. VB 4.0 16-bit projects are also supported except only ResMe Enterprise will import
strings from existing 16-bit Resource Files.
What if I have a 16-bit
Resource file from Visual BasicÒ 4.0?
The Enterprise version of ResMe will convert your 16-bit Resource file into a
32-bit Resource file and add any new extracted strings to the 32-bit Resource file.
What if a file in my
project is shared with another project?
This is a sticky issue because the resource assignments of strings for a file will
be different across multiple projects. The best advice in this case is to maintain one
non-resource based version of the file in source control and incorporate the ResMe String
Extractor into your build process.
Is is possible to fully
automate the string extraction process?
It depends! A great deal of built in intelligence has been provided to help
minimize the accidental selection of inappropriate strings and to help maximize the
extraction of strings associated with the user interface. However, it is important to
review which string have been selected and omitted from
the resource file. Once a project has been reviewed and 'Do Not Localize' comments have
been added when necessary, then it is possible to fully automate the string extraction
process with command line processing .
Can I prevent some project
files from being processed while processing the others?
Yes, it is possible to individually specify which
files should not have their strings extracted and moved to a resource file.
How are string constants
that I declare handled since they cannot use LoadResString()?
It is possible to ignore or to convert string Const assignments. Module level string constants are converted into into a
read-only property and local string constants
are converted into standard strings.
What problems can occur
from using a resource file?
There are a few small errors that could be introduced by
either using resource files or form the ResMe String Extractor utility.