Posted
by
Bink on
on July 23 2008, 8:32 AM
with no comments
Jeffrey Snover [MSFT]: In V1, we had a problem which caused our assemblies to not get ngen'ed during installation. If you don't know what "ngen" is, don't worry - you don't need to. All you need to know is that we didn't do the step that makes things go fast on your machine. The instructions for how to fix this:
Set-Alias ngen @(
dir (join-path ${env:\windir} "Microsoft.NET\Framework") ngen.exe -recurse |
sort -descending lastwritetime
)[0].fullName
[appdomain]::currentdomain.getassemblies() | %{ngen $_.location}
See discussion HERE.
You should stop what you are doing and go run that script. If you've already done this in the past, it will be harmless but if you haven't, you'll be amazed at the improvement in startup times. Please tell all your friends to do this as well. A lot of people don't know about it and have a bad opinion about PowerShell startup times. After people run it, the typical reaction is, "WOW!".
Full Story At Source
6894 Views