Scott M.
8/8/2008 9:48:00 PM
Well, as I said, there's not much you can do about performance with COM
InterOp bottlenecking your code.
<selain@libero.it> wrote in message
news:31b1cc98-b03f-4807-a917-95d1be3f5ed3@34g2000hsh.googlegroups.com...
>I tried what you told me bu speed remained the same.
>
> Also it seems that if i disconnect the network cable the problem never
> shows (tha application has nothing to do with the network)
>
> I'm a bit confused ..
>
> On 18 Lug, 00:00, "Scott M." <s-...@nospam.nospam> wrote:
>> COM InterOp is inherantly going to introduce a performance bottleneck.
>>
>> There's not too much you can do about increasing performance, other than
>> making sure that you are releasing the COM objects from the CLR by
>> calling
>> Marshal.ReleaseComObject(obj) when you are done with the COM reference in
>> your managed code.
>>
>> - Scott
>>
>> <sel...@libero.it> wrote in message
>>
>> news:37fad700-3cc6-477a-9e61-4ebffbfb807e@d45g2000hsc.googlegroups.com...
>>
>>
>>
>> > Hi, i've got a problem with dotnet framework 2 and the tidestone
>> > component f1book.
>> > I've got an application built with visual studio 2005 that use the
>> > f1book component (so it creates the interop layer dlls do comunicate
>> > with the component).
>> > On certain computers it becomes incredibly slow to perform the
>> > features, i'm almost sure that the problem is in COM interop when i
>> > call the component methods, does anyone have any suggestion to tweak
>> > it up ?- Nascondi testo citato
>>
>> - Mostra testo citato -
>