Windows PowerShell Blog

I noticed that when this ran that it was unable to compile assemblies that were loaded by PSCX (PowerShell Community Extensions).  How would you modify this script to handle assemblies that belong to other snap-ins?

This script has an oversight and does not locate ngen correctly. It does not work properly since I have a _folder_ called "ngen.exe" located here: C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files\Bind Logs\ngen.exe\

This is a great bit of script.  I've shared this out with several people on my team, and it's resolved all of the "PowerShell is slow to start" comments.

Can you say anything about whether this will still be useful/needed on PowerShell v2?  I understand wanting the installation to be responsive, but I'd rather wait an extra minute or two during the installation if it means that PowerShell starts more quickly the first time.

WOW - no real numbers but significant reduction in startup time

OMG!

Slow startup times were actually my (only) ONE major complaint about PowerShell, though I assumed there was nothing you could do about it so I hadn't complained about it.

WAY COOL! THANKS!

Don't forget that on x64 systems, you need to use "Microsoft.NET\Framework64" instead.

Great info (as always)!

As I'm not a .NET-guy, where can I find some backgroud info on GAC, ...

I made a couple of tweeks to add detection of x86 and AMD64:

Set-Alias ngen @(

$ngen_path = Join-Path ${env:\windir} "Microsoft.NET\Framework"

if(${env:PROCESSOR_ARCHITECTURE} -eq "AMD64"){

$ngen_path = Join-Path ${env:\windir} "Microsoft.NET\Framework64"

}

dir $ngen_path ngen.exe -recurse | where {$_.length -gt 0} | sort -descending lastwritetime

)[0].fullName

[appdomain]::currentdomain.getassemblies() | %{ngen /nologo $_.location}

Yes it does speed up the exchange managment shell.  it is still a little slow, but a major improvement.

Jeffrey Snover of Microsoft, PowerShell dude extraordinaire, recently reminded us of a way to Speed Up

Am I correct in assuming that this script, in order to retain its benefits, would need to be re-run after any update or patch to Exchange or the .NET Framework?

Error for System.Data.dll on x64 PowerShell.

For some reason ngen always fails to comile a native image of System.Data.dll on PowerShell x64. Here's the relevant message.

Microsoft (R) CLR Native Image Generator - Version 2.0.50727.3053

Copyright (c) Microsoft Corporation.  All rights reserved.

Installing assembly C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll

Failed to find dependencies of image C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll be

cause this image or one of its dependencies is not a valid Win32 application.

   Compiling assembly C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll ...

Error compiling C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll: An attempt was made to

load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)

Uninstalling assembly C:\Windows\assembly\GAC_64\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll because of an err

or during compilation.

@Brian - Making Microsoft.NET\Framework into Microsoft.NET\Framework64 as DM said.

I tried this Script and it does not do any thing to speed the start-up of poweshell console for Exchange 2007 installed on a Windows Server 2008!!! Any idea on how to fix this??

Thanks.

I ran the script in V2, still takes on the order of 15-20 seconds to get to PS when issuing powershell.exe from cmd.  I'm worried about the scripting speed.  I need to poll 300 machines repeatedly for very specific info.  It's starting to sound like I need to use a binary or maybe wscript

Even after running this script my powershell takes > 20 seconds to start (either from shortcut or by typing powershell from cmd).  Starting it from within powershell itself is fast.

Here is the output from the commands Josh suggested:

PS C:\Documents and Settings\jdease>  1..10 | %{Measure-Command {powershell exit}}|ft totalseconds

                                                                                                          TotalSeconds

------------

0.6983097

0.6771509

0.7174827

0.6861359

0.6862929

0.7018789

0.6871349

0.6774461

0.6860443

0.6863205

PS C:\Documents and Settings\jdease> gwmi win32_processor |fl name,NumberOfCores,MaxClockSpeed,L2CacheSize

name          : Intel(R) Core(TM)2 CPU          6400  @ 2.13GHz

NumberOfCores : 2

MaxClockSpeed : 2128

L2CacheSize   : 2048

PS C:\Documents and Settings\jdease> gwmi Win32_PhysicalMemory |ft tag,speed,{$_.capacity/1mb} -auto

tag               speed $_.capacity/1mb

---               ----- ---------------

Physical Memory 0   667            1024

Physical Memory 2   667            1024