dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: VB6,MTS,COM+
Expertise: beginner
Dec 15, 2001

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Make COM objects in a COM+ application visible to clients

What I describe for COM+, applies to MTS with some slight differences as well.

Registering COM objects remotely has been quite a pain before MTS showed up (remember the VBR file?). In COM+ it's very easy to do:

1) Right click on the COM+ application and choose export Choose application proxy, choose the export package file name (.msi file)
2) Go to the client, run the .msi file, (make it accessible to the server creating a proper share), you are done.

Watch out there is a bug in W2K SP2 that produces a bad .msi file that don't register the component correctly. Get the proper post SP2 fix from MS before SP3 will be released.

The other export option you have in W2K is conceived to deploy an exact copy of the COM+ App to another server. In MTS you do not have these two options separately. The export option in MTS produces both kind of exports. The export for the client is the exe file in the client subdirectory.

Enrico Sabbadin
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
×
We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.
Thanks for your registration, follow us on our social networks to keep up-to-date