Module Philosophy

[jdhitsolutions]

The goal of this module is to provide a welcome introduction to people new to PowerShell 7. The idea is that they might see the welcome splash screen as part of their profile. The tutorial features are intended to be the most fundamental knowledge a beginner should know. I don't want to turn this into a tutorial module.

[PaulDash]

Someone would need to already be pretty proficient in PowerShell to locate and install your module. What would you say is your aim in terms of distribution:

• for IT departments to load this into profile scripts of their users?
• inclusion into core PowerShell as an OOBE type welcome page?

[SamErde]

It could be pretty easy to share and find this module if Microsoft is willing to create an aka.ms URL.

A clear and simple readme/docs site can make anyone a fast user.

Along with a "getting started" function, the module could include another function to add itself to the user's profile.

What are your thoughts on using ScriptsToProcess to provide instant functionality to the user?

[jdhitsolutions]

Technically, adding a line to a profile or even creating it isn't difficult. But there are potential obstacles with execution policy or other settings which might be managed with Group Policy.

[SamErde]

Technically, adding a line to a profile or even creating it isn't difficult. But there are potential obstacles with execution policy or other settings which might be managed with Group Policy.

Would these primarily be obstacles to running the module or obstacles to modifying the profile? I'm a sucker for engineering around edge cases, ha ha, so do you think there are conditions that a function could check and then validate functionality, or are the potential blockers to diverse to reliably detect?

[jdhitsolutions]

I would never want to presume to modify a user's profile. But I could easily add a function to add a line to the profile. I was also considering a command to create the current user current host profile.

[SamErde]

I would never want to presume to modify a user's profile. But I could easily add a function to add a line to the profile. I was also considering a command to create the current user current host profile.

100% agree about not presuming to modify the profile. I believe the idea was to make it easy to add if the user elects to run a function that adds it for them. (Or better yet, teach them how to create a profile and add it themselves.)

[jdhitsolutions]

The next module version will include Add-PSIntro which will add a Get-PSIntro command to the user's current user current host profile. If the profile doesn't exist, the user will be prompted to create it.

PS C:\> add-psintro -ModuleStatus -Verbose
VERBOSE: [13:33:01.4806843 BEGIN  ] Starting module command Add-PSIntro
VERBOSE: [13:33:01.4806843 BEGIN  ] Using module version 2.0.0
VERBOSE: [13:33:01.4806843 BEGIN  ] Executing in PowerShell v5.1.26100.7462
VERBOSE: [13:33:01.4806843 PROCESS] Testing PowerShell profile script
C:\Users\Jeff\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1
VERBOSE: [13:33:01.4963642 PROCESS] Updating PowerShell profile script
C:\Users\Jeff\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1
VERBOSE: [13:33:01.4963642 END    ] Ending module command Add-PSIntro