Visual Studio - Debug - Launch Application

[Guest]

Trying to figure out why the following happens:

1) At work connected to the LAN and Internet, I created a quick dummy
application for a Pocket PC 2003 SE Emulator in Visual Studio .NET 2003. I
start the debug, and the Emulator I have picked, launches, the program
installs, I get my warning message for legacy applications, and then Visual
Studio reports that it is Launching the Application. In a few seconds the
Application is running on the Pocket PC Emulator.

2) At home, not connected to the LAN, Not connected to the Internet, I
perform the same debug steps, and I get the following result. The
Application deploys, installs, I get my warning, and then Visual Studio says
that it is Launching the Application. However on the Emulator, the
application never launches. And after about a minute the Debug envioronment
closes, and Visual Studio is back ready for editing the program. In the mean
time on the Emulator, the program was installed, I can browse to it, and I
can even launch it manually to run it, and it works.

Any ideas what would cause this behaviour, which seems to be by design...I
read somewhere that when the Emulator loads, it boots just like regular
pocket pc, and that there was something about being connected to the Internet
or Work...and how VS.NET first deploys Compact Framework onto the emulator.
Could it be attempting to go out the internet or something...?

Thanks
J

 

[Robert Jordan]

Any ideas what would cause this behaviour, which seems to be by design...I
read somewhere that when the Emulator loads, it boots just like regular
pocket pc, and that there was something about being connected to the Internet
or Work...and how VS.NET first deploys Compact Framework onto the emulator.
Could it be attempting to go out the internet or something...?

The VS.NET debugger uses TCP/IP to communicate with the Pocket-PC
debugger, but it does not use TCP/IP to upload the files (it uses
RAPI instead). Do you have a working loopback interface? Open
a command line box and type "ping 127.0.0.1".

bye
Rob

 

[Guest]

Hey Robert, everything I have been reading points to exactly what you are
suggesting. I am on an XP Pro SP2 machine, and a Ping of the Local address,
results in success. A route print shows the 127.0.0.1 available, I think
that in XP this is already a default option...as I have seen below.

I also tried to install a loopback network card, and after selecting the
Microsoft Loopback the connection is created with only the Virtual Machine
Network Services option checked. This option is also present in the standard
LAN connection...and while not connected to the network at work I would
expect the loopback to still work.

As I mentioned I have been reading a bit on the whole loopback setting, and
I have been seeing that in VS 2005, there are settings for the network
connection for this, as it relates to the device defined in the
(Tools-->Options-->Device Tools-->Devices) then I pick the Emulator, and
Configuration, and in 2005 there are network settings, but in Visual Studio
2003 there are no Network Settings, so I figure they must be hidden else
where...?

Any more ideas?