URGENT: "Cannot establish a connection. Be sure the device is physically connected to the developmen

S

Sami

Hello,
I just started out with VS.NET 2003 to develop for PPC2003.

I have been developing for PPC2002, HPC2000 and PPC2003 using eVC++3.0 &
eVC++4.0.
I have now decided to move upto "better" things like VS.NET2003.

I can connect to PPC2002 emulator, PPC2003 SE Emulator but unfortunately the
development device that I have is a PPC2003 device. And ofcourse I get a
stupid problem trying to connect to PPC2003 device and emulator from VS.NET
2003 with the error: "Cannot establish a connection. Be sure the device is
physically connected to the development computer"

I also installed the Windows CE Utilities for Visual Studio .NET 2003 Add-on
Pack v1.1 and tried all the things in there without any result.

The IP address that the PPC2003 device gets is 192.168.55.101 and when I try
to Setup the Device from VS.NET 2003 it gives me an error saying that it
cannot find the device IP Address.

I also set the Processor type in VS.NET 2003 to ARMV4 which is present in
the PPC2003 device. no luck so far.
I tried out the .reg fixes and the delDesktopCryptKey fix without any
result.

Any help would be greatly appreciated.

It is a shame that such a big software company like Microsoft don't test
their products thoroughly.
 
S

Sami

Why does VS.NET 2003 try to connect to the PPC2003 device using TCPTransport
and not ActiveSync??

Because I have an ActiveSync connection between my device and the Desktop.
 
F

Frederik Jensen

Sami said:
Hello,
I just started out with VS.NET 2003 to develop for PPC2003.

I have been developing for PPC2002, HPC2000 and PPC2003 using eVC++3.0 &
eVC++4.0.
I have now decided to move upto "better" things like VS.NET2003.

I can connect to PPC2002 emulator, PPC2003 SE Emulator but unfortunately
the
development device that I have is a PPC2003 device. And ofcourse I get a
stupid problem trying to connect to PPC2003 device and emulator from
VS.NET
2003 with the error: "Cannot establish a connection. Be sure the device is
physically connected to the development computer"
[Cut]

A really annoying issue with VS.NET 2003. I have experienced it multiple
times and it appears out of the blue sky at time. When the problem arises I
focus on setting the Device CPU type using the buildin tool that comes with
the Add-on. Also I try rebooting the device and desktop computer. This
solves the problem for me. However I have one WinCE 4.1 device that I cannot
connect to even though an ActiveSync exists. For that reason I have upgraded
to Windows CE 4.2.
 
S

Sami

I tried out a lot of things without any success. I then repaired my VS.NET
2003 installation and now I can deploy my project to the PPC2003 device.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top