One of the things that I have not had a chance to do is to figure out how to create my own libraries in Windows 7. I have spent a bit of time browsing MSDN, and did find an article<\/a> that discussed working with the API. Unfortunately, there are no .NET Framework classes to do this. While I can use the Add-Type<\/strong> cmdlet to work with native code, the results are not very pretty. (See these Hey, Scripting Guy! Blog posts for some excellent examples<\/a> of this type of scripting.)<\/p>\n Anyway, luckily I ran across the Windows7Library for PowerShell project on Codeplex<\/a>. (Make sure you get the updated version of the module<\/a>. Ragnar updated the module to version .5 based upon some feedback I had given him while I was writing this article.) This project, written by Ragnar Harper<\/a>, is discussed on Ragnar’s blog<\/a>. One limitation of my Copy-Modules.ps1 script, is that it only looks for modules and for manifest files. It does not look for *.xml, *.dll, or *.exe files. I did this on purpose because I wanted an easy installer for “script modules” not for more complex types of module projects. I figured that if I created a module project that relied on external *.dll’s or *.exe files, I would create a Windows Installer project to do that. As seen in the following figure, Ragnar’s Windows7Library module uses several different file types; this is because he relied upon a couple of other projects to simplify the creation of his module.<\/p>\n <\/p>\n This does not mean that I cannot use my Copy-Modules.ps1 script to install the Windows7Library module. But it does mean that I will need to copy the remaining files into the folder once I run the script.<\/p>\n AfterI have the two modules installed, I can write a quick script to pin my applications to the taskbar and to create my custom libraries.<\/p>\n There are four default libraries created when Windows 7 is installed. These are stored in the profile. The four default libraries appear in the following figure.<\/p>\n My complete SetLibraryAndTaskBar.ps1 script is not too complicated. It includes two Import-Module<\/strong> statements, and then calls the Set-PinnedApplication<\/strong> function to add Windows PowerShell and the Windows PowerShell ISE to my taskbar. It then creates a library, and adds a folder to the library. In reality, I would not need to really create this “script” except that these are things I generally do to all of my workstations, and it saves a bit of typing.<\/p>\n Import-Module PinnedApplicationsModule<\/p>\n Import-Module Windows7Library<\/p>\n <\/p>\n Set-PinnedApplication -Action PinToTaskbar -FilePath $PSHOME\\powershell.exe<\/p>\n Set-PinnedApplication -Action PinToTaskbar -FilePath $PSHOME\\powershell_ise.exe<\/p>\n Add-Library -LibraryName “ScriptingGuys_2011”<\/p>\n Add-LibraryFolder -libraryName “ScriptingGuys_2011” -folderPath E:\\data\\ScriptingGuys\\2011<\/p>\n <\/p>\n I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n Ed Wilson, Microsoft Scripting Guy<\/b><\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Summary: Learn how to combine Windows PowerShell modules to save time and reduce scripting overhead. Microsoft Scripting Guy Ed Wilson here. One of the cool things about Windows PowerShell modules is that they are easy to share. In addition, because the code is packaged as a module, one automatically knows what to do with […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[16,47,52,3,4,45],"class_list":["post-13491","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-desktop-management","tag-general-management-tasks","tag-modules","tag-scripting-guy","tag-scripting-techniques","tag-windows-powershell"],"acf":[],"blog_post_summary":" Summary: Learn how to combine Windows PowerShell modules to save time and reduce scripting overhead. Microsoft Scripting Guy Ed Wilson here. One of the cool things about Windows PowerShell modules is that they are easy to share. In addition, because the code is packaged as a module, one automatically knows what to do with […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/13491","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=13491"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/13491\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=13491"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=13491"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=13491"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/6765.HSG-06-28-11-01.png\" "\\"Image")
<\/a><\/p>\n![\"Image](\"https:\/\/devblogs.microsoft.com\/wp-content\/uploads\/sites\/29\/2019\/02\/2133.HSG-06-28-11-02.png\" "\\"Image")
<\/a><\/p>\n