Update (3 February 2014): PowerShell Type Provider merged into FSharp.Management.
I am happy to share with you the first version of PowerShell Type Provider. Last days were really hot, but finally the initial version was published.
Lots of different emotions visited me during the work =). Actually, Type Provider API is much harder than I thought. After reading books, it looked easier than it turned out in reality. Type Providers runtime is crafty.
To start you need to download source code and build it – no NuGet package for now. I want to get a portion of feedback and after that publish to the NuGet more consistent version.
Also you need to know that it is developed using PowerShell 3.0 runtime and .NET 4.0/4.5. This means that you can use only PowerShell 3.0 snap-ins.
#r @"C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\System.Management.Automation\v4.0_184.108.40.206__31bf3856ad364e35\System.Management.Automation.dll" #r @"C:\WINDOWS\Microsoft.NET\assembly\GAC_MSIL\Microsoft.PowerShell.Commands.Utility\v4.0_220.127.116.11__31bf3856ad364e35\Microsoft.Powershell.Commands.Utility.dll" #r @"d:\GitHub\PowerShellTypeProvider\PowerShellTypeProvider\bin\Debug\PowerShellTypeProvider.dll" type PS = FSharp.PowerShell.PowerShellTypeProvider<PSSnapIns="WDeploySnapin3.0">
As you see in the sample, PowerShellTypeProvider has a single mandatory static parameter PSSnapIns that contains semicolon-separated list of snap-ins that you want to import into PowerShell. If you want to use only default ones, leave the string empty.
You can find list of snap-ins registered on your machine using Get-PSSnapin method.
Enjoy it. I will be happy to hear feadback (as well as comments about type provider source code from TP gurus).