After the conversion is finished a log is generated which shows success or failure
for each form and all the controls on each form. This log can be viewed in
the grid, printed or exported to Excel for additional processing.
This step of the process shows each dialog and view in the resource file.
You
have the option of including or excluding any of the dialogs or views
in the progect.
For each form we will generate a .cs or .vb file and
a corrsponding .resx file. In 2005 format we will also generate a *.designer.cs
or *.designer.vb file.
We display a grid of the resource file's strings and their IDs. Both the string
name and the string text can be edited. The strings can be individually selected
for inclusion in the project. The selected strings will be appended to the string resource
file that was selected on step 2. If the string resource file
does not exist, it will be created.
This screen allows the selection of the .NET programming language and the version which
you would like to use for the converted forms. C# and VB .NET are the
supported languages for both Framework 1.1 and Framework 2.0 (Visual Studio 2003
or 2005)and C++/CLI is supported for Framework 2.0 (Visual Studio 2005) only.
We provide default scaling factors for the control size and location, but these
can be adjusted as needed.
The prefix and suffix of the class name can be selected. The class name is
generated from the prefix and suffix and the form or dialog ID. The rule followed
is similiar to that for control names. In generating the form name, the current
prefix will be removed, any underscores in the existing ID will be removed, the
initial letter after any underscores will be capitalized and the remaining letters
will be in lower case. For example, IDD_ABOUTBOX becomes frmAboutbox.
Select a namespace for the .NET forms and a prefix and/or suffix for menu item names.
You also have the option to keep your existing dialog and control names, though
this is not recommended.
Next select the directory where the .NET files will be generated. Also, select
the file where the string resources will be stored. If the string resource
file does not exist, it will be created.
Here you can also enforce naming conventions for the controls, as you can select prefixes for each control type.
The rule followed in generating the control name is that the current prefix will
be removed, any underscores in the existing ID will be removed, the initial letter
after any underscores will be capitalized and the remaining letters will be in lower
case. For example, if the control ID is currently, IDC_MY_BOX, and the prefix
entered is edit, the .NET control name will become editMyBox.
The first step is to choose the resource file you would like to convert.
You can choose any valid MFC/ATL resource file.
It is not required to have an extension of '.rc' .
You can press F1 on any field to get help for that field. Pressing the Help
button on the bottom right will bring up the Help file with more extensive help.