|
-
Sep 1st, 2001, 05:52 AM
#1
Thread Starter
Frenzied Member
Hey MTS User . . .
Right . . .
COM+ doesn't have packages it has configured applications (jsut a point)
You will need to export the configured application (right-click, Export) This will create an MSI or Windows Installer file.
You can choose whether you want all of the code to be installed on the client, or whether you want remote access - in which case choose the option that allows you to export an application proxy.
Thi should solve your problem.
And I agree, compared to MTS/COM, COM+ is very weird to work-with. It's behaviour also appears to be a little inconsistent - try updating live applications - somethimes you have to remove them from the COM_ subsystem which is real pain
Hope this Helps
-
Sep 2nd, 2001, 04:07 PM
#2
New Member
Thanks dude! Light at the end of the tunnel, although I have yet to implement it.
So what happens with ASP?
Do you carry out an install on the server holding IIS?
Have I just opened another can of worms?
I'll get back once I can get the dll's spinning.
-
Sep 3rd, 2001, 04:56 AM
#3
Junior Member
Registering components with W2K
Don't anybody forget that registering with W2K (unless a local machine administrator) is Profile specific! If you register something as anyold user, then some other users who log into that PC won't be able to use the components!
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|