ust to be sure what shows up, I built an OS and a SDK and tried creating a
managed code application. You're correct that the SDK name does not appear
as a target OS when you create a new project. As I indicated before, use
Windows CE 5.0 or one of the Windows Mobile targets, whichever will give you
the best match for your device.
You can target the emulator from your managed code project directly by
specifying the device emulator for your target build. It should show up in
the list where CE Emulator, CE Device, etc. appear. It might be something
like MyProjectSDK Emulator in the list. If you do that, when you hit Run to
run the managed code, an instance of the emulator will be launched with your
emulation (from the SDK), OS in it. The application will then be downloaded
You can also target the emulator being run from VS2005/Platform Builder (if
you want to debug some low-level OS thing that causes problems for your
application, maybe). To do that, use a Platform Builder instance of VS2005
to launch the emulator OS (Target | Connect). Once that's up and running,
you can use a second instance of VS2005, with the managed code program
loaded, to deploy the program and debug it by selecting CE Emulator as the
target device. This will connect the managed code instance of VS2005 to the
currently-running emulator launched by Platform Builder. I would suppose
that you could do this all from a single instance of PB, too, if you
inserted the managed code project as a subproject in the OS solution, but I
didn't try that.
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT
com> wrote in message news: XXXX@XXXXX.COM ...