![]() ![]() ![]() Even if access to PSGallery is possible, you may not want-or even be allowed-to publish your corporate modules to a public space. ![]() However, this is not really an option if you are creating PowerShell applications for closed networks that are air-gaped or behind proxy servers restricting internet access. It is relatively simple to include a script that installs required modules from PSGallery and to call this script either from your application on the first run or from a custom action in your installer. This is all well and good if you share your modules with the public on PowerShell Gallery or any other public repository. SAPIEN PowerShell Module Manager is an excellent tool for this purpose because it makes the process more visual and streamlines module management. The prescribed way to deploy modules calls for using a module repository, from which you will retrieve and install any PowerShell module you need. There is, however, the hurdle of module deployment. Modules make your development tasks more manageable in many ways, so you should employ them whenever possible. Within a larger project, they enable you to distribute defined tasks to individuals or groups of developers who can implement the already defined interfaces without impairing other tasks. They allow you to share code with defined interfaces amongst your projects, applications, organization, and peers. Modules are a substantial part of the PowerShell infrastructure in many ways, they serve the same purpose as DLLs or assemblies do for developers using traditional compiled languages. As all the information is recent and there have been no changes, you can skip this post if you are familiar with the original. This part of the MSI Builder Step-by-Step series is a re-post of a previous article on adding PowerShell modules to your Installer. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |