An example of what's possible with ps1xml type deffinitions, and how you can improve on the default Add-Type, and use ps1xml the way you use extension methods in C#
By reflecting on a snap-in assembly, Cmdlet Help Editor creates customized barebones documentation that includes the cmdlets, parameters, and attributes ... enabling you to create help topics for Windows PowerShell cmdlets in the correct XML format...
A succinct explanation of PowerShell's threat model, defenses, and new security options. Note in particular that Set-ExecutionPolicy now allows you to define a USER ExecutionPolicy which overrides the Machine ExecutionPolicy.
An Out-Grid cmdlet implemented in what may possibly be the most complicated fashion ever ;-) David Barnhill has created a WPF app which you can instantiate from PowerShell by sending output to it... but the cmdlet actually creates a separate application object (a new process) and then communicates with it (using WCF) to send it the grid data.
Some cool tech there, but it seems like he might as well have made Out-WPFGrid into a stand-alone app -- and it seems like that would have been easier?
Like this http://cheaptravelbooker.com
Like this http://cheaptravelbooker.com
like this http://killdo.de.gg
travel,hotel,fun,hotel new,new offer,hotel best,best hotel,hotel travel,seo,backlinks,edu,gov,ads,indexing,bookmark,killgoggle,gogglesuck,goggle bookmark,kill goggle,yahoo,bing,indexing,quality links,linkwell,traffic boster,index best
This is at the top of my list of crazy things ... I'm not 100% sure why you'd want to use a variable instead of a function badly enough to do this, but I guess variables are a lot easier to work into a string. Plus, it's obviously cool.
This is necessary if you want to load .net assemblies (like compiled PowerShell snapins/modules) from a network share! Without setting up your CasPol settings you can neither load a snapin, import a module, or use Assembly.LoadFrom
Group items tagged 
