Running the Checkv4 Utility (Windows Embedded CE 6.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.
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.
You can obtain the Checkv4 utility from the IPv6 Technology Preview, available for download at this Microsoft Web site. For more information about using the Checkv4 utility, see this Microsoft Web site.
To run the Checkv4 utility
Obtain the Checkv4 utility.
On your development workstation, put the Checkv4 utility in the same directory as your application, %_WINCEROOT%\PBWorkspaces\<OS design name>\<SimpleClient or Simple Server>.
In Platform Builder, on the Build menu, choose Open Release Directory in Build Window.
At the command prompt, navigate to %_WINCEROOT%\OSDesigns\<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:
Notepad displays Checkv4 output that contains IPv6 conversion issues. 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.