NDNM3

An ActiveX Control for embedding NetMeeting in your VB/ATL apps

Features:
Provides the functionality of the NetMeeting SDK to Visual Basic and ATL programmers!

Installation:
To install this control as well as the VB6 sample application, simply run the main installation package below.
Click here to download the latest version of the control

(Update 10/8/2003)  Click here to download a redistributable version of the control

(Update 2/15/2005)  Sorry, folks, but I will no longer answer any emails asking for a sample application. Please download the main installation to get the sample app.


Licensing:
I've given up on the idea of this becoming a commercial product - I simply am too busy with other projects (that pay much better!) to be able to guarantee response times for technical support or to be able to generate documentation that meets my standards for "commercial-grade." Therefore, you are welcome to redistribute the control for free - you will have to run the installation package on the target machines either manually or as part of your application's installation, and I would greatly appreciate an acknowledgement of my contribution to your application in a readme or an about box
Something like this would be great:
NetMeeting functionality provided by Andy Hopper
http://www.hoppersoft.com

7/10/2002 - 2.0 SP3
(NDNM3.OCX version 1.0.0.6)
This version contains a fix for the VideoChannel object's ImageQuality property - valid values are 0 to 31 where 0 gives the fastest framerate with 'muddy' video and 31 gives the lowest framerate with sharp video.
Added member and video channel information forms to the AVConference sample.

6/10/2002 - 2.0 SP2
(NDNM3.OCX version 1.0.0.5)
This version of the control adds support for Windows '9X/Me, as well as bug fixes for the data and file transfer channels.

Notes:
You can change the picture displayed in the video windows by modifying the Picture property of the video window controls.

Since NetMeeting is an out-of-process COM server, you can accidentally leave it running after your application is closed. This happens most often when an unhandled runtime error occurs or when you leave VB at a breakpoint while in debug mode, so be careful to use error handlers.

Only one instance of NetMeeting can run at any time, so if your users start NetMeeting in parallel with your application, they will 'hijack'
any conferences in progress.

Support:
For technical support, you may contact me at Andy.Hopper@mindspring.com, but I can't guarantee a timely response.

Back to the HopperSoft.com home page