ModuleBuilder VS powershell-poc

I'm using the ModuleBuilder module to perform the build. This follows the "Public", and "Private" folder conventions, etc... It builds the module into one single `.psm1`, from all the files in the public and private folders. Any function files in the public folder are automatically added to the exported module functions in the module's `.psd1` manifest.

I recommend using this module. You organize your module to have a source folder with private and public folders containing your private and public functions in individual files. You can then invoke Build-Module and the module will put it all together into module. I recommend reading their readme for more information on how to set it up. https://github.com/PoshCode/ModuleBuilder

The closest to that is using something like ModuleBuilder and building a single psm1 as a build step. That's the closest to a supported way to do that.

I've always just used my own script for this so I can't tell you more than what you yourself can read here: https://github.com/PoshCode/ModuleBuilder

Link: https://github.com/PoshCode/ModuleBuilder

My team uses https://github.com/PoshCode/ModuleBuilder to do module building, but it's much along the same idea as what you're doing.

@{ RootModule = 'PSHello.psm1' ModuleVersion = '{0}' GUID = 'debdc63d-af3f-4e54-8136-489156fd6819' Author = 'andyfeller' CompanyName = 'Unknown' Copyright = '(c) andyfeller. All rights reserved.' Description = 'Basic Powershell Hello world' PowerShellVersion = '3.0' FunctionsToExport = @({1}) CmdletsToExport = @() VariablesToExport = '*' AliasesToExport = @() PrivateData = @{ PSData = @{ ProjectUri = 'https://github.com/andyfeller/powershell-poc' ReleaseNotes = @' {2} '@ } } }