PackageManagement module path does not meet PowerShell standards

[lfshr]

Powershell standards dictates that the root folder of a module should have the exact same name as the filename of the psd1 file. Currently the root folder of packagemanagement is 'PackageManagement' and the filename is 'AzureAutomationTools.PackageManagement' Either the psd1 file or the path should change it's name.

[stvnrs]

You are confusing the source setup (modeled on official Microsoft projects) and the deployment of the module - the build creates a folder with the same name as the module so that it deployed in line with powershell convention

On Wed, Apr 26, 2017 at 9:45 AM, Liam notifications@github.com wrote:

Powershell standards dictates that the root folder of a module should have the exact same name as the filename of the module. Currently the root folder of packagemanagement is 'PackageManagement' and the filename is 'AzureAutomationTools.PackageManagement' Either the psd1 file or the path should change it's name.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/big-data-for-humans/azure-automation-tools/issues/11, or mute the thread https://github.com/notifications/unsubscribe-auth/AAd6h4G7Va2AMPXTuffCw_SShMdrQKV0ks5rzwQqgaJpZM4NIi8D .

[lfshr]

My mistake 😞