Transport Layer, SDK, Remote Tools CE6.0

Hello,

I got a complicated problem I cannot solve regarding the Remote Tools.

Here is the discription:

1. Step: I build a WinCE6.0 Image (x86) in Visual Studio 2005.
2. Step: I build a SDK.
3. Step: Install the SDK.
4. Step: (ERROR) Want to connect with Remote Tools in Visual Studio 2005
Menu-->Target-->Remote Tools ; My device from my SDK doesn't show up.
5. Step: Connect with Remote Tools from Start Menu -->Visual Studio
2005-->Remote Tools ; My device shows up, i can configure the TCP Connect
Transport. All fine.
6. Step: Rebuild my WinCE6.0 Image (x86), I changed a few things, nothing
important
7. Step: I rebuild and install the SDK
8. Step: same like Step4
9. Step: (ERROR) Want to connect with Remote Tools from Start Menu -->Visual
Studio 2005-->Remote Tools ; My device shows up, but I CANNOT configure the
TCP Connect Transport
10. Step: I installed the first SDKs on another machine. The same behavior!

So here are a few question:
Why does not my device show in Step 4?
In Step 9, why does nothing happen when I press the "Configure"-Button in
Device Properties?
I belive in Windows CE 5.0 you could add a transport layer to SDK, how can I
do this in WinCE6.0?

Regards,

Mazzo

Paul
Thu Jun 12 09:38:23 PDT 2008

Visual Studio is sensitive to what solution is currently loaded. It's
possible that in some of your test cases, you had the Platform Builder
solution loaded and that changes how the remote tools connect (they're
expecting KITL). So, in that case, you're *not* connecting via the SDK
stuff; you're connecting to the current Target for Platform Builder. You
need to use the Start menu method to get to the remote tools-via-SDK.

Now, as to why you can't configure the TCP Connect Transport... Yes, that's
just the way it works. You can set the TCP Connect options via VS2005
itself, Tools | Options | Device Tools | Devices, but the remote tools
themselves don't allow that (I'd say it's a bug, but maybe there's a
reason). In any case, the remote tools will use the configuration that you
set via the VS2005 IDE.

Paul T.

"Mazzo" <Mazzo@discussions.microsoft.com> wrote in message
news:0A12B64B-C014-41D6-95F9-9F505802A9BA@microsoft.com...
> Hello,
>
> I got a complicated problem I cannot solve regarding the Remote Tools.
>
> Here is the discription:
>
> 1. Step: I build a WinCE6.0 Image (x86) in Visual Studio 2005.
> 2. Step: I build a SDK.
> 3. Step: Install the SDK.
> 4. Step: (ERROR) Want to connect with Remote Tools in Visual Studio 2005
> Menu-->Target-->Remote Tools ; My device from my SDK doesn't show up.
> 5. Step: Connect with Remote Tools from Start Menu -->Visual Studio
> 2005-->Remote Tools ; My device shows up, i can configure the TCP Connect
> Transport. All fine.
> 6. Step: Rebuild my WinCE6.0 Image (x86), I changed a few things, nothing
> important
> 7. Step: I rebuild and install the SDK
> 8. Step: same like Step4
> 9. Step: (ERROR) Want to connect with Remote Tools from Start
> Menu -->Visual
> Studio 2005-->Remote Tools ; My device shows up, but I CANNOT configure
> the
> TCP Connect Transport
> 10. Step: I installed the first SDKs on another machine. The same
> behavior!
>
> So here are a few question:
> Why does not my device show in Step 4?
> In Step 9, why does nothing happen when I press the "Configure"-Button in
> Device Properties?
> I belive in Windows CE 5.0 you could add a transport layer to SDK, how can
> I
> do this in WinCE6.0?
>
> Regards,
>
> Mazzo

Mazzo
Thu Jun 12 23:10:00 PDT 2008

Hello Paul,

thank you so much for your response. Sometimes it seams so difficult...

I got it to work, thanks to your answer.

Greetings from Germany,

Mazzo

"Paul G. Tobey [eMVP]" wrote:

> Visual Studio is sensitive to what solution is currently loaded. It's
> possible that in some of your test cases, you had the Platform Builder
> solution loaded and that changes how the remote tools connect (they're
> expecting KITL). So, in that case, you're *not* connecting via the SDK
> stuff; you're connecting to the current Target for Platform Builder. You
> need to use the Start menu method to get to the remote tools-via-SDK.
>
> Now, as to why you can't configure the TCP Connect Transport... Yes, that's
> just the way it works. You can set the TCP Connect options via VS2005
> itself, Tools | Options | Device Tools | Devices, but the remote tools
> themselves don't allow that (I'd say it's a bug, but maybe there's a
> reason). In any case, the remote tools will use the configuration that you
> set via the VS2005 IDE.
>
> Paul T.
>
> "Mazzo" <Mazzo@discussions.microsoft.com> wrote in message
> news:0A12B64B-C014-41D6-95F9-9F505802A9BA@microsoft.com...
> > Hello,
> >
> > I got a complicated problem I cannot solve regarding the Remote Tools.
> >
> > Here is the discription:
> >
> > 1. Step: I build a WinCE6.0 Image (x86) in Visual Studio 2005.
> > 2. Step: I build a SDK.
> > 3. Step: Install the SDK.
> > 4. Step: (ERROR) Want to connect with Remote Tools in Visual Studio 2005
> > Menu-->Target-->Remote Tools ; My device from my SDK doesn't show up.
> > 5. Step: Connect with Remote Tools from Start Menu -->Visual Studio
> > 2005-->Remote Tools ; My device shows up, i can configure the TCP Connect
> > Transport. All fine.
> > 6. Step: Rebuild my WinCE6.0 Image (x86), I changed a few things, nothing
> > important
> > 7. Step: I rebuild and install the SDK
> > 8. Step: same like Step4
> > 9. Step: (ERROR) Want to connect with Remote Tools from Start
> > Menu -->Visual
> > Studio 2005-->Remote Tools ; My device shows up, but I CANNOT configure
> > the
> > TCP Connect Transport
> > 10. Step: I installed the first SDKs on another machine. The same
> > behavior!
> >
> > So here are a few question:
> > Why does not my device show in Step 4?
> > In Step 9, why does nothing happen when I press the "Configure"-Button in
> > Device Properties?
> > I belive in Windows CE 5.0 you could add a transport layer to SDK, how can
> > I
> > do this in WinCE6.0?
> >
> > Regards,
> >
> > Mazzo
>
>
>