Hopefully you’ve read the previous entries on how to create MshSnapins to include your own cmdlets\/providers without having to create an entire separate executable (custom shell).<\/p>\n
If you didn’t or if you did and you don’t feel like writing the extra MshSnapin class to be used by InstallUtil.exe, you’re in luck. I wrote a little ditty(script) about taking any arbitrary assembly and setting the appropriate values in the Registry for use.And in using this little handy script, you’ll be able to look at registry settings to see what needs to get added to add your mshsnapin. <\/p>\n
This script takes 2 parameters. first parameter is the assembly containing your cmdlets and\/or providers. The 2nd optional parameter is the “name” of the mshsnapin. If you don’t supply a name, then the name of the mshsnapin will be the assemblyfile (1st parameter)
Lets assume that you created an assembly “myawesomecmdlets.dll” which contain the most awe-inspiring cmdlets possibly imaginable.<\/p>\n
MSH> register-mshsnapin myawesomecmdlets.dll mysnapin
MSH> add-mshsnapin mysnapin # add your snapin to the current session
MSH> create-somethingwonderful # run one of your cmdlets \ud83d\ude42<\/p>\n
If you run regedit, you’ll then be able to see the entries that get added for your mshsnapin “mysnapin”:
HKLM\\Software\\Microsoft\\MSH\\1\\MshSnapins\\mysnapin has values for
ApplicationBase – directoryname where your assembly is located. This is also the dir where help files, types & format files are looked for
AssemblyName – Full strong name of assembly
Description – text describing your mshsnapin
ModuleName – full path of assembly file
MshVersion – “1.0”
Version – “1.0”<\/p>\n
<\/p>\n
So use the script at end of this post to quickly take any assembly and configure it be added as an mshsnapin. <\/p>\n
Hope this helps!<\/p>\n
Scott<\/p>\n
<\/p>\n
# Beginning of script ‘register-mshsnapin’<\/p>\n
param ([string] $assemblyfile, [string] $MshSnapinName = $assemblyFile)<\/p>\n
# Make sure we can load assembly
################################
$assemblyInfo = [System.Reflection.Assembly]::LoadFrom($assemblyFile)
if($assemblyInfo -eq $null)
{
“unable to load assembly $assemblyFile!”
exit -1
}<\/p>\n
# Based on MshSnapinName, lets create the Reg Key values
#################################################
$keyname = “HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Msh\\1\\MshSnapins\\” + $MshSnapinName<\/p>\n
[Microsoft.Win32.Registry]::SetValue($keyname, “ApplicationBase”,
[System.IO.Path]::GetDirectoryName($assemblyInfo.Location) )
[Microsoft.Win32.Registry]::SetValue($keyname, “AssemblyName”,$assemblyInfo.FullName)<\/p>\n
[Microsoft.Win32.Registry]::SetValue($keyname,”Description”,”A Test MshSnapin”)
[Microsoft.Win32.Registry]::SetValue($keyname,”ModuleName”,$assemblyInfo.Location)
[Microsoft.Win32.Registry]::SetValue($keyname,”Version”,”1.0″)
[Microsoft.Win32.Registry]::SetValue($keyname,”MshVersion”,”1.0″)<\/p>\n
# End of script<\/p>\n
[Edit: Monad has now been renamed to Windows PowerShell. This script or discussion may require slight adjustments before it applies directly to newer builds.<\/i>]<\/p>\n","protected":false},"excerpt":{"rendered":"
Hopefully you’ve read the previous entries on how to create MshSnapins to include your own cmdlets\/providers without having to create an entire separate executable (custom shell). If you didn’t or if you did and you don’t feel like writing the extra MshSnapin class to be used by InstallUtil.exe, you’re in luck. I wrote a little […]<\/p>\n","protected":false},"author":600,"featured_media":13641,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-10521","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-powershell"],"acf":[],"blog_post_summary":"
Hopefully you’ve read the previous entries on how to create MshSnapins to include your own cmdlets\/providers without having to create an entire separate executable (custom shell). If you didn’t or if you did and you don’t feel like writing the extra MshSnapin class to be used by InstallUtil.exe, you’re in luck. I wrote a little […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/10521","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/users\/600"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/comments?post=10521"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/10521\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media\/13641"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media?parent=10521"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/categories?post=10521"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/tags?post=10521"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}