PreCaching Dot Net Framework Load

  • Thread starter Thread starter Jason Garland \(Secure Access Pty Ltd\)
  • Start date Start date
J

Jason Garland \(Secure Access Pty Ltd\)

Is there a way to preload the MS compondents of the Dot Net Framework V1.1
Before user login ?

We have a few programs that are created under VB Dot Net that run at user
login. On the older machines it takes quite a while for the Framework to
load (all code native Dot Net, no 3rd Party) with the rest of the system,
and makes it appear to hang.

Is there a service or a way of preloading the Framework to make it appear
faster ?

With Thanks

Jason
 
Jason said:
Is there a way to preload the MS compondents of the Dot Net Framework V1.1
Before user login ?

We have a few programs that are created under VB Dot Net that run at user
login. On the older machines it takes quite a while for the Framework to
load (all code native Dot Net, no 3rd Party) with the rest of the system,
and makes it appear to hang.

Is there a service or a way of preloading the Framework to make it appear
faster ?

With Thanks

Jason
Click to expand...

Hi Jason -

Have a look at Ngen.exe (Native Image Generator). From MSDN:
The Native Image Generator creates a native image from a managed assembly
and installs it into the native image cache on the local computer. The
native image cache is a reserved area of the global assembly cache. Once you
create a native image for an assembly, the runtime automatically uses that
native image each time it runs the assembly. You do not have to perform any
additional procedures to cause the runtime to use a native image. Running
Ngen.exe on an assembly allows the assembly to load and execute faster,
because it restores code and data structures from the native image cache
rather than generating them dynamically.

More info here: http://tinyurl.com/2or38
 
Jason Garland (Secure Access Pty Ltd) wrote:

Hi Jason -

Have a look at Ngen.exe (Native Image Generator). From MSDN:
The Native Image Generator creates a native image from a managed
assembly and installs it into the native image cache on the local
computer. The native image cache is a reserved area of the global
assembly cache. Once you create a native image for an assembly, the
runtime automatically uses that native image each time it runs the
assembly. You do not have to perform any additional procedures to cause
the runtime to use a native image. Running Ngen.exe on an assembly
allows the assembly to load and execute faster, because it restores code
and data structures from the native image cache rather than generating
them dynamically.

More info here: http://tinyurl.com/2or38
Click to expand...

In most cases, results of Ngen's work are unrunnable (critical error at
startup, etc.), I'm afraid you can only write your own preloader, but I
haven't seen anybody went so far.... :)
 
Maniaque |CIA| said:
In most cases, results of Ngen's work are unrunnable (critical error at
startup, etc.), I'm afraid you can only write your own preloader, but I
haven't seen anybody went so far.... :)
Click to expand...

Could you cite your source please?
 
Back
Top