I'm not sure if this is possible, or if perhaps I'm not thinking .Net enough for the idea, but I'm coming from a perspective of process creation and assembly loading, that appears to be much slower than I would desire.
When creating a Win32 API application (non-.Net) in say Delphi or C++, and using Win32 DLLs I can statically or dynamically link the dlls and either way it doesn't really have much apparent issue on the loading of the application.
I Currently have several library Assemblies which are "Engines" as they were that are used by other "control" assemblies that are used by the application. So IN all effect there are 10 total assemblies to this application.
Now, when debugging, I've noticed the assemblies being loaded in sequence down at the bottom status bar of VS. and sometimes given the nature of a rather full desktop of applications I don't always see the Splash screen. However when I just run
the application, not through VS for debugging, but i've installed it on another computer and just run the short cut to the exe, and even on average modern systems it can sometimes take 15 or 20 seconds (maybe more) before the splash screen even displays.
On slower systems this can even be extended to a full minute. I'm wondering if my design of having t
View Complete Post