>I've created a batch file to do most of these steps, all I need to do is
>find some way of getting the location of ngen (the location of the .net
>framework + version directory). Is there a registry key or some other easy
>way of finding the location of the ngen executable?

"Stephen" <s@m.com> wrote in message
news:#v4lTz#4DHA.2692@TK2MSFTNGP09.phx.gbl...
> Thanks for the reply!
>
> We did investigate using the deployment solutions provided by visual
studio,
> but found their capability very limited and their use restrictive. We've
got
> our own installation software (ZeroG InstallAnywhere) and I was thinking
of
> adding a post install step of running my batch file to ngen the
assemblies.
> The only problem is I can't find an easy way of locating the current .net
> framework directory containing ngen.exe. Can anyone help?
>
>

"Stephen" <s@m.com> wrote in message
news:u2lUA5#4DHA.1852@TK2MSFTNGP10.phx.gbl...
> We've also had a look at ngen'ing some of the System assemblies, as it
looks
> as though only a few are ngen'd during the install of the framework. Is
this
> recommended? The reason i ask is i am wondering why they are not all
ngen'd
> during the install of the framework.
>
> Also, if I do ngen the system assemblies, should I delete these native
> images during the uninstall? Only there doesn't seem to be any way of
> telling how many people have ngen'd each assembly and so I wouldn't want
to
> remove this image if some other application also wanted it ngen'd.
>
>

Conrad Zhang wrote:
> Ngen is not a good story in v1/v1.1. It is probably not worth that
> much to ngen your assemblies.
> It is a totally different story in whidbey though.

wrote in message news:umMjsUBDEHA.3408@tk2msftngp13.phx.gbl...
> Conrad Zhang wrote:
> > Ngen is not a good story in v1/v1.1. It is probably not worth that
> > much to ngen your assemblies.
> > It is a totally different story in whidbey though.
>
> Could you elaborate on this? What makes it worth considering with Whidbey?
>
> - Petri
>
>