Re: Slow startup of Deployed Application

On Wed, 20 Sep 2006 12:15:15 -0700, "jeff" <jhersey at allnorth dottt com> wrote:


the delay before my project starts... the user sits and waits ... sometimes
10 seconds ... that is the issue.

so, my question / issue is there a way to ...

a. preload the net 2 framework ... to avoid this delay.

b. have a popup window start before the .net 2 framework loads indicating to
the user to wait 5 / 6 seconds while OS loads its NET framework...this is
not likely, 'cause any 'splash window' would require the .net framework to
be loaded.

c. what are other people doing to notify the user to hold on tight ...
'cause we are waiting for the OS to load the .net framework.

d. tell all the users you need to upgrade to 2 gigs of ram ...

e. preload the .net framework during startup / reboot of the computer.

Ideas?

Thanks

Jeff


"Izzy" <israel.richner@xxxxxxxxx> wrote in message
news:1158776902.814824.250950@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
What is the issue?

jeff wrote:
Hi All.

I realize that when my Deployed winforms application starts, Windows
needs
to load the .net 2 framework before control is given to my
application....

Is there anyway to either ...

- preload the .net 2 framework (windows startup or whatever)

- splash a screen ... application loading ... please wait ... type of
message.

I was considering building a 'launcher' program in VB 6 ... a simple
splash
window ...

this launcher would

- open a form ... prgraming is starting please be patient...
- call my application to start ...
- pole a file every few seconds to check to see if my main applicaiton is
open yet ...
- once flag in file set ... shutdown form...


Any thoughts / ideas ...

Thanks
Jeff.



1) I use the builtin Splash Screen funtionality in VB2005. It loads and displays
"before" any other part of the application is initialized. From a cold boot, the
builtin splash (at least in my cases) displays within a second or two. This would
not be the case necessarily using a standard form as a Splash Screen launched from a
SubMain (), for example.

2) Use the main form load event only for getting the main form displayed asap. When
the main form is displayed, the builtin Splash Screen closes and the main form's
Shown Event is fired. Use the Shown Event to do any furher initializations. If
that's a lenghty process, you can display some kind of wait/progress form from the
Shown Event.

Gene
.

Relevant Pages

  • Re: Slow startup of Deployed Application
    ... You could try writting a simple single form applicaton and add the ... this way the delay will only happen when the OS starts. ... I don't think the issue is the .NET framework but probably the JIT ... the same time to load for the client as does the production application we ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Slow startup of Deployed Application
    ... preload the net 2 framework ... ... 'cause we are waiting for the OS to load the .net framework. ... I use the builtin Splash Screen funtionality in VB2005. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Slow startup of Deployed Application
    ... the delay before my project starts... ... preload the net 2 framework ... ... have a popup window start before the .net 2 framework loads indicating to ... 'cause we are waiting for the OS to load the .net framework. ...
    (microsoft.public.dotnet.languages.vb)
  • While teachers madly present swimmings, the jazzs often derive through the unchanged tablets.
    ... Martha gazes the framework for hers and obnoxiously competes. ... specially equivalent, so I load you. ...
    (sci.crypt)
  • Re: User Control Security on .Net 2.0
    ... Right now I have a problem with printing permissions. ... we did not have to create a code group on the clients ... > load the latest installed dotnet framework on the client machine. ...
    (microsoft.public.dotnet.framework.aspnet)
Quantcast