Hi All,

I want to invoke a Serviced Component (COM+) lying on a remote machine
from my Web application without manually installing a proxy for the
remote com+ component.

Please suggest the options available for me.

Regds
Chakree

Chakree,

Hmm, that's a tough one. If you designed the component properly
(separating interface definitions from implementation), then you ^might^ be
able to make a call to the static GetTypeFromProgId method on the Type
class, passing the program id of the component and the name of the remote
machine. Then, you can pass that type to the static CreateInstance method
on the Activator class and cast the return result to the interface type.

However, I don't know that this will work. You will have to install the
proxy, most likely, in order to make this work.

Hope this helps.

--
- Nicholas Paldino [.NET/C# MVP]
- (E-Mail Removed)

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi All,
>
> I want to invoke a Serviced Component (COM+) lying on a remote machine
> from my Web application without manually installing a proxy for the
> remote com+ component.
>
> Please suggest the options available for me.
>
> Regds
> Chakree
>

Hello Nicholas Paldino [.NET/C# MVP],

What if to use SOAP Services? U need not to use proxy

N> Hmm, that's a tough one. If you designed the component properly
N> (separating interface definitions from implementation), then you
N> ^might^ be able to make a call to the static GetTypeFromProgId method
N> on the Type class, passing the program id of the component and the
N> name of the remote machine. Then, you can pass that type to the
N> static CreateInstance method on the Activator class and cast the
N> return result to the interface type.
N>
N> However, I don't know that this will work. You will have to
N> install the proxy, most likely, in order to make this work.
N>
N> Hope this helps.
>> I want to invoke a Serviced Component (COM+) lying on a remote
>> machine from my Web application without manually installing a proxy
>> for the remote com+ component.
>>
>> Please suggest the options available for me.
>>
>> Regds
>> Chakree
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/members/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsch

"Michael Nemtsev" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
| Hello Nicholas Paldino [.NET/C# MVP],
|
| What if to use SOAP Services? U need not to use proxy
|
| N> Hmm, that's a tough one. If you designed the component properly
| N> (separating interface definitions from implementation), then you
| N> ^might^ be able to make a call to the static GetTypeFromProgId method
| N> on the Type class, passing the program id of the component and the
| N> name of the remote machine. Then, you can pass that type to the
| N> static CreateInstance method on the Activator class and cast the
| N> return result to the interface type.
| N>
| N> However, I don't know that this will work. You will have to
| N> install the proxy, most likely, in order to make this work.
| N>
| N> Hope this helps.
| >> I want to invoke a Serviced Component (COM+) lying on a remote
| >> machine from my Web application without manually installing a proxy
| >> for the remote com+ component.
| >>
| >> Please suggest the options available for me.
| >>
| >> Regds
| >> Chakree
| ---
| WBR,
| Michael Nemtsev :: blog: http://spaces.msn.com/members/laflour
|
| "At times one remains faithful to a cause only because its opponents do
not
| cease to be insipid." (c) Friedrich Nietzsche
|
|

Yes, you'll always need a proxy, you need the interface descriptions at the
client side. For COM+ services you need to export the service proxy and
include it as part of your deployment.

Willy.

Michael,

You don't need a COM+ proxy, but you do need a SOAP proxy, of course.


--
- Nicholas Paldino [.NET/C# MVP]
- (E-Mail Removed)

"Michael Nemtsev" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hello Nicholas Paldino [.NET/C# MVP],
>
> What if to use SOAP Services? U need not to use proxy
>
> N> Hmm, that's a tough one. If you designed the component properly
> N> (separating interface definitions from implementation), then you
> N> ^might^ be able to make a call to the static GetTypeFromProgId method
> N> on the Type class, passing the program id of the component and the
> N> name of the remote machine. Then, you can pass that type to the
> N> static CreateInstance method on the Activator class and cast the
> N> return result to the interface type.
> N> N> However, I don't know that this will work. You will have to
> N> install the proxy, most likely, in order to make this work.
> N> N> Hope this helps.
>>> I want to invoke a Serviced Component (COM+) lying on a remote
>>> machine from my Web application without manually installing a proxy
>>> for the remote com+ component.
>>>
>>> Please suggest the options available for me.
>>>
>>> Regds
>>> Chakree
> ---
> WBR,
> Michael Nemtsev :: blog: http://spaces.msn.com/members/laflour
>
> "At times one remains faithful to a cause only because its opponents do
> not cease to be insipid." (c) Friedrich Nietzsche
>
>