Hello,
I developed a Windows Form Control, and put a COM wrapper around it. The
control runs correctly on my development machine, but when I deploy it to
other machines (using VS Setup utility), some of the functions in the control
take up to 3 minutes to return (I found the functions by writing to a text
file at entry and exit times). An example of such a functions is the
ListBox.SetSelected(...) method - it took over 3 minutes to return. I am
starting to think that maybe the slow run time is because of some kind of
incorrect interop functionality has anyone else ever encountered such a
problem? Anyone has suggestions?
PS. I know that this is a public domain and some might not want their
answers to be scrutinized by the whole community, but I really need help - so
if you even think that you know what's going on, please email me at livshitz
on the domain purdue, extension edu.
Thanks in advance,
Yuri
Robert Jordan - 24 Sep 2004 23:22 GMT
> Hello,
>
[quoted text clipped - 7 lines]
> incorrect interop functionality has anyone else ever encountered such a
> problem? Anyone has suggestions?
It's not clear what you have done:
- a .NET UserControl registered as an ActiveX control
- a COM control (non visual) that opens a new Windows.Form
Supposing it's an ActiveX control: what's the host for
the control? The framework supports only MFS 7.1 and IE containers.
bye
Rob