I converted an ActiveX COM dll application written in VB6 to VB.Net.
In this VB6 application, there was a CreateObject call to another ActiveX Object which is activated on a remote server.
The statement is as follows:
CreateObject("HRA.NQAGGR")
The above statement takes less than 0.5 secs to execute.
On conversion to VB.Net, the above statement remains same in VB.Net.
CreateObject("HRA.NQAGGR")
But, in this VB.Net application this single call takes exactly 25 secs to execute, each and every time, even though it called multiple times one after the other.
Both the VB6 Object and VB.Net are run on the same COM server. A proxy exists for the remote "HRA" object on the COM server.
I even tried adding a direct reference to the remote object and tried creating the object using New, but still takes exactly 25 seconds.
I do not have access to the source of the remote object. Other ActiveX objects that I have created in VB.Net are activated instantly.
Main question is why it takes so long creating this particular object from VB.Net compared to VB6.
Submit an article or tip