SURVEY: http://spreadsheets.google.com/viewform?key=pgTpVBomNgDwUA9uQNRKAbw&hl=en

Taking an app from an internal application to a shrink-wrap ready for
the masses state is a lot of work, and updating/supporting/marketting
a product even more so. So after the huge sucess of PowerShell Plus
which is now safe in Idera's hands we need your help to decide what we
are going to release next. We plan to release some free projects, even
some opensource apps, but will likely look at productizing a project
so we can continue to feed our families. Please take the time to take
our survey
 

So I've loved portable apps from time memorial and have valued making my own apps as portable as possible - XCOPY friendly.

Given the context on the last few posts. I've made a simple helper method in C# that can take a simple powershell hashtable and create a PSCustomObject based on it. Here is an example of how you can call it.

Based on the performance testing and work being done by myself , mow , Brandon Shell and others the question has come up what is the quickest way to generate a PSCustomObject, whether in script , on in C#, and how do you even do it in C#?

Some typical ways of doing in PowerShell have been either something like the following trick:

I've spend a lot of time in the past looking at the performance of PowerShell but have never gotten around to blogging about it. However it has become quite a hot button among MVPs and others in recent days and we've been busy testing and comparing the speeds different techniques in PowerShell in both V1 and V2.

In V1 there seems to be extreme slowdowns when invoking cmdlet, functions, any type of scriptblock and when using the pipeline. If you...

One thing that has bothered me about true cmdlets in contrast scripts is that they lived in SnapIns and couldn't be deployed with xcopy as scripts can because SnapIns required Registration/Installation. I build my own way to deal with this need some time ago, and thought that I'd start a blog series covering it. I call them Snapininis or SnapIn-Lites. A good thing is you can achieve the same end result in PowerShell V2 with modules - but that is V2 and a while away from being released, and then even further away from being fully deployed.

Many people recently have asked how to determine programatically what version of PowerShell their script is running in. Well in version two there is a $psversiontable variable, but this sadly isn't in V1. All is not lost though, as you can write a simple function to return a version object for v1. Below is a quick function that I wrote that I have been using for the last year or so. 

PowerShell Analyzer 1.0 is finally released. For a week or two we consider this a "soft" launch, just in case there is some major issue that eluded our testing, but we are pretty confident its stable. Additionally, if you have already used your 45 Day trial, we have EXTENDED it another 45 days. PowerShell Plus is now available with a 45 Day trial as well, and Additionally its available fully free for Non Commercial use as well.

Finally my main blog is back in Business. I had gotten discouraged with my previous web host and abundant comment spam, and just plain being busy. But now with the help of an updated WordPress, new Host and Windows Live Writer all should be good.