ClickOnce and Com dll

  • Thread starter Thread starter Harry Strybos
  • Start date Start date
H

Harry Strybos

Hi Guys

Maybe this has been asked before however I am not able to find a reference
to it.

I have a project that uses a com .ocx. Sure, the interop does all that ok
and the project works fine in the DVE (because the ocx is installed and
registered on my development pc).

However, when I publish this project to my users (network) via ClickOnce,
the .ocx is not installed (or registered) on the target system.

Can I fix this and if so, how?

Thank you
 
Hi Guys

Maybe this has been asked before however I am not able to find a reference
to it.

I have a project that uses a com .ocx. Sure, the interop does all that ok
and the project works fine in the DVE (because the ocx is installed and
registered on my development pc).

However, when I publish this project to my users (network) via ClickOnce,
the .ocx is not installed (or registered) on the target system.

Can I fix this and if so, how?

Thank you
Click to expand...

In project properties, references, have you set CopyLocal to true?
This means the OCX will be used from a local copy in your application
directory, which I believe is essential for ClickOnce.
 
Mark said:
In project properties, references, have you set CopyLocal to true?
This means the OCX will be used from a local copy in your application
directory, which I believe is essential for ClickOnce.
Click to expand...

Yes, the .ocx is set to CopyLocal, however, ClickOnce does not install it to
the client.
 
Back
Top