COM DLL METHOD SLOW IN WEB APPLICATION BUT FAST IN WINDOWS APPLICATION

Hot Topic

regarding datasets
help: c# console output system.byte[]
.net 1.1, WebProxy.GetDefaultProxy() not functioning
can i get the type of an unreferenced object?
How do I use this method: " Private Shared Sub AssignParameterValues "
unmanaged c++ class in c#
Storing MailMessage?
Javascript Validation in ASP.Net
WebBrowser (VS2.0) on UserControl
list of files from another web server?

.NET Development

JScript When Disabled
SslStream and AuthenticateAsServer
Timeout in WinHttp object
Constraint Error Handling
SQL MOBILE - Cannot find data source
Listbox.Items.RemoveAt question/problem - possible solution
TCP Async Callback problem
How to do a programmatic update of table
Text in XSLTransform
Socket performance

COM DLL METHOD SLOW IN WEB APPLICATION BUT FAST IN WINDOWS APPLICATION

We have developed an application using ASP.NET/C# which uses COM api. We figured out that API methods are relatively slow in Web Application but the same code, same method if i try to use in a window based application, it is extremely fast. Please let us know, if what could be the reason.


Answer this question

COM DLL METHOD SLOW IN WEB APPLICATION BUT FAST IN WINDOWS APPLICATION

  • _Ed Noepel

    The COM DLL is a third party supplied  developed in Visual Basic.  The DLL Which if try to use in ASP.NET Web Application is slowing down rapidly.  But the Same operation if i try to carry out in ASPorVB it is extremely fast.

    I thought that the delay might be due to the interop which creates that delay.  But i tried with sample .NET windows application which uses this interop dll and executes extremely fast.

    I am wondering that interop Dlls will it behave differently for Web and Windows based applications. 

    Please throw lights on my thoughts.



  • CharlestonSW.com

    I am using C# to access COM dll interop.  The Same SLL if i try to use in asp it works fine.  But the interop dll  is creating me lot of problems.



  • Jobr77

    I can't think of any reason, but to help you identify your case...
    are you using C# to access a COM dll using COM interoperability, or to access a legacy (native) dll (for instance win32 API)

  • xhh

    well... COM interoperability works fine for me and I've never heard of any problems. Of course calling a COM object is not as fast as calling a .NET object, since interoperability adds some overhead, but what you are talking about seems to be something else.
    I think you are going to go deeper to find your answer. Try for instance some code optimizations. If you are using the COM object inside a .NET loop, try to transfer the loop inside your COM object to minimize the call overhead.


  • COM DLL METHOD SLOW IN WEB APPLICATION BUT FAST IN WINDOWS APPLICATION
Answer this question