I'm not used to .NET so maybe I'm messing around in a obvious point but I'm trying to debug and application using the SipXTapiDotNet and when I try to debug the Visual Studio Express complains about the sipxtapid.dll. Already tried to put the dll on the debug directory but up to know I had no success. Does anyone know how to solve this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are you working with code directly from SVN, a pre-compiled binary from the download page or a zip file of the source from the download page?
In SVN, I've added a PlaceCall example application which could be helpfull.
If you have placed both sipxtapi.dll and sipxtapid.dll into the bin\debug directory and you are NOT working with code from SVN, then you may try to create a directory called C:\devrootsipx\sipxcalllib\examples\bin\ and adding the dll files to that directory. (a potential bug in the pre-compiled libraries from the download page.)
Finally, you can download the dependancy walker from http://www.dependencywalker.com/ and open the sipxtapid.dll or sipxtapi.dll to see if you are missing any of the sipxtapi dependancies. When you have the file open in dependancy walker, press F9 to show the full paths of each dependancy. Items that are missing will appear at the top of the list, if I remember correctly.
When I open sipxtapid.dll with dependancy walker, mine shows c:\windows\system32\mpr.dll as missing an export function in a delay dependent module. This can be ignored.
- Josh
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for the reply. I'm using the SVN. I decided to use it when I found out that the I'm not sure why but I solved if by just adding the reference to the DLL intead of adding the whole SipXTapiDotNet_VB Project to the Visual Studio Solution. It worked and in fact I guess that I was doing it on a more complicated way.
Today I was able to debug and I'm amazed with result.
Really simple to use and quite powerfull! Great work.
New questions will come. :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not used to .NET so maybe I'm messing around in a obvious point but I'm trying to debug and application using the SipXTapiDotNet and when I try to debug the Visual Studio Express complains about the sipxtapid.dll. Already tried to put the dll on the debug directory but up to know I had no success. Does anyone know how to solve this?
Are you working with code directly from SVN, a pre-compiled binary from the download page or a zip file of the source from the download page?
In SVN, I've added a PlaceCall example application which could be helpfull.
If you have placed both sipxtapi.dll and sipxtapid.dll into the bin\debug directory and you are NOT working with code from SVN, then you may try to create a directory called C:\devrootsipx\sipxcalllib\examples\bin\ and adding the dll files to that directory. (a potential bug in the pre-compiled libraries from the download page.)
Finally, you can download the dependancy walker from http://www.dependencywalker.com/ and open the sipxtapid.dll or sipxtapi.dll to see if you are missing any of the sipxtapi dependancies. When you have the file open in dependancy walker, press F9 to show the full paths of each dependancy. Items that are missing will appear at the top of the list, if I remember correctly.
When I open sipxtapid.dll with dependancy walker, mine shows c:\windows\system32\mpr.dll as missing an export function in a delay dependent module. This can be ignored.
- Josh
Josh,
Thank you for the reply. I'm using the SVN. I decided to use it when I found out that the I'm not sure why but I solved if by just adding the reference to the DLL intead of adding the whole SipXTapiDotNet_VB Project to the Visual Studio Solution. It worked and in fact I guess that I was doing it on a more complicated way.
Today I was able to debug and I'm amazed with result.
Really simple to use and quite powerfull! Great work.
New questions will come. :-)