Re: Mobile 5 - Debugging Managed C#/Unmanaged C++ Code
- From: "Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT com>
- Date: Mon, 3 Mar 2008 10:12:38 -0700
No, you can't step from managed code through a P/Invoke call into native
code in the Smart Device debugger. You might be able to use Attach to
Process to do the native debugging (with the native DLL project loaded into
that instance of VS2005), or simply write debug information from the native
DLL to a serial port or something. This really doesn't come up very often,
though, where you actually *need* to step from one to the other.
Paul T.
<john.e.otten@xxxxxxxxx> wrote in message
news:ecbcb079-b7e8-48d8-81da-9d67757ad571@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
We are working on an application that is targeting a PDA that runs
Windows Mobile 5.0. Our development environment is Visual Studio 2005
with the appropriate plugins.
Currently, the GUI is being built with C# managed code using the VS
2005 GUI builder. The main processing of the code is planned to be
contained in a static DLL written with unmanaged C++. We will use
PInvoke calls to access data in the DLL for display/interaction on the
GUI. We decided upon this as it does not appear that we can use
managed C++ in the Windows Mobile 5 platform, and the only way to use C
++ for the GUI in the Mobile environment is to use the Windows API
calls (which means development would take longer, and perhaps be less
robust).
I wrote some simple functions on the C++ side to verify that the
concept would work with the current version of the GUI, and it did.
However, now that we are trying to do full up development we realize
that we will need to use the debugger on the unmanaged C++ side.
I poked around on the internet and found some references that state
you should set your debugging state to "Both" in the C++ unmanaged
project so that debugging would work with both managed and unmanaged
code. However, that option does not appear in our DLL project -
instead only "Smart Device Native Debugger" appears as a choice.
Also, the MSDN pages discuss an option in the C# project settings
under the debug tab that allows you to "Enable unmanaged code
debugging." That checkbox does not appear in our C# project either.
My concern is that such settings (like some others) do not exist in
the Windows Mobile paradigm. If they do exist, how can I access
them? If they do not exist, does anyone have any suggestions on how
to proceed?
We do not have any experience programming in C# (hence the desire for
a C++ unmanaged DLL) and although we would like to learn, we do have
to keep our project deadline in mind. If it is the most expedient way
to do it, we can possibly bite the bullet (but I'll have to find some
way to appease the project manager for the additional time it may
take).
My only other thought is (assuming that the settings do not exist in
the Mobile environment) that we attempt to do the managed/unmanaged
development outside of the Mobile environment and then port it to
Windows Mobile 5 after it is completed. This is not a very attractive
solution either. Has anyone done anything similar to this?
Any comments or suggestions would be greatly appreciated!
Thanks,
John
.
- Follow-Ups:
- Re: Mobile 5 - Debugging Managed C#/Unmanaged C++ Code
- From: john . e . otten
- Re: Mobile 5 - Debugging Managed C#/Unmanaged C++ Code
- Prev by Date: Re: Do I need to have both .Net CF 2.0 and 3.5?
- Next by Date: Re: Mobile 5 - Debugging Managed C#/Unmanaged C++ Code
- Previous by thread: Do I need to have both .Net CF 2.0 and 3.5?
- Next by thread: Re: Mobile 5 - Debugging Managed C#/Unmanaged C++ Code
- Index(es):
Relevant Pages
|
