Connecting to the Device Emulator
Use the direct memory access (DMA) transport that Visual Studio provides for connecting to the Device Emulator. This transport eliminates most connection issues between the development computer and the emulator.
.gif) Important Note: |
|---|
Use the TCP/IP transport only if you have a specific reason. To resolve issues that stem from the use of TCP/IP with the emulator, review the steps that follow. For more information, see the
Mobile Developer Center.
|
Failed to Open Virtual Switch Driver
If you are trying to connect the Device Emulator to a network by using the emulated NE2000 or CS8900 card, you need a virtual switch driver. You can download a driver from the Mobile Developer Center.
An error opening the driver can occur for several reasons:
Lack of driver.
The network card on the development computer does not have the driver installed.
There were problems during the installation of the driver.
The driver is in a disabled state.
The development computer does not have a network card.
Use the following steps to diagnose the precise cause.
To diagnose the precise cause of the failure
Look on the Network tab of the Emulator Properties dialog box.
If the NE2000 and/or the CS8900 cards are enabled, verify that the network cards to which they are bound are present and connected. To open the Emulator Properties dialog box, click Configure on the File menu of the Device Emulator.
Look at the network properties of the adapter to verify that the item Virtual Machine Network Services is present, enabled, and of the correct version, which is 2.6.465.224 or later versions.
If these steps do not fix the problem, reinstall the driver.
Deployment to Emulator Error
If your development computer has a wireless network connection and you are using the TCP transport, you might need additional steps, such as installing the Microsoft Loopback Adapter. For more information, see the Mobile Developer Center.
.gif) Note: |
|---|
Unless you have a specific reason to use the TCP Transport, use the DMA transport to avoid network issues.
|
Cannot Debug After Switching Transports
You can change the transport for the emulator, but the emulator does not bind to the new transport until you soft-reset the device.
| Note: |
|---|
The DMA transport is the preferred transport for the Device Emulator. Use the TCP/IP transport only if you have specific reasons for doing this.
|
To switch transports
On the Visual Studio Tools menu, click Options, click Device Tools, and then click Devices.
Select an emulator, and then click Properties.
In the Transport box, select a different transport.
If you are switching to TCP/IP, click Configure to set additional options.
Click OK to close the dialog boxes.
Cannot Connect to Emulator While Running in Virtual PC Session
Repairing the Device Emulator Installation
Errors indicating a failure to connect to the Device Emulator are typically not installation errors. However, you can follow these steps to repair the Device Emulator installation. To do this, you need your original installation media. Repairing your Visual Studio installation does not repair the Device Emulator installation.
To repair the Device Emulator installation
Navigate to wcu\ARM on your original Visual Studio installation media.
The location of this folder, such as Disk 1, Disk 2, and so on, varies with your edition of Visual Studio.
Double click vs_emulator.exe to open the Device Emulator Setup Wizard, and then follow the instructions.
Additional Tips
The Device Emulator independent Help system provides additional tips. For more information, click the Device Emulator Help menu and look for "Troubleshooting Connection Issues" on the Content or Index tabs.