GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - modulexcite/ModuleBuilder: A PowerShell Module to help scripters write, version, sign, package, and publish.

BranchesTags
Open more actions menu
 
 

Latest commit

 

History

31 Commits
31 Commits

Folders and files

NameName
Last commit message
Last commit date
Content
Content
 
 
Authenticode.psd1
Authenticode.psd1
 
 
Authenticode.psm1
Authenticode.psm1
 
 
EditFunction.psm1
EditFunction.psm1
 
 
ExecutionPolicy.psm1
ExecutionPolicy.psm1
 
 
GitHub.psm1
GitHub.psm1
 
 
ISETools.psm1
ISETools.psm1
 
 
License.md
License.md
 
 
ModuleBuilder.psd1
ModuleBuilder.psd1
 
 
ModuleBuilder.psm1
ModuleBuilder.psm1
 
 
ModuleCreation.ps1
ModuleCreation.ps1
 
 
NewModule.psm1
NewModule.psm1
 
 
README.md
README.md
 
 
ResolveAlias.psm1
ResolveAlias.psm1
 
 

Repository files navigation

ModuleBuilder

A PowerShell Module to help scripters write, version, sign, package, and publish.

Goals/Ideas

The primary goal of this module is to increase the ease and consistency of PowerShell module creation as well as provide a structure to the project that makes it easy for others to contribute and for the owners to integrate those changes in.

Take a look at the wiki for more details

Features

Module Creation


  • Build folder, psd1/psm1
  • Create/link github repo
  • Setup GitHub
    • Support Templates? (package all the info below)
    • Build Pages site
      • Push help files there? (seperate cmdlet part of 'release' that changes function online help path etc etc)
    • Build Wiki
      • Insert basic docs that represent best practice for community contributions, how to build dev env, submition formats etc
      • Build common sections (FAQ,Contact,etc)
    • Create Tag types for community standard (Some sort of indication that the issue submitter is willing to create the resolution/feature)
    • Create ReadMe.md
      • Inject a todo/checklist for the creator to help guide them (based on template/project type)
  • Be aware of an Icon/Logo?
  • Wizard driven (UI to run cmdlets for you)

Module Management

  • Version management
  • Help file creation/publication (github pages?)
    • Create a default About_ModuleName help file
    • Convert Comment based help to xml/lang based help
  • Auto (cmdlet based) add functions/files to psd1/psm1 (internals ignore by naming convention?)
    • Assume ps1's are function files and add to psm1 to load?

File Tools

  • Clean files (expand alias, formatting type stuff)
  • Run against PSAnalyzer?
  • Function Builder (GUI based tool to build functions shells/params)
    • Also spews XML based help file

Testing

  • Help build tests?
  • Insert test folder with first basic test?
  • Allow for AppVeyor setup (yml file)

Sign

  • Automatically sign scripts upon release

package

  • Create a package (oneget/nuget/whatever)

Release

  • Publish as a release on github, choco, psgallery

Next Steps

  1. Define workflows
  2. Design workflow (what are the steps to build/publish)
  3. Design cmdlets to address that workflow
  4. Create Template Data
  5. Build Tests
  6. Build Functions

About

A PowerShell Module to help scripters write, version, sign, package, and publish.

Resources

Readme
MS-PL license
Activity

Stars

0 stars

Watchers

1 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.