- declared on Line 57
- used on
- Line 341
- This line creates a HostInfo object, which is defined here
- This object is referred to frequently throughout the source code
- Most of these usages are either contributions to the construction of the EditorServicesConfig object or references to one
- These references are usually intances of HostStartupInfo, which also gets declared as "hostInfo"
- These HostStartupInfo and EditorServicesConfig objects hold a lot of data, including data on some of the bootstrapper's parameters. This includes a couple of default values
- Others are used for "Verbose" logging
- These references are usually intances of HostStartupInfo, which also gets declared as "hostInfo"
- Most of these usages are either contributions to the construction of the EditorServicesConfig object or references to one
- Line 393
- Part of function block for GetProfilePathFromProfileObject
- Is combined with the root folder of pwshProfilePath on Line 391
- this guy is declared on Line 384
- references profileObject and profilePathName
- profileObject
- set as profile on Lines 362-365
- profile set on Line 339
- set as profile on Lines 362-365
- profileObject
- references profileObject and profilePathName
- this guy is declared on Line 384
- Line 341
So HostProfileId is a filename prefix used to reference a custom powershell profile that exists in the same directory as the current powershell profile
This is the PowerShell equivalent of Line 393:
function GetProfilePathFromProfileObject( $profile, $user, $host ){ $profilePath = $profile."$user$host" Join-Path -Path (Split-Path $profilePath) -ChildPath "$($HostProfileId)_profile.ps1" }
We need to test this functionality
Discussions
Become a Hackaday.io Member
Create an account to leave a comment. Already have an account? Log In.