The VB.NET client is supplied as a collection of source files and compiled modules that, when compiled, make up a client application that can access and display Ispecs from the runtime system.
It is primarily a starting point for you to create your own, customized VB.NET application. It is not intended as a "turn-key" solution for accessing the runtime system. However, the VB.NET client is a viable application in its own right to access the runtime system.
To begin using the VB.NET client, the project files should be copied from the <CE Installation directory>VB.NET Client/glue files directory to a new directory.
The files in that directory are listed in the following table:
| File Name | Description |
|---|---|
| VBdotNETContainer.vbproj | The VB.NET project file. |
| MainFrame.vb | The main form in the VB.NET client. |
| ConfigDotXML.vb | A class for reading the config.xml file. |
| Logging.vb | A class to allow simple access to the CE logging file. |
| CommandConsole.vb | A form to simulate a console to the runtime. |
| SelectCommand.vb | A form to allow choosing of colon commands. |
| ReportDialog.vb | A form to allow the choosing of reports to run. |
| AssemblyInfo.vb | A class with information on how to make a .NET Assembly for the project. |
| About.vb | A form with version information on the client. |
| Globals.vb | A file with global variable definitions. |
| Config.xml | An example of the config file that is read by the client. |
| VBdotNET Container.Strings.resx | A 'string table' containing all error messages and menu strings used by the VB.NET client. |
| Localization.txt | A text file with instructions for localizing the string table. It is possible to have the one executable display in different languages in the one session. |