Last months my work with SharePoint 2007, I felt a strong inclination to use PowerShell 2.0.
I envied a happy people who were already with SharePoint 2010 and could enjoy SharePoint 2010 Administration via SharePoint.ps1
PowerShell and SharePoint: What, Why and How
Simple concept: How to use SharePoint cmdlets in PowerShell ISE
I also wanted to have such beautiful commands that have been shipped by SharePoint.ps1 for SharePoint 2010:
Get-SPFarm,
Get-SPWeb,
Get-SPWebApplication
So, my problem was that we don't have SharePoint.ps1 for SharePoint 2007.
To easy up my desire, I have created my functions:
Get-SPFarmV3,
Get-SPWebV3,
Get-SPWebApplicationV3.
And some additional:
Get-SitesWithMissingTemplate, Get-SSProvider, Get-SPVersionV3.
All above I have packed in one SPv3Adapter.mdl module.
Windows PowerShell Module Concepts
Module Installation Best Practices:
Do not install modules for Windows PowerShell in the system location at %Windir%\System32\WindowsPowerShell\v1.0\Modules. Only modules included with Windows are installed to the system location.
http://msdn.microsoft.com/en-us/library/dd878350(v=vs.85).aspx
Module installation
http://msdn.microsoft.com/en-us/library/dd878350(v=vs.85).aspx
And some additional PowerShell files:
Helper functions: Start-CustomTranscript, Get-CustomAPPLog,Get-SolutionDeployed
I have used a lot Get-SolutionDeployed during upgrade SP2007 to SP2010:
The module Helper.mdl has dependency on SPv3Adapter.mdl
One of the favorable option for me is to use manifest (you are welcome to use attached customModulesLoader.psm1 and Manifest.mdl) to ship the PS modules.
No comments:
Post a Comment