This project is read-only.

Create .psd1 manifests for each Module (.psm1)


PowerShell module authoring best practice suggests each .psm1 PowerShell Module script file should have an accompanying .psd1 manifest file (multiple, related psm1 files can be packaged in a common manifest).

At the time of creating this issue, the only .psd1 file in the GEM 3.0 release is from the included (dependency) module PSRemoteRegistry


bcdady wrote Aug 12, 2015 at 6:52 AM

Creating new module manifest files can be addressed fairly easily, thanks to the New-ModuleManifest cmdlet.

misabel_gem wrote Aug 12, 2015 at 1:22 PM

Here's what I'm thinking. We could create a module manifest per larger section i.e. one for BuildDeployment, one for Hyper-V, etc.

We might need to write an script to update the module manifest automatically when we commit code to increment the version. Not exactly sure how to go about that one.