Re: IOCTL and name events stuff
- From: "Ben Voigt [C++ MVP]" <rbv@xxxxxxxxxxxxx>
- Date: Fri, 1 Jun 2007 11:25:22 -0500
<Eran.Yasso@xxxxxxxxx> wrote in message
news:1180673356.280645.207080@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi all,
I need to write a GUI app which do the followings:
1. My app waits for events from other app(actually this is a network
adapter driver) running in kernel. The driver writes to file and
signal my app to read the file.
No problem. Named events are placed in a global namespace (ignoring
terminal services, but you can still access the global namespace even from
there).
2. My app also need o communicate this the driver using IOCTL.
Yuck. IOCTL requires passing buffers around... C# may not be your best
choice there.
Can i do it in C#? can C# wait for events signaled from app written in
C\C++ app running in on kernel and sends messages to device using
IOCTL?
How complicated is it going to be? I'm quite noob in C# programming.
should I consider duing it in C|C++ which I am quite noob as well?
I would suggest C++/CLI. The syntax is quite close to C# as far as
interacting with the .NET framework, creating forms and buttons and so
forth. But it also allows seamless access to the Windows API. At the very
least, you should be able to reuse the header files provided by the kernel
component, instead of having to transcribe everything into C# (constants,
function prototypes, structure definitions, etc).
TIA,
.
- Follow-Ups:
- Re: IOCTL and name events stuff
- From: Eran . Yasso
- Re: IOCTL and name events stuff
- References:
- IOCTL and name events stuff
- From: Eran . Yasso
- IOCTL and name events stuff
- Prev by Date: Re: Best options for protecting software from piracy?
- Next by Date: Cleaning Up Event Handlers
- Previous by thread: Re: IOCTL and name events stuff
- Next by thread: Re: IOCTL and name events stuff
- Index(es):