Re: Manage in unmanaged easier or unmanaged in managed
- From: garlic <garlic@xxxxxxxxxxxx>
- Date: Sun, 27 Apr 2008 07:47:00 -0700
WinSock development for WinCE is not totally similar to that on the desktop.
WSAAsynSelect used to notify Windows Message Handler for a socket event is
missing in WinCE. Thus i thought of using CCeSocket in MFC
Using dllimport marsaling is not difficult at all. i just need to state the
name of the dll and the entry point (function name) and convert its initial
parameter to managed parameter. Can i dllimport MFC code like win32 API. I am
afraid it will become messy and wonder if Managed Code can handle.
I know i need to pin the unManaged pointer so that GC will not Garbage
Unmanage heap memory although it will halt the safe code from running. I can
consider MFC code as unmanaged too, right?
I have no problem installing V, X on the devices platform ( i think they are
supported on WinCE), but i think managed code is easier and faster to code. I
don't think speed different can be detected with human eye.
.
- Follow-Ups:
- Re: Manage in unmanaged easier or unmanaged in managed
- From: Paul G. Tobey [eMVP]
- Re: Manage in unmanaged easier or unmanaged in managed
- From: Chris Tacke, eMVP
- Re: Manage in unmanaged easier or unmanaged in managed
- References:
- Manage in unmanaged easier or unmanaged in managed
- From: garlic
- Re: Manage in unmanaged easier or unmanaged in managed
- From: Christopher Fairbairn
- Re: Manage in unmanaged easier or unmanaged in managed
- From: garlic
- Manage in unmanaged easier or unmanaged in managed
- Prev by Date: Setup program
- Next by Date: RE: Setup program
- Previous by thread: Re: Manage in unmanaged easier or unmanaged in managed
- Next by thread: Re: Manage in unmanaged easier or unmanaged in managed
- Index(es):