Можно ли использовать стандарты 4.0 под EVC ++ для отладки на удаленном устройстве?

Question

я бегу Встроенный визуальный C ++ 4 с Сервисный пакет 4, чтобы разработать приложение для устройства, работающего CE 5.0. Я использую CE 5.0 SDK Для этой цели, которая работает нормально, за исключением того факта, что, хотя оно будет нацелено на мое устройство (то есть КПК на основе SH4), он не позволит мне выбрать что -либо, кроме эмулятора STANDARDSDK для отладки. Если я пойду в Инструменты / настройка менеджера платформы, Я могу подключиться к своему устройству под платформой по умолчанию Windows CE, но я не могу выбрать его на панели инструментов Build в целях вывода и отладки. Есть ли какая -то работа по этому поводу. Я подумал о переходе на VS2008 для этого приложения, но оно нарушает большое количество 3 -го кода.

Answer 1

Embedded Visual C++ and "Platform Builder" are different tools. The "Windows CE" SDKs are designed to work with "Platform Builder" to make things like OSes and drivers. However, Applications generally use the "Windows Mobile" or "Pocket PC" SDKs.

So here are three different solutions:

Continue to use EVC++ 4.0

If you want to keep using Embedded Visual C++ 4.0 instead of one of the newer IDEs, you can use "SDK for Windows Mobile 2003-based Pocket PCs". Which I believe is the newest SDK for EVC++ 4.0.

Upgrade to VS2005+

This details how to migrate from EVC++ to VS2005 while still making native apps.

You can use the 5.0 SDK line of features in the "Windows Mobile 5.0 SDK for Pocket PC"

Use Windows CE SDK to make Applications with EVC++ 4.0

It actually is possible to make Applications using a CE SDK. This is used by OS developers to make applications for their OS.

You can develop an application using Microsoft® eMbedded Visual C++® together with Platform Builder. Before you can develop an application, you must use Microsoft Platform Builder to create an OS design, build a run-time image, and then download the run-time image to the target device.

When you download a run-time image, Platform Builder uses a download service to copy the run-time image to the target device. When the run-time image runs, Platform Builder communicates with the target device over a kernel transport.

To develop an application, keep Platform Builder connected to the target device, and then run eMbedded Visual C++. After you write, compile, and run the application, eMbedded Visual C++ uses the established connection to run the application on the target device.

Note The previously mentioned process differs from the process used to develop an application for a run-time image not downloaded by Platform Builder. When you do not use Platform Builder, you manually connect to the target device using the application connectivity communications framework of Platform Manager. For more information about application connectivity, see Application Connectivity. -- http://msdn.microsoft.com/en-us/library/ms859575.aspx