Re: TAPI and .NET

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: William DePalo [MVP VC++] (willd.no.spam_at_mvps.org)
Date: 10/20/04 

Date: Wed, 20 Oct 2004 14:57:44 -0400

"Andreas Marschall [MVP TAPI]" <Andreas.Marschall@I-B-A-M.de> wrote in
message news:%239VNL7ptEHA.220@TK2MSFTNGP15.phx.gbl...
> thanks for your comments on Bishoy's posting.

No problem. Realize, though, that my motives are not entirely altrusitic.
<g>

You see, there is no one here who offers _more_ free, high-quality advice
than you. There is no one here who takes the time to read _every_ post and
offer constructive critiscism when someone else makes a mistake (as I have
done once). So I don't want anyone to try to stifle you (or anyone else) who
has got something to say from which I can learn just because the answer is
one that they didn't want to hear.

Keep up the good work! And thanks.

[And on the subject matter, I'd say the KB article is right-on as far as it
goes. I'd make stronger statements. Never use TAPI3 for anything non-trivial
as it is much less capable than TAPI2. That makes the RCW issue a moot
point. And if one targets the .Net platform use the Platform Invoke (aka
P/Invoke) method to access TAPI2 from a CLS compliant language. I have an
IVR which does just that and allows me to build applications in
C#/VB.Net/J#/JScript.Net and Managed Extensions for C++). Of course, that's
just my opinion.]

Regards,
Will