How do I get the V2005 emulator talking to the internet
I've been floundering around with settings trying to get the emulator connected to the internet with no success.
I've read some of the posts that tell about using ActiveSync instead of the TCP/IP connection. I've tried selecting cradle from the Device Emulator Manager with no success. But I may have other settings on the emulator goofed up now. Do I need to install ActiveSync or did it come with VS2005?
Here is my setup. VS2005 installed along side VS2003. Not using Virtual PC. PC connected to internet via dsl modem.
Can someone help me?
Clark
[562 byte] By [
csann] at [2008-2-2]
You need to install
ActiveSync version 4.0 that was recently released. You can download it from http://msdn.microsoft.com/mobility/windowsmobile/downloads/default.aspxAfter the installation, go into Tools, Options, Devices, Device Tools, your emulator of choice, Properties, Emulator Properties, Network tab, and remove the checkbox next to NE2000. Close the emulator if it is running and reopen the emulator.
In ActiveSync, make sure that "DMA" is selected in the "Connection Settings".
According to your hardware settings, you will probably need to use the "The Internet" instead of the "Work" connection settings within the emulator.
Thanks for the help Carl. Now I can get to the internet from my emulator. Now I have another problem...I can't get connected to the device from VS2005. I have tried both DMA and TCP, neither work.
The DMA error is Connection Failed. Unspecified Error. I bet that is helpful.
The TCP error is Connection Failed. No connection could be made because target machine actively refused it.
This is very frustrating. I tried dozens of configurations this weekend but got no joy. Is there somewhere I can go to understand how to setu connections? Something that explains all the configuration options such as Used fixed port number, Obtain IP address automatically using ActiveSync, Use Specific IP address, when to use TCP vs DMA, and on the device, what the heck is the difference between Work and MyISP. Also when should we use ActiveSync? How does ActiveSync relate to obtaining a connection in VS? All in all it is very confusing. Would it be simpler if I wasn't using an emulator?
Thanks Carl for your help!!!!
When the emulator is connected via ActiveSync, you can use the VS2005 "Device" entry to connect to the emulator. For example, if you have the Smartphone 2003 emulator connected via ActiveSync, you can use the target "Smartphone 2003 Device" to deploy and debug you app.The DMA error sounds like you have an image which does not support DMA. Can you try deleting the files in :
\Documents and Settings\All Users\Application Data\Microsoft\Device Emulator
and
\Documents and Settings\<currentuser>\Application Data\Microsoft\Device Emulator
The TCP error could be 2 things. It could be an artifact from the previous post where I suggested you disable the NE2000 card. Reactivate it when the emulator is running to fix this problem.
If you are using the Windows Mobile 2005 image, the error comes from the fact that the new ActiveSync does not allow external connections to the cradled device.
For Smartphone and Pocket PC development, the default connection settings should work. Those settings are used to connect to CE devices that do not support ActiveSync.
The DMA transport should now be the primary choice to connect to emulator images. The TCP transport can be used to connect over the network or over ActiveSync to devices that have network support.
The Work and MyISP are Windows CE specific settings. Put simply, the work setting should be used in a "work" environment where you access machines via their hostname like http://myserver. The MyISP settings should be used when the device is connected to an ethernet-like network where you can access machines via their internet address like http://www.microsoft.com.
Carl
I deleted the files you mentioned, and now I can't bring up the SE 2003 VGA emulator at all. I think the SE Emulator comes up instead. What do I need to do to get the VGA Emulator back?
Are you saying I really shouldn't use ActiveSync to connect to the emulator, that I should use DMA instead?
Here is how I have the system configured.
Under Tools/Options/Devices/2003 SE VGA Emulator/Properties, the transport is DMA Transport. Under Configure I have it set to Use Specific IP address - 127.0.0.1 which I believe was the default setting. Use Fixed Port number is unchecked but has the number 5654 in it.
Under Emulator Options/Network, nothing is checked.
When I try Tools/Connect to device, the SE Emulator (not the VGA emulator) comes up, but it cannot connect. I get an error message, Connection Failed. Unspecified Error.
I went back and checked to enable the NE2000 card and when I tried Tools/Connect I got the same error.
I next tried to connect using the Device Emulator Manager and got the error Cannot connect to device. Error: 0x80004055.
Is it possible you could call me or I could call you. Maybe a quick phone conversation would get things going. If you want to do this, email me at csann at earthlink.net.
Thank you for you past, present, and future help, however you choose to provide it!!!!!!! I have a nagging suspicion I have caused the problem with some incompatible settings....
Clark
Carl,
I have some further results for you. This time I decided to try the ActiveSync route. I have ActiveSync 4.0 installed. Using the EmulatorManager, I cradled the VGA emulator (which looks like the SE non-VGA emulator). ActiveSync automatically connected to it. Yippee! I then went into VS 2005 and used Tools/Connect to connect to the PC2003 Device. It connected. Well now!
But, when I built my project and deployed it, using the Start Debugging button, the status bar first said Build started, then Deploy started, then I got a "Connect to device failed" error message. Curses!!
Clark
Carl
In order to get my 2003 SE VGA emulator back, I eventually had to remove VS2005 and reinstall it. I am still getting the "Connection failed. Unspecifie error' when trying to connect using DMA. It seems to me the emulator image was loaded with VS2005 since it wasn't there until I reinstalled VS2005.
HELP!
Clark
