I wish I knew what was taking the extra 30 seconds. I am stumped. What do you mean by "profiling"?



I have combed the code both in the program.cs and the initial form that fires up. I do not see anything that stands out. The only thing that I have left to me is to start whacking at the current code...remove all suspected intensive operations, then add them back in one at a time to see which is the culprit. I really do not want to do that because that would involve a lot of updates to currently published applications. It is currently impossible for me to test this application in a controlled environment (one that mimics the two subnets connected by a T1).



If there is anything that I could check in regard to the framework, please let me know. Perhaps a three second startup is to be expected. In light of that, a 30 second startup at the other end might be exactly right. Any insight into the startup plumbing would be appreciated.



Thanks.

Have you figured out what is taking the time? I.e. have you done any profiling? Once we know the answer to that question, then we could likely offer more focused suggestions.

Sure. I am not in a position to make the investment. So, in light of that, what tips and tricks are there for getting an application to startup quickly. There does not seem to be a ton of DB activity initially. And, this slowdown occurs when all is quiet on the network.

Hi Bill.

Have you considered using the Enterprise Server?

Good morning,



I am targeting the application startup to try to speed things up in our remote location. All databases are in location A. Location B is connected by a dedicated T1 (1.5Mbs) line. I have worked on many data queries to speed up certain windows within the application, now it is time to look at the startup. It takes 3-5 seconds for the application to open in location A. In location B, the app takes 30 seconds or more. What can I do...what can I look at...to increase the speed of the opening main window?



Thanks!

Bill