Hi @all,
I try to implement a custom port supplier for VS2008 that interacts with Windows CE (5-6) Devices (.NET CF).
I know that the DE for .NET CF uses the Default .NET Managed Only Engine together with the icordbg Runtime and the Default VSD Port Supplier.
So why I can't use this constellation: The Default VSD Port Supplier only let me choose the Emulator Images or a local ActiveSync attached CE device. I can configure vs to use TCP/IP but this is not applicable.
I checked the Internet and found mdbg working with .net cf by using the CF RemoteToolsFramework. With this Framework it is quiet simple to extend the device collection with any tcp connected device and this is my Goal.
While checking the sources, I figured out that a DebugPortClass (IDebugPort) for the .net cf Runtime (ICorDebug) also has to implement the the undocumented "INetCFDebuggerRemoteDevice" interface.
So I've created a simple DebugPortSupplier and a simple DebugPort Class and registered it in the AD7Engine hive.
For test purpose I've created an vs addin which calls "LaunchDebugTarges" with the Default engine and my DebugPort guid.
First Results with the Windows Mobile Emulator: The Emulator get launched and the cf runtime calls my implementation of "INetCFDebuggerRemoteDevice.Launch", in this I start the net application on the device and Visual Studio get's into debug mode.
And here comes the Problem(s): I have to implement IDebugPort2.GetProcess which have to return a IDebugProcess2 instance. And this is my Problem. I don't know how to implement the Interface correctly in order to interact with the Default .NET DE.
And this is my question: Does anybody know how a implementation of IDebugProcess2 for the Default DE must look like?
Maybe the VS Dev Team can share info's about the PortSupplier implementation for VSD in eps.dll?
Thanks, best regards and a nice weekend
Chris