Hi,

I'm currently developping a Windows application for PocketPC with Visual
Studio 2003.
Since our HHP 9500 Dolphin PocketPC has no USB cradle, we cannot use
ActiveSync (else it conflicts with the utility tool in charge of the
connection to the Ethernet base)

To debug via TCP/IP, we tried (and succeeded) to change Tools / periph TCP
transport configuration, replacing the option "IP adress provided by
ActiveSync" by the option "static IP address", this IP address set to the IP
of the slot receiving the PocketPC.
Few days ago, debug worked fine using this settings.

However, I have not been able to reproduce that way of debugging today...
Visual Studio attempts to establish a connection but fails with a message
"Unable to establish the connection. Check ..."

I think that PocketPC <=> computer connection is actually good, since ping
work in both directions, and I can use a tool which replicates the screen of
the PocketPC on the screen of the computer (this tool is setup to use TCP
transport, and not ActiveSync)

Could you tell me some advice on the possible causes of that issue, and the
way to solve the problem ?
Thanks a lot for your time.

Regards,
Samuel

Re: How to solve TCP connection issue to debug on a PocketPC by r_z_aret

r_z_aret
Thu May 26 16:10:09 CDT 2005

On Wed, 25 May 2005 22:18:46 +0200, "netcoupe.net"
<bor<no_spam>et@club.fr> wrote:

>Hi,
>
>I'm currently developping a Windows application for PocketPC with Visual
>Studio 2003.
>Since our HHP 9500 Dolphin PocketPC has no USB cradle, we cannot use
>ActiveSync (else it conflicts with the utility tool in charge of the
>connection to the Ethernet base)

Can you possibly use ActiveSync via infra red or some serial
connection? If you can do that once and create a partnership, then you
should be able to use ActiveSync (and thus debugging) via Ethernet.



-----------------------------------------
To reply to me, remove the underscores (_) from my email address (and please indicate which newsgroup and message).

Robert E. Zaret, eMVP
PenFact, Inc.
500 Harrison Ave., Suite 3R
Boston, MA 02118
www.penfact.com

Re: How to solve TCP connection issue to debug on a PocketPC by netcoupe

netcoupe
Fri May 27 14:13:08 CDT 2005

Thank you very much for your help. We will try to establish a partnership
using infrared (moreover it is very likely that a partnership was previously
defined the last time it did work, since we had performed some tests using
an USB cradle we have no more now...)

Regards,
Samuel

<r_z_aret@pen_fact.com> a écrit dans le message de
news:mecc91lnb15m1iud0vojn4nhhbnmrh0c59@4ax.com...
> On Wed, 25 May 2005 22:18:46 +0200, "netcoupe.net"
> <bor<no_spam>et@club.fr> wrote:
>
> >Hi,
> >
> >I'm currently developping a Windows application for PocketPC with Visual
> >Studio 2003.
> >Since our HHP 9500 Dolphin PocketPC has no USB cradle, we cannot use
> >ActiveSync (else it conflicts with the utility tool in charge of the
> >connection to the Ethernet base)
>
> Can you possibly use ActiveSync via infra red or some serial
> connection? If you can do that once and create a partnership, then you
> should be able to use ActiveSync (and thus debugging) via Ethernet.
>
>
>
> -----------------------------------------
> To reply to me, remove the underscores (_) from my email address (and
please indicate which newsgroup and message).
>
> Robert E. Zaret, eMVP
> PenFact, Inc.
> 500 Harrison Ave., Suite 3R
> Boston, MA 02118
> www.penfact.com



Re: How to solve TCP connection issue to debug on a PocketPC by RobG

RobG
Wed Jul 06 14:30:07 CDT 2005

If your device can talk to a wireless netowork or LAN ethernet connection
this worked for me.

This saved me after 10 hours trying figure out why deploying via ActiveSync
stopped working, this solution lets you completely avoid Activesync and do it
over the TCPIP ethernet. It deploys way faster too. Thank you microsoft for
coming up with a solution. Not sure what happen to my activesync connection
debug, but I tried everything out there ie: proxyport.reg,reinstall vs.net
and some others but this utility worked for me. Thought I would post this
around to let people know I was able to make this work. I added some notes on
my findings below as well

"Windows CE Utilities for Visual Studio .NET 2003 add-on"
http://support.microsoft.com/default.aspx/kb/816826/EN-US

NOTES: Read the readme very carefully. My first attempt to do TCPIP
debug/deploy didn't work because I still had it connected to active sync.
This will cause a error because was trying to use the virtual ip it created
with ActiveSync. Also this appeared to only work if you can attach your
handheld device with a wireless adapter or LAN connect to the device. Only
other thing I did listed in requirements section of readme, I copied over the
newest version of toolhelp.dll. I did not try the serial cable method listed
that used activesync.

"netcoupe.net et@club.fr>" wrote:

> Thank you very much for your help. We will try to establish a partnership
> using infrared (moreover it is very likely that a partnership was previously
> defined the last time it did work, since we had performed some tests using
> an USB cradle we have no more now...)
>
> Regards,
> Samuel
>
> <r_z_aret@pen_fact.com> a écrit dans le message de
> news:mecc91lnb15m1iud0vojn4nhhbnmrh0c59@4ax.com...
> > On Wed, 25 May 2005 22:18:46 +0200, "netcoupe.net"
> > <bor<no_spam>et@club.fr> wrote:
> >
> > >Hi,
> > >
> > >I'm currently developping a Windows application for PocketPC with Visual
> > >Studio 2003.
> > >Since our HHP 9500 Dolphin PocketPC has no USB cradle, we cannot use
> > >ActiveSync (else it conflicts with the utility tool in charge of the
> > >connection to the Ethernet base)
> >
> > Can you possibly use ActiveSync via infra red or some serial
> > connection? If you can do that once and create a partnership, then you
> > should be able to use ActiveSync (and thus debugging) via Ethernet.
> >
> >
> >
> > -----------------------------------------
> > To reply to me, remove the underscores (_) from my email address (and
> please indicate which newsgroup and message).
> >
> > Robert E. Zaret, eMVP
> > PenFact, Inc.
> > 500 Harrison Ave., Suite 3R
> > Boston, MA 02118
> > www.penfact.com
>
>
>