Problems with COM-Objects

14 Dec 2006 8:34 PM

Greg Cyrus

Hi,
I am using a COM-Object within a dotnet v1.x application.
The COM-Object works quite "fine" on the computer where the deveoping
environment runs.

BUT when I launch the application on another Computer the COM-Objekt slows
down dramatically.
(each interaction such like sending or getting data takes nearly 10x more)

Is there something to register on the target computer to ensure better
performance or soething else to care about?

Greetings and thanx in regard
Greg

P.S: Compiling the app on the target computer the IDE notices that a "never
wrapper is available for the COM-Object".

14 Dec 2006 9:46 PM

Scott M.

Does your code use the Marshall class to release the COM object from the
CLR?

Show quote

"Greg Cyrus" <nomail@invalid> wrote in message
news:elscea$cra$03$2@news.t-online.com...
> Hi,
> I am using a COM-Object within a dotnet v1.x application.
> The COM-Object works quite "fine" on the computer where the deveoping
> environment runs.
>
> BUT when I launch the application on another Computer the COM-Objekt slows
> down dramatically.
> (each interaction such like sending or getting data takes nearly 10x more)
>
> Is there something to register on the target computer to ensure better
> performance or soething else to care about?
>
> Greetings and thanx in regard
> Greg
>
> P.S: Compiling the app on the target computer the IDE notices that a
> "never wrapper is available for the COM-Object".
>

17 Dec 2006 8:57 PM

Greg Cyrus

> Does your code use the Marshall class to release the COM object from the
> CLR?

it does but the COM-Object is slow from the beginning (first instance of
COM-Object) - but what I have recently noticed is that the versions of the
COM-Object are not equal..
So I think it might be the problem that the Runtime-Callable-Wraper-class
specifies the COM-Object-Version on the compiling computer and when running
on the target-computer the RCW-class doesn't really match to the COM-Object
of the target-computer.

Greg