0422 WINCE VS.NET 开发 ActiveSync 模拟器 Emulator Preview activesync

"Microsoft Device Emulator Preview"  Visual Studio 2003 activesync

http://www.shengfang.org/blog/p/0420vsnetwceasimg2.php
0420 WINCE VS.NET 开发 ActiveSync 模拟器 2

利用 Microsoft Device Emulator Preview 开发
感觉这个玩艺是从VS2005分离出来的

运行 Register Device Emulator
运行 Device Emulator Manager
运行 Emulate Smartphone-WM 2003 SE(Cold Boot)
 Device Emulator Manager－－refresh
选择 CSID，右键 －CRSH
这时候 ACTIVESYNC就和模拟器连接了
然后VS2003，运行程序时选择 SP DEVICE，选择设备，不选择模拟器即可

Device Emulator Preview available on Microsoft Betaplace
The Microsoft Device Emulator Preview 1.0 is available on Microsoft Betaplace. This is an open beta for a stand-alone version of the Device Emulator that ships with Visual Studio 2005 Beta 2. The Guest ID is “MSDEVICE” (case is important—it’s all caps). This is an open Beta and we encourage you to use the emulator and provide us feedback in the Device Emulator Forum.

This preview can connect to Visual Studio 2003 and Embedded Visual C++ using Active Sync. This requires that you use start a Device Emulator and run the Device Emulator Manager, then cradle the emulator in the Manager. This will now allow you to create an ActiveSync partnership and use the emulator as you would any other device. Please note that in this case, you deploy to a device, not to the emulator within Visual Studio or eVC.

This is an English-language only beta release. We will not be shipping the beta in any other languages. See the notes on the beta site for installation isntructions and other important notes.

Is it possible to use the device emulator with VS.NET 2003 so that it can directly be called (for connect/deploy ..etc) from the VS.NET 2003 IDE? 
Yes - just use the Device Emulator Manager to cradle an emulator instance, then tell VS.NET 2003 to connect to a hardware device via ActiveSync.

Thanks Barry.

 I am not sure about such option in VS.NET 2003

I have only two available options in VS.NET 2003

1. Tools->Connect to device  which shows Pocket PC 2002 Emulator (Default) and Pocket PC Device. (I would like to configure it to get an an option to connect to Device Emulator)

OR

2. Tools-> Connect Emulator using Activesync which shows - no pocket PC 2003 or Smartphone 2003 Emulators were found. (I would like to configure it to use the Device Emulator)
Barry was talking about the new, ARM-based, emulator which comes with Visual Studio 2005 and is downloadable separately as 'Microsoft Device Emulator 1.0'. To use this in VS.NET 2003, run dvcemumanager.exe from (typically) C:\Program Files\Microsoft Device Emulator\1.0. Select the appropriate image - for the sake of example we'll use 'Pocket PC 2003 SE Emulator' - then choose Actions, Connect from the menu to start the image.

In ActiveSync, go to Connection Settings, and in the 'Allow connections to one of the following' drop-down select DMA. In Device Emulator Manager, keeping the running emulator selected, choose Actions, Cradle. ActiveSync should now connect (assuming you don't have a physical device already connected).

In VS.NET 2003, you can now connect to your emulator by selecting 'Pocket PC Device', just as you would for a physical device.

The VS.NET 2003 emulator is x86-based (using your PC's processor directly), based on technology from Virtual PC. They use a very old 'Virtual PC Application Switch' driver (I believe). XP SP2 disables this driver because it's believed to have problems with No Execute/Execute Disable/Data Execution Prevention (AMD/Intel/Microsoft terminology). If the driver is disabled, IIRC the VS.NET 2003 emulator no longer works.
I m new to using VS2005 for smartphone2003 native development. As it seems I m not very impressed wid its claims of scoring over eVC 4.0. Neways, as I try to deploy any app (even the template for that matter), it shows this error message box--"Failed to open VPC network driver. The driver might not be installed".
MSFT ppl hav any explanation for this behaviour??
I sserched up the forums and got the reason why the error was there. It was because cVC 4.0 SP3 was already installed on my machine. It was preventing the VPC network driver from being installed with whidbey.
  To solve this, (on another machine with eVC installed only) I first uninstalled eVC and then installed VS2005. Thus I got rid of this error. I still dont have a clue how to make both eVC and whidbey run simultaneously. But I doubt why wud anybody want to develop on both IDEs simultaneously.
  So this post can be considered closed.