A module is a self-contained set of code that once loaded can be called/used. I use modules to keep similar SharePoint functionality that I want to reuse. There are 2 basic types of modules:
1.> Script modules, this is the easiest and most common type of module. Take you .ps1 file and rename it .psm1
2.> Code/Binary modules are compiled dll's that can be loaded and used. You can also create a snap-in with binary code.
3> Snap-ins, are compiled code dll's. The snap-ins can be loaded and used within your PS console.
Snap-ins are not code modules. I prefer to keep my files as ps1 files and load them in a controlling .ps1 files before using them or if I need to write code that uses the CSOM I would use C# and create a snap-in that I can port and consume.
More Info:
http://zimmergren.net/technical/sp-2010-how-to-create-a-powershell-snapin-part-1
http://www.wrox.com/WileyCDA/Section/Extending-Windows-Powershell-with-Snap-ins.id-320555.html
1.> Script modules, this is the easiest and most common type of module. Take you .ps1 file and rename it .psm1
2.> Code/Binary modules are compiled dll's that can be loaded and used. You can also create a snap-in with binary code.
3> Snap-ins, are compiled code dll's. The snap-ins can be loaded and used within your PS console.
Snap-ins are not code modules. I prefer to keep my files as ps1 files and load them in a controlling .ps1 files before using them or if I need to write code that uses the CSOM I would use C# and create a snap-in that I can port and consume.
More Info:
http://zimmergren.net/technical/sp-2010-how-to-create-a-powershell-snapin-part-1
http://www.wrox.com/WileyCDA/Section/Extending-Windows-Powershell-with-Snap-ins.id-320555.html
0 comments:
Post a Comment