Re: TAPI and VS.NET 2003

Tech-Archive recommends: Fix windows errors by optimizing your registry

Clayton,

probably the 3rd party application has messed up your system.

It is not allowed (and not necessary anyway) to redistribute tapi3.dll
with an application. Having a duplicate copy of tapi3.dll in a folder
different from system32.

I would suggest to
- completely remove the 3rd party app.
- Reinstall the latest service pack to be sure you have the righ file
- run regsvr32 tapi3.dll in the %WINDIR%\system32 folder
- use a development platform which is supported with TAPI3
(e.g. C++ or VB)

Sooner or later you may run into problems (mainly due to garbage
collection issues) even if the basic things seem to work at first sight.
Just do a search over this group on Google Groups to read about
the numerous problems that have been reported with TAPI and .NET.

You should rather create the TAPI part as a dll in C++ or VB and use
this dll from your .NET application.

Best regards,

Matthias Moetje
-------------------------------------
TERASENS GmbH
Augustenstraße 24
80333 Munich, GERMANY
-------------------------------------
Fon: +49 89 143370-0
Fax: +49 89 143370-22
e-mail: moetje at terasens dot com
www: www.terasens.com
-------------------------------------


"Clayton Rumley" <clayton@xxxxxxxxxxxxx> wrote in message
news:%238J4NK$LGHA.3144@xxxxxxxxxxxxxxxxxxxxxxx
Hi Andreas,


Clayton,
Regarding TAPI and .NET see KB article "841712 - Telephony Application
Programming Interface (TAPI) functionality is not supported from managed
code".

I read the article, but I don't believe the statement that the COM wrapper
generated by VS.NET doesn't work because I've seen other people with
managed code examples online, and I can use the COM wrapper to enumerate
the modems, dial the modem, answer calls, etc. Perhaps they mean that it
only partially works (i.e. a bunch of interfaces don't get generated)?

Are you saying that you see the ITxxx interfaces but not the ITxxx2 ?

Correct. The intellisense lists all the ITxxx interfaces but not ITxxx2.
If I try to simply type the name of an ITxxx2 interface against the
TAPI3LIB namespace it just gives me an error (that the name is not
defined).

Can you reproduce the issue with TAPI Browser TB3x ?

In order to ensure that my modem was going to do what I wanted it to do, I
downloaded a shareware answering-fax machine software from
http://www.go4customer.com/ (which did everything I wanted my program to
do so I know I've got the right modem). When I run TAPI Browser TB3x it
uses the tapi3.dll in this shareware application's directory (not the one
in my system32 directory), where it does in fact list all the ITxxx2
interfaces. So I decided maybe the tapi3.dll in my system32 directory
wasn't the right one and manually added a reference in VS.NET to the
tapi3.dll provided by the answernig-machine software. The end result was
no different.

I'm hoping I'm just missing something really simple and that it can be
easily resolved but I haven't been able to find anyone else online talking
about this problem. I thank you very much for your time.

Clayton



.

Relevant Pages

  • Re: TAPI and VS.NET 2003
    ... the computer I have the modem on only has the ability to ... probably the 3rd party application has messed up your system. ... You should rather create the TAPI part as a dll in C++ or VB and use ... The intellisense lists all the ITxxx interfaces but not ITxxx2. ...
    (microsoft.public.win32.programmer.tapi)
  • Re: TAPI and VS.NET 2003
    ... Regarding TAPI and .NET see KB article "841712 - Telephony Application ... The intellisense lists all the ITxxx interfaces but not ITxxx2. ... In order to ensure that my modem was going to do what I wanted it to do, ... system32 directory), where it does in fact list all the ITxxx2 interfaces. ...
    (microsoft.public.win32.programmer.tapi)