Running the Checkv4 Utility (Windows CE 5.0)
The Microsoft Checkv4 utility enables you to find potentially conversion-sensitive code in your application's socket-level programming. This utility identifies potential issues, highlights code that could benefit from IPv6-capable functions or structures, and recommends a method for resolving the issues.
Note Most Windows Sockets (Winsock) 2.2 functions support IPv6 addresses. Checkv4 identifies those that do not support IPv6.
The Checkv4 utility documentation includes tips about the order in which to address IPv6-enabling issues. This is the order in which to approach the conversion process in your applications.
As an example, in this procedure, you will use the IPv4-only Client Code as shown in IPv4-only Client Code.
For more information about using the Checkv4 utility, see this Microsoft Web site , and then search for "Using the Checkv4.exe Utility."
To run the Checkv4 utility
- On your development workstation, copy the Checkv4 utility from %_WINCEROOT%\SDK\bin\i386 and put it in the same directory as your application, %_WINCEROOT%\PBWorkspaces\<OS design name>\<SimpleClient or Simple Server>.
- In Platform Builder, from the Build OS menu, choose Open Release Directory.
- At the command prompt, browse to %_WINCEROOT%\PBWorkspaces\<OS design name>\<SimpleClient or SimpleServer>.
- At the command prompt, type one of the following:
Checkv4 parses the information into the file (ch4client.txt or chrserver.txt).
- To view the checkv4 output for the file, at the command prompt, type one of the following:
Checkv4 output that contains IPv6 conversion issues is displayed in Notepad. You will use this information to change your code to support IPv6.
Next, you must change your code to support IPv6 as described in Changing the Application Source Code to Support IPv6.
Send Feedback on this topic to the authors