How to install a client that references a COM+ object

[Frank Vella]

This has never been posted before so I believe all of you know how to install a client on any machine within a windows2000 professional system that references a com+ obj(dll). How in the world do you do this!!

Problem: Can not get our Package and deployment wizard to package up and deploy using the com object that has been set up during our developement process...

During developement if you install the .msi onto the visual basic debugger (project file is on the server with the com object) and then make reference to that X.dll then everything works fine, in debug mode (all the com objects are spinning visually on the server ). No security option is selected on the Com+ server.

However when I create a setup package I keep getting an "unable to load dll error" and I can not see the spinning on the server anymore.....any advice would be appreciated....thanks..

P.S When I tried copying all the files to my local machine and then run the program in debug mode the program works BUT the com objects do not spin which leads me to believe my install wizard inherits the same problem and therefore the clients will never get installed correctly!!!!!!!!!!! Please respond to this post as I have not gotten my email problems solved as of yet.

[Frank Vella]

Thanks for your reply, I have a component that will be used by multiple desktop applications. The com+ commponent is built in visual basic. (I have created a dll in process component and have made reference to it through the references in visual basic for the other client programs).
When I am in visual basic and am debugging I can see that I am hitting the com+ component because the objects in the console on the server are spinning. However when I go to package and deploy using the PDW I am almost certain that the deployment wizard grabs the dll as if it were being referenced by a standard dll. When we deploy, the com+ component never activates and I allways get a "dll not loaded error 48" as soon as I load up the client. If that can clear it up I pray for some ideas.........

ps. We do use the Enterprise Edition, and I am using a server that is local to our Domain Controller. (Not sure if that is remote or not....)

Late breaking newsss.....we have found our problem thank you again for attempting to help. When we instantiate our objects in visual basic I was using the NEW keyword. It cost us an instance with microsoft but they let me in on a little secret, use CreateObject.....sure for you vbscripters using the internet this was obvious, but to vb desktop never doing com+ before, well you know you live and you learn......later