Exporting the COM+ Application

Author Topic: Exporting the COM+ Application  (Read 3885 times)

Offline beingchinmayTopic starter

  • Trade Count: (0)
  • Jr. Member
  • **
  • Thank You 1
  • Posts: 73
  • Karma: 0
  • Gender: Male
  • I am Chinmay
    • Modular Kitchen Designer
Exporting the COM+ Application
« on: 08-26-2016, 03:54:49 »
The COM+ component now resides on the server, and a client could access it through the COM+ application. However, COM relies on a proxy and stub to make communication between the client and server seamless. Unlike DCOM, where you have to use different calls to access a remote component, COM+ applications use the same call. Using this technique means you must create a local proxy for the client. This proxy will take the place of the component on the server from the local machine’s perspective. Creating a proxy is relatively easy; the following steps will show you how.

1. Right-click UserADLog in Component Services, then choose Export from the context menu. You’ll see a Welcome to the COM Application Export Wizard dialog box.

2. Click Next. You’ll see an Application Export Information dialog box. This is where you’ll choose the name and type of export application created. We need a proxy application, in this case, so that the installation routine will direct UserADLog requests to the server, not to the local machine.

3. Click Browse. You’ll see an Export Application to File dialog box. Choose a location for the installation program. The wizard automatically gives the application an MSI extension. The example uses an installation program name of UserADLog Install, but you can use any name you wish


Related Topics

  Subject / Started by Replies Last post
2 Replies
Last post 08-26-2011, 11:23:55
by takeshiro
0 Replies
Last post 10-13-2011, 02:17:58
by manvbf
3 Replies
Last post 04-16-2012, 18:09:32
by fizzer
16 Replies
Last post 12-17-2020, 23:21:49
by Ensafeindia
0 Replies
Last post 08-26-2016, 04:00:37
by beingchinmay