Tracing BundledModulesPath parameter
[#]
- (on the Start-EditorServices cmdlet)
This is an attempt at comprehensively tracing the BundledModulesPath parameter. In this log, all uses of the BundledModulesPath parameter will be documented. This will support my unofficial documentation on the Start-EditorServices cmdlet
Unofficial Documentation:
[#]
[syntax section] - (syntax/usage)
[-BundledModulesPath
< string, not null or empty >]
PSES/module/PSES/Start-EditorServices.ps1:
[#]
[line 44] - (cmdlet-script powershell param block)
[ValidateNotNullOrEmpty()]
[string]
$BundledModulesPath
[#]
[line 116] - (cmdlet-script C# cmdlet call)
Import-Module -Name "$PSScriptRoot/PowerShellEditorServices.psd1"
Start-EditorServices @PSBoundParameters
PSES/module/PSES/PowerShellEditorServices.psd1:
[#]
[line 11] - (module manifest - root module field)
# Script module or binary module file associated with this manifest.
RootModule = if ($PSEdition -eq 'Core')
{ 'bin/Core/Microsoft.PowerShell.EditorServices.Hosting.dll' }
else
{ 'bin/Desktop/Microsoft.PowerShell.EditorServices.Hosting.dll' }
- I believe this is a call to the Microsoft.PowerShell.EditorServices.Hosting namespace - still uncertain about this.
PSES/src/PSES.Hosting/Commands/StartEditorServicesCommand.cs:
[#]
[line 24] - (cmdlet definition)
/// <summary>
/// The Start-EditorServices command, the conventional entrypoint for PowerShell Editor Services.
/// </summary>
...
[Cmdlet(
VerbsLifecycle.Start, "EditorServices",
DefaultParameterSetName = "NamedPipe"
)]
public sealed class StartEditorServicesCommand : PSCmdlet
{ ... }
Discussions
Become a Hackaday.io Member
Create an account to leave a comment. Already have an account? Log In.