Home > Articles > Web Services > XML

Designing COM+ Applications with a Web Service Appeal

.NET, COM, COM+, and Web Services—can they all get along? You bet! Not only can you create COM applications with .NET, but you can also create COM+ applications that are usable as Web services. Find out how.
Like this article? We recommend

One of the more interesting preconceptions that developers have about working with .NET is a perceived lack of compatibility with older applications. Some developers don't use .NET because they think it's going to be hard to get it to work with their existing applications.

Nothing could be further from the truth. Not only can you create COM applications with .NET, but you can also create COM+ applications, and then make those COM+ applications usable as Web Services. In short, you can write one .NET application and have it serve any of a number of environments, even those that appear on other platforms.

You can create COM or COM+ components with equal ease using .NET. In fact, the same component can serve both environments. All you need to do is create a Class Library project and add your code to it. You don't have to do anything weird to make your code accessible to VB6 or VC++ developers.

That said, you do need to add a few custom attributes and give your component a strong name to ensure it works properly. In addition, you need to provide an interface to ensure COM can actually see the methods.

All of these needs are relatively easy to address. Listing 1 shows the simple component used for this example.

Listing 1: Creating a Simple Class for Use with COM or COM+

namespace MyMathClass
   public interface ISimpleMath
      Int32 DoAdd(Int32 Input1, Int32 Input2);
      ... Other Methods ...

   public class SimpleMath : ServicedComponent, ISimpleMath
      public SimpleMath()

      public Int32 DoAdd(Int32 Input1, Int32 Input2)
         return Input1 + Input2;

      ... Other Methods ...

Let's begin with the interface. You must create an interface for the class because COM and COM+ might not see the methods you expose otherwise. The interface must include two attributes: [Guid], which contains the Globally Unique Identifier (GUID) for the interface, and [ComVisible], which makes the interface visible to COM and COM+. You'll find that .NET automatically provides a GUID for you if you fail to include the [Guid] attribute, but you'll quickly find that this approach can leave your registry with tons of orphaned entries. Adding the [Guid] attribute is quick and easy, so it makes sense to use it to save time.

You might wonder where the mystery number for the [Guid] attribute comes from. Select the Tools | Create GUID command, and you'll see the Create GUID utility shown in Figure 1.

Figure 1Figure 1. The Create GUID Utility.

Select option 4, as shown, and click Copy to place the new GUID on the clipboard. Paste the result into your code and remove the curly braces from either end of the GUID.

The class comes next. Notice that you must implement the interface in your class to create the required linkage. Like the interface, the class uses the [Guid] attribute, but not the [ComVisible] since the interface makes the methods public. The GUID you use for the class must be different from the one you used for the interface. The [ClassInterface] attribute contains one of the ClassInterfaceType enumeration values. I recommend that you alway use AutoDual, unless you have a good reason to choose one of the other options (such as making the component available to only VB6 or only VC++ developers).

Notice that this class inherits from the ServicedComponent class. This entry isn't too important when you want to use the component for COM or COM+ work, but Web services require it. If you don't include this entry, COM+ exports the basic interface information, but won't create the required method declarations; COM+ appears to create the Web service and even IIS seems to show that the Web service will work, but you won't be able to access the methods in the Web service.

You'll find the ServicedComponent class in the System.EnterpriseServices namespace. Theoretically, you can also inherit from the Component class, which results in a less complex implementation, but it can also introduce problems in using the Web service in some cases (the export isn't as precise as it could be).

The code for the class isn't anything special. I just put something together for demonstration purposes. Any code you normally use for a .NET class will work in most cases. However, in special situations you have to use the InteropServices namespace members, such as the Marshal class to create a bridge between .NET and the Win32 environment.

Creating the code is a good start, but you must perform one additional task: give the component a strong name. To do that, open a command prompt and use the:

SN -k MyKey

command to create a key pair. This key pair signs the component to ensure no one can tamper with it. You add the strong name to the AssemblyInfo file using code, like this:

[assembly: AssemblyKeyFile(@"..\..\MyKey")]

Now you can compile the component. It's ready for use as either a COM or COM+ application.

Registering the Component

Unlike .NET applications, you must register COM and COM+ components for use. However, you don't use the normal RegSvr32 utility to perform this task with .NET components; instead, you use the RegAsm utility.

The RegAsm utility has more than a few command line switches, and I won't go into all of them in this article. However, you won't normally need to use all of those switches, especially when working with COM+. The example component creates MyMathClass.DLL. To register this class in such a way that COM+ can use it, you'd type:

RegASM MyMathClass.dll /tlb:MyMathClass.TLB

at the command prompt and press Enter. RegAsm will create all of the required registry entries to use MyMathClass. In addition, it creates a type library that you must have to add the component to COM+.

Before you make any changes to the code or recompile the component, make sure you unregister the component from the registry. Again, you use the RegAsm utility to perform this task. Here's the command line for this example:

RegASM MyMathClass.dll /unregister

Using RegAsm is good enough when you want to use COM+ alone. However, in this example, we also want to access the component as a Web service. To make the component usable at this level, you must also register it in the Global Assembly Cache (GAC) using the GACUtil utility. Like RegAsm, GACUtil includes a number of interesting switches you won't normally use. To register the example component, simply use this command:

GACUtil -i MyMathClass.dll

Removing the assembly from the GAC is equally easy. Simply use this command (notice that the DLL extension is omitted).

GACUtil -u MyMathClass

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020