How to use remotely installed OCX control?

[Indra Bisen]

Hi,


I am designing an windows application in which we would like to use an
OCX control which is installed on server. Actually, we cannot
installed this ocx control on client machines we have to use it only
on server machnies.

Whether it is possible using .net reomoting or not? (I'm not sure)
If Yes, please give some idea.

regards,

Indra Bisen

[Günter Prossliner]

Hallo Indra!

Post by Indra Bisen
I am designing an windows application in which we would like to use an
OCX control which is installed on server. Actually, we cannot
installed this ocx control on client machines we have to use it only
on server machnies.

When you use the OCX only in Server code this would not be a problem.

But I imagine that you want to use it in the Client e.g. in the UI.

Post by Indra Bisen
Whether it is possible using .net reomoting or not? (I'm not sure)
If Yes, please give some idea.

Of cause not.

To execute code on the Client the modules have to be on the client. Or at
least they have to be registered on them. You may register then on a UNC
location, or you may distribute them to the client and then install them
transparently.

But what I don't understand is that you already have a Client-App why don't
you just deploy the OCX along with that. If you use a Browser as the UI (IE
for OCX), be aware of the auto-deploy mechanisms (codebase="...").


GP

[Indra Bisen]

Hallo Günter,
Thanks for reply.

regards,

Post by Günter Prossliner
Hallo Indra!

Post by Indra Bisen
I am designing an windows application in which we would like to use an
OCX control which is installed on server. Actually, we cannot
installed this ocx control on client machines we have to use it only
on server machnies.

When you use the OCX only in Server code this would not be a problem.
But I imagine that you want to use it in the Client e.g. in the UI.

Post by Indra Bisen
Whether it is possible using .net reomoting or not? (I'm not sure)
If Yes, please give some idea.

Of cause not.
To execute code on the Client the modules have to be on the client. Or at
least they have to be registered on them. You may register then on a UNC
location, or you may distribute them to the client and then install them
transparently.
But what I don't understand is that you already have a Client-App why don't
you just deploy the OCX along with that. If you use a Browser as the UI (IE
for OCX), be aware of the auto-deploy mechanisms (codebase="...").
GP