Re: [Iaxclient-devel] Catching up, and info on a new NCT IAXClient Library Wrapper

[Jason S. <jas...@rc...>]

Andrew,

 

I've been monitoring this list but not posting because I've been waiting for
a post just like this!

 

I would be very interested in a VS 2005 (.NET 2.0) build against a stable
iaxclient - you are definitely not wasting your time!

 

Many thanks,

Jason Steele

 

 

  _____  

From: iax...@li...
[mailto:iax...@li...] On Behalf Of Andrew
Pollack
Sent: 20 July 2007 14:05
To: iax...@li...
Subject: [Iaxclient-devel] Catching up,and info on a new NCT IAXClient
Library Wrapper

 


Hello all -- 
        Its been a while and I apologize for not monitoring this list.  My
work has kept me busy. 

In may of 2006 I released the "NCT IAXClient Library Wrapper" for vs.NET
2003, and I know a number of you have downloaded it and used it.   
(for reference, its still here:
http://www.thenorth.com/northern.nsf/html/nct_iaxclientwrapper ).   I get
email every once in a while from someone thanking me for it but other wise
here little about it. 

I've had good success and found it and the iaxclient.dll build I used with
it to be very reliable in day to day production use, however as I moved to
vs.NET 2005 I had several problems crop up with the marshaling from managed
to unmanaged memory.  For my own use, I fixed this this week -- there were a
few lines of code that needed changing -- so I'm going to at least release
that update. 

In addition, I've created a "wrapper class" around my wrapper (laugh if you
like) that provides an object oriented approach to a multi-call handling
client.  It's working very well for me, and I plan to release that code as
well when I get a few hours to generalize and document it a bit better. 

Before I do, I have some questions about the newer builds of the client
library.  I wasn't able to catch up quickly by reading sourceforge, the
wiki, documentation, or anything else online other than to look at the svn
itself.  I beg your forgiveness in light of my contributions as I ask what
may be some redundant questions.  If these questions are so redundant as to
be considered a pollution to this list, then please reply to me privately
saying so and I will stop posting -- then neither of us will further add to
the issue. 

All that said, here's what I'm looking to find out before I release a new
wrapper around the original DLL build I used: 

1.  I am using build 566 from about 1 year ago, with a patch to tell the
library to leave your mixer alone.  Surely much progress has been made
since.  Is there a definitive opinion on what the current "best stable"
build is to use for a project like this? 

2.  Is compiling the current best (see #1) still the same process under
cygwin? 

3.  Does the visual studio build produce a better or worse result for the
win32 users? 

4.  Is the current version function call compatible with the older ones, or
if I recompile will I have to re-do all the marshaling to managed memory
work I did originally? 

5.  Is there a cumulative bug & feature change list somewhere that I can
reference to see if its a good idea to update my build? 

6.  Are you still using the wrapper I built, or would you use the new one?
(aka, should I bother?) 

Thank you for your patience.