Occasional rantings about Dynamics CRM, Power BI, SharePoint, Office 365, Power BI and the application blocks in Azure. Intrigued about how people collaborate and data driven decision making. Taking the first small steps in machine learning. Putting all of the above in practical use to help companies "embrace" their customers
Wednesday, September 28, 2005
Developing with Office Communicator - sample code
Presence Controls for Microsoft Office Communicator 2005 - The Presence Controls are designed to provide presence information and real time collaboration options to Microsoft Windows Forms, Web Forms and GUI applications that are based on the Microsoft Win32 application programming interface. The controls provide developers of these applications with the ability to drag-and-drop the control from the toolbox in Visual Studio onto applications and provide access to the capabilities of Communicator in an easy to incorporate manner.
Role Agent for Microsoft Office Live Communications Server 2005 - Role Agent is a sample Microsoft Windows service application that implements a role-based messaging agent for managing sessions and for brokering and dispatching instant messages between users and members of a defined group. The RoleBot sample application is built on the .NET Framework and is written in C#. The base component of this application is a base class derived from the Real-time Communications (RTC) API 1.3. The RTC API 1.3 contains a set of COM interfaces and methods for building real-time communications applications and the interop assembly used in this application provides a managed wrapper for the API.
Group Alerts Sample for Microsoft Office Live Communications Server 2005 - The group alerts sample application provides a simple user interface for sending instant messages to the online members of an Active Directory group or distribution list and its subgroups. The names of available groups for alerting are stored in a configuration file between application sessions. The user may also type the name of a group to add an existing Active Directory group to the list. The sample application uses Active Directory as its catalog, but application developers can easily modify the application to use any catalog that suits their organization.