Problems start after compile
I have an application that analyzes html from a list of website and provides are report based on the results. I am using the inet component to grab the html.
When I run the app from the VB IDE, it goes very quickly and provides accurate results. After I compile the application, it slows down considerably (IDE runs are about 100-200 times faster than compiled runs). I thought I might be referencing two different msinet.ocx files but they are the same. I also looked for any indication that I need to somehow initialize the inet control. Again - nothing.
Does anybody have any suggestions.
I am getting the html as follows:
================
strGet= Inet1.OpenURL(url)
Do While Inet1.StillExecuting
DoEvents
Loop
I then analyze the contents of strGet
Any help is greatly appreciated.
EDIT: I just wanted to add that I have confirmed through logging that the slow down is when the inet.OpenURL is called.
Re: Problems start after compile
You are going to need to put some timing code in your app to find the exact place where this "Slow Down" happens. You can use ******* in my signature to help you do this, or you can use a VB Analyzer ($$$$) to time your functions.
You can also not do DoEvents on each iteration in your loop. Do it on every tenth iteration to see if there is any difference.
I have never seen where an exe runs slower than interpeted code in the IDE.
Re: Problems start after compile
Well, the jam up is definitely occurring at the inet1.OpenUrl call. I even commented it out of the code and rebuilt the exe to make sure. I fooled around with the DoEvents as well - but I couldn't detect any difference between the builds.
I also unplugged my connection and it runs without delay. So it is almost like there is something else competing for the inet control when I run the exe. My thought is that the IDE must be doing something to initialize or manage requests to the control that my code does not do.
Any thoughts?
Re: Problems start after compile