I am hoping someone can explain to me what is going on behind the scenes
between these two scenarios that would cause such a difference.

We have been piecemeal upgrading a large application from VB6 to .NET. Over
time we've upgraded each of the (100 or so) modal screens and placed them
into .NET libraries. The Vb6 exe interops the screens.

We're now to the point of upgrading the main MDI screen and the few MDI
Child screens. The startup logic is nearly identical to the VB6 version's
startup. The difference is when I startup the VB6 executable (containing the
MDI main and 8 or so child screens) it starts up nearly instantaneously.
However, when I start the .NET version (.NET version of the MDI main and MDI
childs) it takes 4-5 seconds.

Why is there such a difference in time? FusLog Viewer says each exe is
loading about 40 libraries, but the VB6 version is so much faster. What is
the .NET exe doing differently to cause this difference?

Thanks

Okay, I figured out the difference. The way our system is designed our
libraries are deployed into a specific local folder on the user's machine.
(We don't use the GAC for our libraries.) For all of our other .NET
executables we've created config files that contain assembly binding
information for each of our libraries in this folder. As soon as I created a
config file for my application the startup time was comparable to that of my
VB6 app. Basically the probing for these libraries was killing our startup
time. Now it is nearly instantaneous.

Thanks


"JJ" wrote: