How To Create a COM+ Application Proxy That Installs Only Type Library Files

Article translations Article translations
Article ID: 292184 - View products that this article applies to.
This article was previously published under Q292184
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page

SUMMARY

COM+ application proxies usually install the component dynamic link libraries (DLLs) on client computers because the DLLs contain the type library files that are needed to support the component's interfaces in addition to the component code. Only the type library that is contained in the DLL is used on the client computer; the component code is not used. The objects still run on the remote COM+ server as expected.

This article explains how you can have a COM+ application proxy install only a type library file (.tlb) that supports your component interfaces instead of the entire DLL. This file contains only the type library and none of the component code.

MORE INFORMATION

Step-by-Step Example

NOTE: Windows 2000 Service Pack 2 or later must be installed on the COM+ application server computer for this procedure to work correctly.

  1. Generate the type library files for your component DLLs, and ensure that the .tlb file is built in the same folder as the .dll file:
    • For a Microsoft Foundation Classes (MFC) or Microsoft Active Template Library (ATL) DLL, the .tlb file is built by default.
    • For a Microsoft Visual Basic DLL, select the Remote Server Files check box on the Component tab of the Project Properties dialog box, and then build the DLL.
  2. Install both the component .dll and the typelib .tlb file into your COM+ application at the same time. To do this, you must select the Install new component(s) option and then select both files together in the Select files to install dialog box when you install your component in the COM+ application.

    NOTE: If you already installed the .dll file separately, you must delete the component and install the files together.
  3. Export the application proxy.
  4. Run the resultant .msi on the client computers. Notice that only the .tlb files are copied to the client computer.
NOTE: There is a known problem when you run the application proxy on Windows 95-based, Windows 98-based, or Windows NT 4.0-based computers. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
289821 FIX: COM+ Application Proxy Does Not Register CLSID After You Install COM+ Rollup Hotfix 5

REFERENCES

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
255973 FIX: Exporting Application Proxy in COM+ Gives Export Application Error

Properties

Article ID: 292184 - Last Review: February 27, 2014 - Revision: 2.3
APPLIES TO
  • Microsoft COM+ 1.0, when used with:
    • Microsoft Windows 2000 Service Pack 2
    • the operating system: Microsoft Windows XP
  • Microsoft COM+ 1.5, when used with:
    • Microsoft Windows 2000 Service Pack 2
    • the operating system: Microsoft Windows XP
Keywords: 
kbnosurvey kbarchive kbhowto KB292184

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com