It's actually an interesting story in side-effects.
Visual Studio has a fixed list of assemblies in their "Add Reference" dialog.
Anything else has to be browsed for.
Developers tended to browse for this location in the Windows directory, where System.Management.Automation.dll (the assembly that runs most of PowerShell lives)
This made an absolute reference to this location.
Since there wasn't going to be a side-by-side install option with PowerShell (as there is with the .NET framework), the best choice available was to allow people to keep referencing the same assembly, both by path and by StrongName, as they did before.
If this story hadn't have stayed this way, all applications written on top of PowerShell V1 would have to be re-released for V2.
与恶龙缠斗过久,自身亦成为恶龙；凝视深渊过久,深渊将回以凝视…
