Printable View
Here is my problem, I developed COM on the A server and an interface written by VB running on B client. Now, my program is completed and want to distribute to the customer. How can I do that? How can I distribute my COMs to other server and how to install my interface program on other clients. Can I pack everything in one install by using Install Shield? If so, how? Any suggestion or ideas are welcome. Thank you in advance.
Hi there,
You should use some SW like the package & Deployment wizard to make a package of your client project.
If your COM Server is a DLL, then you should include the dll in the package.
If your server is an EXE, you will then need to recompile it with the tiny difference of creating a remote server file from Project properties->Component. When compiling the EXE with this feature, VB will create for you a DCOM extension to your server, a TLB file. This file will then be needed in your client package, and to run of course it should exist in the same LAN, you just state security properties and the server the COM server is installed.
Hope this helps a little,
André
I am trying to test with COM and these are the problems that I have encountered.
With the Server-side of the program, I do not encounter any problem anymore. The only question with the Server-side is, do I need to run the EXE everytime a client (same machine or not) needs it? (even if I have setted the 'Unattended execution' option checked)
How do you register the EXE in the server? Is it not done by creating the EXE in VB? Do I need to register it similar to DLL's?
With the client-side, I have encounter these two problems:
1.) Active X object can not be created.
2.) Remote machine can not be located or does not exists.
I have setted the client COM component to access the ActiveX object from the Server and these are the errors that I encounter.
Please explain the possible cause of the error.
Alot of the issues you are facing are described in msdn. I suggest you used a couple of minutes searching in http://search.microsoft.com/us/dev/default.asp for keywords such as distributing COM applications, register server components, type in the exact error message you get and you will see that you are not the first to encounter them. I guess this is better than me writing a brainstorm for you. But if I have the time I'll will try to help you more, ok?
Regards,
André