Implement PowerShell PSProvider *in* PowerShell - powershell

Question

I'm looking to implement a PowerShell Provider in PowerShell.
I keep thinking that if I just define the types, then import them into my session (import-module), I should be able to have them available.
For example, this does not work but its along the path of what I'd like to implement.
I'm obviously missing quite a bit...anyone know if this is possible?
# EnvironmentProvider.ps1
$reference_assemblies = (
"System.Management.Automation, Version=1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
# "System.Configuration.Install, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
)
$source = #"
namespace Providers
{
using System.Management.Automation;
using System.Management.Automation.Provider;
[CmdletProvider("Environments", ProviderCapabilities.None)]
public class EnvironmentProvider : DriveCmdletProvider
{
protected override PSDriveInfo NewDrive(PSDriveInfo drive)
{
return new EnvironmentDriveInfo(drive);
}
protected override object NewDriveDynamicParameters()
{
return base.NewDriveDynamicParameters();
}
}
public class EnvironmentDriveInfo : PSDriveInfo
{
public EnvironmentDriveInfo(PSDriveInfo driveInfo) : base(driveInfo)
{
}
}
}
"#
# -ea silentlycontinue in case its already loaded
#
add-type -referencedassemblies $referenced_assemblies -typedefinition $source -language CSharp -erroraction silentlycontinue
After import-module, I try to create the drive "environments":
new-psdrive -psprovider Environments -name "Environments" -root ""
errors with:
New-PSDrive : Cannot find a provider with the name 'Environments'.
Assuming the provider actually worked, maybe have it return a list of environments: dev, qa, staging, production.
Then I'd like to be able to re-use this through:
c:\adminlib>import-module .\EnvironmentProvider.ps1
c:\adminlib>environments:
environments:>ls
dev
qa
staging
production
environments:> cd production
environments\production> [execute actions against production]
environments\production:> cd dev
environments\dev:> [execute actions against dev, etc]

Answer 1

I would strongly recommend looking at the stuff Oisin wrote, suspect for people like you, who can grab their head around it, that could be very good reference on how-to. Or maybe what to avoid? ;)
You can find it on codeplex: http://psprovider.codeplex.com/

Answer 2

I know it's been some time since you asked the question, but I've been searching for that same answer myself. As it happens, re-reading the Samples in msdn finally got me my answer, and given the frustration quotient I thought I'd share:
The assembly containing the provider needs to be imported using Import-Module (not merely the module containing the add-type declaration). This can be done using two ways:
Option 1:
Use the parameter of Add-Type that builds the runtime assembly as a .dll file and import the file.
Option 2:
Import the runtime assembly from memory. This is how I did that with the standard msdn samples:
[appdomain]::CurrentDomain.GetAssemblies() | Where {$_.ExportedTypes -ne $null} | Where {($_.ExportedTypes | Select -ExpandProperty "Name") -contains "AccessDBProvider"} | Import-Module
Replace the Provider name in the where filter with your own.
Cheers,
Fred