Well, I’m honestly not sure what I did differently than anyone else. It’s a pretty straight-forward 32bit assembly project, with my cut-and paste version of a PSSnapin module. Anyone who wants to, is, of course, free to work from my GPL project template

And amazingly, you managed to do something that the big boys (err… other big boys) can’t seem to do – you provided one snapin that works in both 32-bit and 64-bit PowerShell. I’m not sure if you intended to do that or not, but explaining it would sure make a great blog post because there are a lot of folks out there who need some help.

You Rock!
-Chris

Basically, it just runs InstallUtil.exe and it’s really for my purposes in development, because it copies the dll before registering it, so I can recompile even if the dll is loaded in a host.

Assuming the install worked correctly, neither of the commands you ran is the right one to find it. You need to check for registered snapins, because the Install.ps1 script doesn’t Add-PSSnapin unless you pass it the -Add parameter.

The full process is like this, and if you’re on Vista, you have to run install.ps1 in an elevated console. I’ve added this to the main post, but basically, you need to do something like this:

I’ve pasted the results of the install here and the contents of the _installed.InstallLog file follows.

PS C:\toolbox\Scripts\dlls> .\install-poshnet.ps1 .\poshnet.dll
Microsoft® .NET Framework Installation utility Version 2.0.50727.1434
Copyright© Microsoft Corporation. All rights reserved.

The uninstall is beginning.
See the contents of the log file for the C:\toolbox\Scripts\dlls\_installed.dll assembly’s progress.
The file is located at C:\toolbox\Scripts\dlls\_installed.InstallLog.
Uninstalling assembly ‘C:\toolbox\Scripts\dlls\_installed.dll’.
Affected parameters are:
logtoconsole =
assemblypath = C:\toolbox\Scripts\dlls\_installed.dll
showcallstack =
logfile = C:\toolbox\Scripts\dlls\_installed.InstallLog

The uninstall has completed.
Microsoft® .NET Framework Installation utility Version 2.0.50727.1434
Copyright© Microsoft Corporation. All rights reserved.

Running a transacted installation.

Beginning the Install phase of the installation.
See the contents of the log file for the C:\toolbox\Scripts\dlls\_installed.dll assembly’s progress.
The file is located at C:\toolbox\Scripts\dlls\_installed.InstallLog.
Installing assembly ‘C:\toolbox\Scripts\dlls\_installed.dll’.
Affected parameters are:
logtoconsole =
assemblypath = C:\toolbox\Scripts\dlls\_installed.dll
showcallstack =
logfile = C:\toolbox\Scripts\dlls\_installed.InstallLog

The Install phase completed successfully, and the Commit phase is beginning.
See the contents of the log file for the C:\toolbox\Scripts\dlls\_installed.dll assembly’s progress.
The file is located at C:\toolbox\Scripts\dlls\_installed.InstallLog.
Committing assembly ‘C:\toolbox\Scripts\dlls\_installed.dll’.
Affected parameters are:
logtoconsole =
assemblypath = C:\toolbox\Scripts\dlls\_installed.dll
showcallstack =
logfile = C:\toolbox\Scripts\dlls\_installed.InstallLog

The Commit phase completed successfully.

The transacted install has completed.
PS C:\toolbox\Scripts\dlls> Get-PSSnapin

Name : Microsoft.PowerShell.Core
PSVersion : 1.0
Description : This Windows PowerShell snap-in contains Windows PowerShell management cmdlets used to manage components of Windows
PowerShell.

Name : Microsoft.PowerShell.Host
PSVersion : 1.0
Description : This Windows PowerShell snap-in contains cmdlets used by the Windows PowerShell host.

Name : Microsoft.PowerShell.Management
PSVersion : 1.0
Description : This Windows PowerShell snap-in contains management cmdlets used to manage Windows components.

Name : Microsoft.PowerShell.Security
PSVersion : 1.0
Description : This Windows PowerShell snap-in contains cmdlets to manage Windows PowerShell security.

Name : Microsoft.PowerShell.Utility
PSVersion : 1.0
Description : This Windows PowerShell snap-in contains utility Cmdlets used to manipulate data.

PS C:\toolbox\Scripts\dlls> gcm dns -commandType cmdlet

Nothing Returned

trimmed by Jaykul

@Lance Robinson Yeah, “hobbyist” licenses remind me a bit of the whole “first hit’s free” marketing plan ... but I didn’t even think theirs might support looking up different types at once, good job.

I should check theirs out to see how they format their output. This class from CodePlex is dying for a decent ps1xml format file with some scripting to unwrap things.

i’m sure ‘somebody’ is very happy that you did this!

- somebody

NetCmdlets has a free hobbyist license listed on its sales page too.