Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
4/8/2010

DeviceInfo is a Win32 Desktop component that demontrates the use of IRAPI interfaces to get information about the Windows ®phone connected through ActiveSync and the corresponding communication medium used. Once the information is collected, it is printed on the console window

Feature Area

Relevant APIs

Usage

To run the code sample

  1. Open the project file in Visual Studio. It is located in the folder C:\Program Files\Windows Mobile 6.5.3 DTK\samples\common\CPP\Win32\Rapi\DeviceInfo\DeviceInfo.sln

  2. Navigate to "Tools" -> "Options", and expand "Projects and Solutions" and click "VC++ Directories".

  3. In "Show directories for:" select "Include files".

  4. Add the path to the mobile device include directory. If you accepted the defaults when installing the Windows Mobile SDK, then the new directory will be in " C:\Program Files\Windows Mobile 6.5.3 DTK\Activesync\Inc"

  5. In "Show directories for:" select "Library files".

  6. Add the path to the mobile device library directory. If you accepted the defaults when installing the Windows Mobile SDK, then the new directory will be in " C:\Program Files\Windows Mobile 6.5.3 DTK\Activesync\Lib"

  7. Navigate to "Build", and click "ReBuild All" to compile the executable file.

  8. From a command line, run DeviceInfo.exe while a device is connected

Development Environments

SDK:Windows Mobile Professional SDK and Windows Mobile Standard SDK

Development Environment:Visual Studio 2005 or 2008.

ActiveSync:Version 4.5.

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.