One thing I never quite figured out is how exactly I should write and deploy client applications that uses MTS/COM+ component.
I have been writing MTS components for a long time. I usually just test them as if they were local components in simple client applications. I never had to write client side applications. I am wondering if there are any steps that are particular to using MTS components in VB client. Under DCOM, client application simply references type library generated by the DCOM Active EXE. What about under MTS? I know I can export MTS packages, and one thing it generates is client executable.
I guess what I am after are two scenarios:
(1) If I had to write a client application on the same computer where I write my MTS component, what is the right way to reference the MTS component in the client application, and is there any special steps involved in deploying the client application?
(2) If I had to write a client application using MTS component sitting on a remote computer, how exactly do I reference the MTS component? (Is it all I have to do is to run the exe in the MTS export directory on the computer where the client application is being written, and that would generate the necessary entries in registry or tlb files?) Again, if I had to deploy the client application to another computer, is there any special steps involved?
In addition, just to round off my questions: what scenarios have anyone come across where it is necessary to use MSMQ? I must admit that I never ever had to use that feature ever.
Now that MTS/COM+ is no longer being embraced by Microsoft, and .Net remoting (such as XML over SOAP and Web Services) is being heavily promoted as a replacement technology, I think now is a good time to find out the rest of the MTS/COM+ that I never had to learn, before they become ancient history.
Thanks in advance
I have been writing MTS components for a long time. I usually just test them as if they were local components in simple client applications. I never had to write client side applications. I am wondering if there are any steps that are particular to using MTS components in VB client. Under DCOM, client application simply references type library generated by the DCOM Active EXE. What about under MTS? I know I can export MTS packages, and one thing it generates is client executable.
I guess what I am after are two scenarios:
(1) If I had to write a client application on the same computer where I write my MTS component, what is the right way to reference the MTS component in the client application, and is there any special steps involved in deploying the client application?
(2) If I had to write a client application using MTS component sitting on a remote computer, how exactly do I reference the MTS component? (Is it all I have to do is to run the exe in the MTS export directory on the computer where the client application is being written, and that would generate the necessary entries in registry or tlb files?) Again, if I had to deploy the client application to another computer, is there any special steps involved?
In addition, just to round off my questions: what scenarios have anyone come across where it is necessary to use MSMQ? I must admit that I never ever had to use that feature ever.
Now that MTS/COM+ is no longer being embraced by Microsoft, and .Net remoting (such as XML over SOAP and Web Services) is being heavily promoted as a replacement technology, I think now is a good time to find out the rest of the MTS/COM+ that I never had to learn, before they become ancient history.
Thanks in advance
