When you install SP2 you get the ServicePackFiles in your Windows folder. Depending on your computer setup you may also have an I386 folder there, too. When you install IIS it will try for the I386 folder and if that fails it will ask for your CD. If you
patch your I386 (using the -s command line) you're all set, otherwise (and someone correct me if I'm wrong here) Windows will combine the CD's I386 folder with the ServicePackFiles folder to give you the SP2 version of IIS.
I'll grant that there was a big learning curve jumping from VB6 to .Net. But for those that haven't jumped yet because they're "missing that magic of VB6" they'll hopefully be happy with .Net 2. The biggest thing for me is the background worker thread
object, quite possibly my favorite addition to the framework/language.
But also you can still use tons of old VB6 code. "Dim RS as New ADODB.RecordSet" still works if you add a reference to the ADO library (just as in VB). CInt, CDbl, CBool are all there. Sure, we lost control arrays, but we gained so much. There's tons of power
available now, you don't need to use it if you don't want to, but its still there.
How is the Live Comms Server actually connected to the PBX?
Same question here. I assume you guys don't have your individual phones connected to your desktop computer directly since most modern desktop machines only have modems available as extras add-ons. So does the PBX actually take the phone off the hook and dial
it for you? I was looking for a whitepaper on this but couldn't find anything.
We use Act! here which has a TAPI interface to dial phones but its pretty clumsy (no offense to the TAPI developer earlier). This might be a better solution and I'd like to know more about it.