C# -> C

[TMSTKSBK]

Oh joy.

@ work, they want me to make a program that jumps on rasapi32.dll (unmanaged C code), and dials numbers.

rasapi is the thing that makes dial-up networking work. Same as rasdial.

So, if any of you can give me pointers on how to work with unmanaged stuff (ya, P/Invoke & COM stuff...but...meh) that'd be great.

Sorry for the vagueness. Very tired.

[TheOutkastDev]

pinvoke.net: RasDial (rasapi32)

[TMSTKSBK]

Yeah, I read that fun little blurb. Already using significant portions (all) of it. (Thanks, though.)

How does one do a callback from C to C#? I understand delegates in C# well enough to do one, but I've never tried to make unmanaged code that I can't touch call managed code...

So yeah. My extra-kludgy workaround is to grab rasdial.exe and throw command line args at it. Not terribly happy with that..

[Jeff]

Originally Posted by TMSTKSBK

Yeah, I read that fun little blurb. Already using significant portions (all) of it. (Thanks, though.)

How does one do a callback from C to C#? I understand delegates in C# well enough to do one, but I've never tried to make unmanaged code that I can't touch call managed code...

So yeah. My extra-kludgy workaround is to grab rasdial.exe and throw command line args at it. Not terribly happy with that..

A callback from C to C# is done exactly the same way. You just have to create the callback in C#

Heres a greate example.

pinvoke.net: CopyFileEx (kernel32)

CopyFileEx requires a callback, as it is an asynchronis method.

Basically, find out all the arguments the callback needs, create the delegate for it using these arguments and feed it to the invoked method. Pretty much works the exact same way it works creating a callback C#->C# .

On Microsofts page about this function found here they describe the delegate as such

Originally Posted by msdn

lpvNotifier
[in] Specifies a window handle or a RasDialFunc, RasDialFunc1, or RasDialFunc2 callback function to receive RasDial event notifications. The dwNotifierType parameter specifies the nature of lpvNotifier. Please refer to its description preceding for further detail.

If this parameter is not NULL, RasDial sends the window a message, or calls the callback function, for each RasDial event. Additionally, the RasDial call operates asynchronously: RasDial returns immediately, before the connection is established, and communicates its progress via the window or callback function.

If lpvNotifier is NULL, the RasDial call operates synchronously: RasDial does not return until the connection attempt has completed successfully or failed.

If lpvNotifier is not NULL, notifications to the window or callback function can occur at any time after the initial call to RasDial. Notifications end when one of the following events occurs:

* The connection is established. In other words, the RAS connection state is RASCS_Connected.
* The connection fails. In other words, dwError is nonzero.
* RasHangUp is called on the connection.

The callback notifications are made in the context of a thread captured during the initial call to RasDial.

Note specifically this line

Originally Posted by msdn

[in] Specifies a window handle or a RasDialFunc, RasDialFunc1, or RasDialFunc2 callback function

These functions are outlined in the link above but here are links to all three

http://msdn2.microsoft.com/en-us/library/aa377039.aspx
RasDialFunc1 (Windows)
RasDialFunc2 (Windows)

I would assume you can just create delegates that manage this, Or and this may be your better bet, just create a wrapper to invoke these.

[TMSTKSBK]

Thanks, Jeff.

Give me a day or so to digest that...

[Jeff]

Originally Posted by TMSTKSBK

Thanks, Jeff.

Give me a day or so to digest that...

Your really thinking about it to hard I think. Just use a delegate the same as you would as always in C#, or just use any of those 3 functions the same as you are using the RasDial function.

[TMSTKSBK]

Just an FYI...got it working. Yay.

Now if only they gave me some time to actually work on this...