Download and Install the Utility

The conversion utility is called Microsoft Java to .NET Framework conversion utility. It can be downloaded from

http://www.microsoft.com/downloads/details.aspx?FamilyID=46bea47e-d47f-4349-9b4f904b0a973174&DisplayLang=en

Version 2.0 of the utility is adequate for a Field Translator. Run the downloaded .exe file to install it into Visual Studio.

The conversion utility works on a directory of java files, so you should copy your Field Translator java file to a new, empty directory.

To run the utility, perform the following:

  1. Start Visual Studio without opening a project or solution, and from the File menu, choose Open then Convert.

  2. From the list of available converters, select the 'Java Language Conversion Assistant'.

  3. Select the Create a new solution radio button.

  4. Click OK to start the conversion Wizard, then click Next on the startup screen to display the Source Files page of the Java Language Conversion Assistant Wizard.

  5. Select the 'A directory containing the projects files.' radio button and click Next to display the Select source directory page of the wizard.

  6. Enter, or browse for, the directory into which you copied your Field Translator, then click Next to display the Configure your new project page of the wizard.

  7. Give the project the same name as your Field Translator.

    For example, FieldTranslator_en_AU_MCP

    The 'additional' files edit box should already display your CLASSPATH. If not, enter the location of LINCApplet.jar.

  8. Set the Appropriate Project Type to class library, then click Next to display the “Specify a directory for your new project” page.

  9. Enter, or browse for, a location to store your new .NET Framework Field Translator solution and project, then click Next to display the “Begin your conversion” page.

  10. Click OK to create the new directory, if required, then Next to begin the conversion.

At the end of the conversion, you are presented with a conversion report. There might be some warnings about changing primitive types. These can be ignored as they can be fixed in the next step.