Ngen process during installation of .net framework 1.1

[Sameeksha]

Hi everyone,

I have observed that the ngen process appears in the list of processes
in
taskmgr while .net framework 1.1 gets installed. This process consumes
0-50%
of cpu and 0-20K of RAM.
I would like to know if this process can be a cause of slowing down
performance of a high speed application. The installer of this
application
examines whether .net framework is installed, if it is not installed it
first
installs .net 1.1 and then continues with its own installation.
It would be great if anyone knows about problems related to ngen during

installation of .net framework 1.1, say, under low memory conditions,
or for
particular OSs, or for particular hardware configuration

 

[Naveen]

Hi,

In .NET Framework 1.1 all ngen work was done synchronously at
install-time since Microsoft did not support asynchronous compilation.
Pre-compiling all the .NET Framework 1.1 assemblies synchronously would
have increased the amount of time taken to install the redist. Thus the
only assemblies included were mscorlib, System, System.Windows.Forms,
System.Design, System.Drawing, System.Drawing.Design, System.Xml and
CustomMarshalers.



In .NET Framework 2.0 Microsoft have the .NET Runtime Optimization
Service which can compile assemblies in the background. As a
consequence, when .NET Framework 2.0 is installed, 8 assemblies are
compiled synchronously while the rest (another 19 including
System.Data, System.Web and System.Web.Services) are compiled at
machine idle-time by the service.