D
DraguVaso
Hi,
I have an application that uses a custom ocx. Because I need to deploy this
ocx with XCOPY and not with a setup, I need a way to get around this setup.
What I was thinking about was this: Is there a way to kind of 'include' an
ocx into an appliation, so I don't need to register it anymore on the
client-pc. I kind of wanne put the ocx into the exe-file.
And is this only necessary for ocx-files, or also for some dll's? Because it
seems that in .NET this behaviour is kind of standard for dll's?
Thanks a lot,
Pieter
I have an application that uses a custom ocx. Because I need to deploy this
ocx with XCOPY and not with a setup, I need a way to get around this setup.
What I was thinking about was this: Is there a way to kind of 'include' an
ocx into an appliation, so I don't need to register it anymore on the
client-pc. I kind of wanne put the ocx into the exe-file.
And is this only necessary for ocx-files, or also for some dll's? Because it
seems that in .NET this behaviour is kind of standard for dll's?
Thanks a lot,
Pieter