471,319 Members | 1,226 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,319 software developers and data experts.

c# Enterprise Services

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

Jan 16 '06 #1
4 3588
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]
- mv*@spam.guard.caspershouse.com

<ch*********@gmail.com> wrote in message
news:11*********************@g49g2000cwa.googlegro ups.com...
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

Jan 16 '06 #2
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
Jan 16 '06 #3

"Michael Nemtsev" <ne*****@msn.com> wrote in message
news:9c**************************@msnews.microsoft .com...
| 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.

Jan 16 '06 #4
Michael,

You don't need a COM+ proxy, but you do need a SOAP proxy, of course.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Michael Nemtsev" <ne*****@msn.com> wrote in message
news:9c**************************@msnews.microsoft .com...
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

Jan 16 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by wycklk | last post: by
4 posts views Thread by mark | last post: by
reply views Thread by desmcc | last post: by
reply views Thread by rosydwin | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.