2005 Remote Tools Connectivity with Emulators

[troy anderson]

I have asked this before but got not response; I am hoping this time I will
get some help. We are going to start this project and would like to use
VS-2005. If we cannot get this to work we will probably go back to old
eVC++. My question is as follows:

How do I get the Remote Tools that come with VS-2005 to work with my
WinCE emulation image. My emulator is not displayed in the "Select a
Windows CE Device" dialog when I lauch Remote Registry Editor. The only
custom platform I see is the device image I created but not the emulator
one.

Note: When I launch eVC++ Remote Tools I can connect to my emulator.
However, when I do this it launches another emulation env. that does not
allow me to connect to the one I am debugging using VS-2005.

Thanks

 

[John Roberts]

I recently had success in connecting a WinCE emulator image (the x86
emulator) to VS 2005 using this process:

http://msdn2.microsoft.com/en-us/library/ms228708(en-US,VS.80).aspx

I had to launch the emulator with 'virtual switch' to allow incoming IP
connections.

I have read that this technique can be used with remote tools as well as
managed deploy/debug but I haven't tried that.

- John

 

[troy anderson]

Thanks for the info but this does not answer my question. I am having
problem getting the VS2005 Remote Tools to work; I am able to get VS2005 to
work with my emulator. I need to be able to use Remote Registry Editor with
my CE emulator image; it does not appear in the "Select a Windows CE Device"
dialog see details below.

Thanks

 

[John Roberts]

In which case I don't know. Perhaps you can explain how you managed to get
VS2005 working with a custom WinCE emulator image? Did you build a Platform
Builder SDK for it? Do you use the emulator transport or TCP/IP? Are you
using CF 1.0 or 2.0? Do you use ActiveSync?

Using the technique I described, it is possible to launch Platform Builder
with the emulator image using KITL, Target Control support and the remote
tools that ship with Platform Builder. At the same time, you can debug using
VS2005 and the TCP/IP transport.

 

[troy anderson]

Problem with your method is not all of my developer's have Platform Builder.
Plus one would think that PBuilder should not be required to do app level
development in VS2005.
Answers to your questions:
-) Perhaps you can explain how you managed to get VS2005 working with a
custom WinCE emulator image? "As documented by MS. which matches your
description."
-) working with a custom WinCE emulator image? "yes"
-) Did you build a Platform Builder SDK for it? "yes"
-) Do you use the emulator transport or TCP/IP? "yes"
-) Are you using CF 1.0 or 2.0? 2.0
-) Do you use ActiveSync? "No"

 

[John Roberts]

OK, the only thing I can add is that I read on google search that you are
supposed to be able to run the VS2005 remote tools in this scenario by
running CMAccept a 2nd time. I haven't tried it though. Do post if you
manage to get it working...

TIA,
- John

 

[Upender R. Sandadi [MSFT]]

Sorry if this is already answered. Are you able to debug applications on the
same emulator image using VS 2005? If you are able to do that, then just
launch the remote tools from VS start --> all programs --> VS remote tools
location and then in the remote tools connect dialog, select the same device
as what you used in VS for debugging. Is that not working?

thx.
--
Upender R. Sandadi [MS]
_____________________________________________________________
This posting is provided "AS IS" with no warranties, and confers no
rights.
_____________________________________________________________

 

[troy anderson]

No because selecting "start --> all programs --> VS remote tools --> Remote
xxx" does not list my device in the tree view for the "Select a Windows CE
Device." This is where my problem is.

However, it does show up in the tree view for the "Select a Windows CE
Device." dialog when launched from eVC++.

Thanks

Sorry if this is already answered. Are you able to debug applications on
the same emulator image using VS 2005? If you are able to do that, then
just launch the remote tools from VS start --> all programs --> VS remote
tools location and then in the remote tools connect dialog, select the
same device as what you used in VS for debugging. Is that not working?

thx.
--
Upender R. Sandadi [MS]
_____________________________________________________________
This posting is provided "AS IS" with no warranties, and confers no
rights.
_____________________________________________________________

OK, the only thing I can add is that I read on google search that you are
supposed to be able to run the VS2005 remote tools in this scenario by
running CMAccept a 2nd time. I haven't tried it though. Do post if you
manage to get it working...

TIA,
- John