CI/CD

[omiossec]

I have few remarks regarding how the module is tested and build

I did not see any build or CD information in the module. There is no badge, no build process.
If you look at the final product, the one you get from the PowerShell Gallery, include the same folder as the GitHub repos. This include the source, the .git, the .vscode and the images folders, readme.md and the test files.

My suggestions:

• Create a build process (Azure DevOps ? but perhaps it exists elsewhere)
  Include a module creation with one psm1 file and a class folder for type.ps1
• Test the newly created module (test the module and the scripts)
• Include a badge on the readme page
• Automate module publishing

[chriskuech]

I am working (slowly) on CI/CD for this (and simultaneously other) PowerShell module repos. I also just created #22 for testing the psm1.

one psm1 file and a class folder for type.ps1

I see value in removing the development files (.git, .vscode, imgs, etc), but are you saying all the script files (except types.ps1) should be merged into a single psm1? If so, what is that value of that over dot-sourced scripts?

[omiossec]

Hi
The values of a unique psm1 file are

• fast loading (but it's not the case now)
• easier to debug and to manipulate
  take a look at
  https://github.com/lazywinadmin/AdsiPS/blob/master/build/tasks.build.ps1

[chriskuech]

GitHub Actions landed, so I finally added CI/CD. I don't build a psm1, but we are no longer publishing redundant dev files (though I have yet to release a new module version). Integration test enforcement and improvement is being tracked in another issue.