HOW TO: Use Loosely Coupled Events from Visual Studio .NET

This article was previously published under Q318185
This article has been archived. It is offered "as is" and will no longer be updated.
Use this step-by-step guide to create a .NET assembly containing a publisher, a subscriber, and an interface for handling loosely coupled events in Microsoft COM+ Services.

back to the top


The following list outlines the recommended hardware, software, network infrastructure, and service packs that you need:
  • Microsoft Windows 2000 Professional, Microsoft Windows 2000 Server, Microsoft Windows XP Professional, or Microsoft Windows XP Server.
  • Microsoft .NET Framework.
  • Microsoft Visual Studio .NET.
  • Microsoft Visual C# .NET.
  • Microsoft COM+.
This article assumes that you are familiar with the following topics:
  • COM and Enterprise Services.
  • Extending meta data by using attributes.
back to the top

Create a .NET Assembly that Uses Loosely Coupled Events

The following procedure creates a .NET assembly containing a publisher, a subscriber, and an interface that handles loosely coupled events in COM+ Services:
  1. Click Start, point to Programs, point to Microsoft Visual Studio .NET, and then click Microsoft Visual Studio .NET.
  2. Click New Project.
  3. In Project Types, click Visual C# Projects.
  4. In Templates, select Windows Application.
  5. In the Name box, type HowToLCE, and then click OK.

    You now have a Solution containing the shell of a Windows Forms application.
  6. Create a Class Library that contains code for the publisher, the subscriber, and the interface that is shared by both. On the File menu, point to Add Project and then click New Project.
  7. In Project Types, click Visual C# Projects.
  8. In Templates, click Class Library.
  9. In the Name box, type ClassLibLCE, and then click OK.
  10. In Solution Explorer, under ClassLibLCE, right-click References, and then click Add Reference.
  11. On the .NET tab, under References, click System.EnterpriseServices and then click Select. Click OK.
  12. Add the following Using directives at the top of the Class1.cs file to access classes in these namespaces:
    using System.EnterpriseServices;using System.Diagnostics;						
    When you compile the Class Library component, it becomes a .NET assembly. After you register it, you can run it under COM+ Services because the publisher and subscriber derive from EnterpriseServices.ServicedComponents().
  13. Declare the interface these two classes will share. In the Class1.cs file, add the following code after public class Class1:
    public interface IEvSink{	void OnEvent1();	void OnEvent2();}					
  14. Replace public class Class1 with the following code for the Publisher class:
    [EventClass]public class MyPublisher : ServicedComponent, IEvSink{	public MyPublisher()	{	// 	// TODO: Add constructor logic here.	// 	}	public void OnEvent1()	{}		public void OnEvent2()	{}	}						
    Notice the preceding class is decorated with the [EventClass] attribute. This attribute is critical. It tells COM+ Services that this class forms the connection between the publisher and its subscriber(s). When you have worked through all the code in this article, notice that there are no direct calls to the MyPublisher class. In other words, the interaction between publisher and subscriber is handled by COM+ Services by the class with the [EventClass] attribute. Therefore, the publisher does not have any direct knowledge of the subscriber(s). Any subscriber registered with COM+ Services for this application that uses the IEvSink interface can receive events from the publisher.
  15. The final bit of code required in the Class Library is for the subscriber. This class handles the events fired by the publisher. In this case, you make a simple entry in the Event Log to show that the subscriber is notified when a call is made to the published interface. Add the following code after the MyPublisher class:
    public class MySubscriber : ServicedComponent, IEvSink{	EventLog ev = new EventLog("Application");	public void OnEvent1()	{		ev.Source = "ClassLibLCE";		ev.WriteEntry("OnEvent1 Fired");	}	public void OnEvent2()	{		ev.Source = "ClassLibLCE";		ev.WriteEntry("OnEvent2 Fired");	}}					
  16. To use the assembly compiled from the Class Library, give it a strong name. To generate this cryptographic key pair, use the SN tool (Sn.exe). It is located in the \bin folder where the .NET Framework Software Developer's Kit (SDK) documentation is installed. The SN Tool is very easy to use. The command line statement uses the following syntax:
    sn -k "C:\%DirectoryToPlaceKey%\%KeyName%.snk"
  17. Run this command from the Visual Studio .NET command prompt. Click Start, point to Programs, point to Microsoft Visual Studio .NET, point to Visual Studio .NET Tools, and then click Visual Studio .NET Command Prompt. At the command prompt, type the following:
    sn -k "C:\ClassLibLCE\key.snk"
    If your Class Library project is not in this path, change the path to the root of the project folder for your Class Library project.

    A key is generated. To verify this, in Solution Explorer, select ClassLibLCE and then click the Show All Files button on the Solution Explorer toolbar.

    Notice the key.snk item under ClassLibLCE.
  18. Because this key is not yet associated with the Class Library assembly, create this association. In Solution Explorer, under ClassLibLCE, double-click AssemblyInfo.cs. In AssemblyKeyFile, type the following between the existing quotation marks:
  19. Complete the code for the whole solution by wiring up a Windows Form to the Class Library. Remember that this Form is merely for demonstration purposes. It basically serves as a "test harness". Add the appropriate references.
    1. In Solution Explorer, under HowToLCE, right-click References, and then click Add Reference on the shortcut menu.
    2. On the .NET tab, click System.EnterpriseServices.
    3. On the Projects tab, click ClassLibLCE.
    4. Click Select.
    5. Click OK.

      Notice the System.EnterpriseServices and ClassLibLCE items listed under References.
  20. In the Code Editor, click the Form1.cs [Design] tab. Double-click anywhere on the Form to create a Form1_Load event handler. To this event handler add the following code.

    Notice that there are two sections. The first is solely for the purpose of registering the Class Library. It is used only one time. The second triggers the publisher events.
    // Section #1// Register Class Library as a COM+ application.    ClassLibLCE.MySubscriber l = new    ClassLibLCE.MySubscriber ();// Section #2//  Call Events on Publisher//  ClassLibLCE.MyPublisher l = new ClassLibLCE.MyPublisher();//  l.OnEvent1();//  l.OnEvent2();					
  21. Press F5 to run the application and register the Class Library.

    This makes the subscriber accessible to, but not yet registered with, COM+ Services. After the Form loads, close it. This is the simplest method of registering a .NET Assembly so that it can take advantage of COM+ Services. However, to register in this manner you must be logged on to the local computer with Administrative rights. If users who use your application do not have Administrative rights to their local computer, you can register an assembly by using the Regasm.exe utility for them when you deploy the application.
  22. Run the Component Services snap-in.

    You cannot set up subscribers by using attributes in .NET version 1.0. But, you can do this manually by running the Component Services snap-in: Open Control Panel, double-click Administrative Tools, and then double-click Component Services.

    NOTE: If you want, you can write code to automate the following steps by using the COM+ 1.0 Admin Library. For additional information, view the Library contents in the Object Browser.
  23. Expand Component Services. Expand Computers. Expand My Computer. Expand COM+ Applications. Expand ClassLibLCE. Expand Components. Expand ClassLibLCE.MySubscriber.
  24. Right-click the Subscriptions folder, point to New, and then click Subscription.
  25. In the COM+ New Subscription Wizard, click Next. Select the Subscribe to the IEvSink interface option. Click Next.
  26. In the Select Event Class page, click ClassLibLCE.MyPublisher. (This is the class that was decorated with the [EventClass] attribute.) Click Next.
  27. Enter the name you want to use and then click to select the Enable this subscription immediately check box. Click Next. Click Finish.
back to the top

Code for the Class1.cs File

using System;using System.EnterpriseServices;using System.Diagnostics;namespace ClassLibLCE{       /// <summary>       /// Summary description for Class1.       /// </summary>       [EventClass]       public class MyPublisher : ServicedComponent, IEvSink       {	     public MyPublisher()	     {	     // 	     // TODO: Add constructor logic here.	     // 	     }	     public void OnEvent1()	     {}		     public void OnEvent2()	     {}	     }	     public class MySubscriber : ServicedComponent, IEvSink	     {		EventLog ev = new EventLog("Application");		public void OnEvent1()		{			ev.Source = "ClassLibLCE";			ev.WriteEntry("OnEvent1 Fired");		}		public void OnEvent2()		{			ev.Source = "ClassLibLCE";			ev.WriteEntry("OnEvent2 Fired");		}	}	public interface IEvSink	{		void OnEvent1();		void OnEvent2();	}}				
back to the top

Code for the AssemblyInfo.cs File

using System.Reflection;using System.Runtime.CompilerServices;// // General information about an assembly is controlled through the // following set of attributes. Change these attribute values to modify// the information associated with an assembly.// [assembly: AssemblyTitle("")][assembly: AssemblyDescription("")][assembly: AssemblyConfiguration("")][assembly: AssemblyCompany("")][assembly: AssemblyProduct("")][assembly: AssemblyCopyright("")][assembly: AssemblyTrademark("")][assembly: AssemblyCulture("")]		// // Version information for an assembly includes the following four // values://      Major Version//      Minor Version //      Build Number//      Revision// // You can specify all the values or you can use the default Revision and // Build Numbers by using the '*', similar to this:[assembly: AssemblyVersion("1.0.*")]// // To sign your assembly, specify a key to use. For more // information about assembly signing, see the Microsoft .NET Framework // documentation.// // Use the following attributes to control which key is used for signing. // // NOTES: //   (*) If no key is specified, the assembly is not signed.//   (*) KeyName refers to a key that is installed in the Crypto Service//       Provider (CSP) on your computer. KeyFile refers to a file that //       contains a key.//   (*) If the KeyFile and the KeyName values are both specified, the //       following processing occurs://       (1) If the KeyName is found in the CSP, that key is used.//       (2) If the KeyName does not exist and the KeyFile does exist, the //           key in the KeyFile is installed into the CSP and used.//   (*) To create a KeyFile, you can use the Sn.exe (Strong Name) //       tool. When specifying the KeyFile, the location of the KeyFile //       must be relative to the project output folder which is//       %Project Directory%\obj\<configuration>. For example, if your //       KeyFile is located in the project folder, specify the //       AssemblyKeyFile attribute as //          [assembly: AssemblyKeyFile("..\\..\\mykey.snk")]//   (*) Delay Signing is an advanced option. For more information, see the //       Microsoft .NET Framework documentation.// [assembly: AssemblyDelaySign(false)][assembly: AssemblyKeyFile("..\\..\\key.snk")][assembly: AssemblyKeyName("")]				
back to the top

Code for the Form1.cs File

using System;using System.Drawing;using System.Collections;using System.ComponentModel;using System.Windows.Forms;using System.Data;namespace HowToLCE{	/// <summary>	/// Summary description for Form1.	/// </summary>	public class Form1 : System.Windows.Forms.Form	{		/// <summary>		/// Required designer variable.		/// </summary>		private System.ComponentModel.Container components = null;		public Form1()		{			// 			// Required for Windows Form Designer support.			// 			InitializeComponent();			// 			// TODO: Add any constructor code after the			// InitializeComponent call.			// 		}		/// <summary>		/// Clean up any resources being used.		/// </summary>		protected override void Dispose( bool disposing )		{			if( disposing )			{				if (components != null) 				{					components.Dispose();				}			}			base.Dispose( disposing );		}		#region Windows Form Designer generated code		/// <summary>		/// Required method for Designer support; do not modify		/// the contents of this method with the Code Editor.		/// </summary>		private void InitializeComponent()		{			// 			// Form1			// 			this.AutoScaleBaseSize = new System.Drawing.Size(5, 13);			this.ClientSize = new System.Drawing.Size(292, 266);			this.Name = "Form1";			this.Text = "Form1";			this.Load += new System.EventHandler(this.Form1_Load);		}		#endregion		/// <summary>		/// The main entry point for the application.		/// </summary>		[STAThread]		static void Main() 		{			Application.Run(new Form1());		}		private void Form1_Load(object sender, System.EventArgs e)		{			//Section #1			// Register Class Library as a COM+ application.//			ClassLibLCE.MySubscriber l = new ClassLibLCE.MySubscriber();			//Section #2			// Call Events on Publisher.				ClassLibLCE.MySubscriber l = new ClassLibLCE.MySubscriber();						l.OnEvent1();						l.OnEvent2();		}	}}				
back to the top

Verify it Works

  1. In the Code Editor window, comment the code in Section #1 of the Form1.cs file and uncomment the code in Section #2.
  2. Run only the executable for the HowToLCE project. To do this, click Configuration Manager on the Build menu. Clear the Build check box for ClassLibLCE. Click Close.
  3. Press F5 to run the application in debug mode.
  4. When the Form loads, close it.
  5. Press CTRL+ALT+S to start Server Explorer. Expand Servers. Expand computer name. Expand Event Logs. Expand Application. Expand ClassLibLCE.

    Notice the two Event Log entries.
back to the top


  1. Refresh the Event Log to see the entries in Server Explorer.
  2. If you make changes to the Class Library after running through the aforementioned procedures and then rebuild the Class Library it is very likely that the assembly will be locked by component services. To work around this, use either of the following methods:
    • Right-click the component in Component Services and then click Shut Down.

    • Delete the component if you want to make significant changes to your code.
back to the top

For additional information about loosely coupled events, visit the following Microsoft Web site:For additional information about how to implement and deploy COM+ configured classes, visit the following Microsoft Web site: back to the top

Article ID: 318185 - Last Review: 02/27/2014 21:11:50 - Revision: 3.3

Microsoft Visual Studio .NET 2002 Professional Edition, Microsoft .NET Framework Class Libraries 1.0

  • kbnosurvey kbarchive kbhowtomaster KB318185