Automating the world one-liner at a time…
I talked about this before but a number of people have missed it so here it is under a better title.
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 are 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!".
Jeffrey Snover [MSFT]Windows Management Partner ArchitectVisit the Windows PowerShell Team blog at: http://blogs.msdn.com/PowerShellVisit the Windows PowerShell ScriptCenter at: http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx
I have powershell v2 ctp3 installed on a windows 2k8 x64 machine. If I run a certain powershell script as Administrator...the execution time is less then 10 seconds...if I run the same script as LocalSystem ..the execution time is 30 minutes, I've run "ngen"..but there's not progress on it. Which can be the problem?
P.S. I run powershell with -nologo and -noprofile
Is there a way to do this without using Internet Explorer? It seems odd that this should be controlled by an IE option setting