v2.1.0

Author: jdhitsolutions

ISERemoteTab.psd1

@@ -59,9 +59,10 @@ $ISERemoteProfile = "C:\Scripts\RemoteProfile.ps1"
 $psise.CurrentPowerShellTab.AddOnsMenu.Submenus.Add($Display,$Action,$shortcut) | Out-Null
 ```
 
+The console function, `New-ISERemoteTab` will also use the value of `$ISERemoteProfile` as its default value.
+
 A sample profile script, [SampleRemoteProfile.ps1](SampleRemoteProfile.ps1), is included with this module.
 
 ## Deprecation Notice
 
 This module should be considered in maintenance-mode. The PowerShell ISE should be considered deprecated. I will try to address bug fixes, but do not expect any other changes or enhancements to this module. If you like the concept of separate remoting sessions, you can achieve similar results with [Windows Terminal](https://docs.microsoft.com/en-us/windows/terminal/get-started).
-

README.md

@@ -15,7 +15,7 @@ Create remote tabs in the PowerShell ISE.
 ### ComputerCredential (Default)
 
 ```yaml
-New-ISERemoteTab -Computername <String[]> [-Credential <PSCredential>] [-Authentication <String>]  [-CertificateThumbprint <String>] [-ConfigurationName <String>] [-Port <Int32>]  [-SessionOption <PSSessionOption>] [-UseSSL] [-ProfileScript <String>] [<CommonParameters>]
+New-ISERemoteTab -Computername <String[]> [-Credential <PSCredential>] [-Authentication <String>]  [-CertificateThumbprint <String>] [-ConfigurationName <String>] [-Port <Int32>] [-SessionOption <PSSessionOption>] [-UseSSL] [-ProfileScript <String>] [<CommonParameters>]
 ```
 
 ### ComputerPrompt
@@ -231,9 +231,9 @@ Accept wildcard characters: False
 
 Specify the path to a profile script file.
 
-hNormally, you do not have a traditional PowerShell profile script when you enter a remote PSSession. But you have the option to specify a profile script that will be executed in the remote session in place of a regular profile script. The form will look in your current session for a variable called ISERemoteProfile which is the path to a ps1 file with your remote profile script.
+hNormally, you do not have a traditional PowerShell profile script when you enter a remote PSSession. But you have the option to specify a profile script that will be executed in the remote session in place of a regular profile script. The command will look in your current session for a variable called ISERemoteProfile which is the path to a ps1 file with your remote profile script.
 
-You can set this in your PowerShell ISE Profile script or you can use the Save script setting checkbox to store the current file in the variable.
+You can set this in your PowerShell ISE Profile script or you can use the Save script setting checkbox when running New-ISERemotTabForm to store the current file in the variable.
 
 Note that this variable is only for the length of your PowerShell session and does NOT update your ISE profile.
 
@@ -244,7 +244,7 @@ Aliases:
 
 Required: False
 Position: Named
-Default value: None
+Default value: $ISERemoteProfile
 Accept pipeline input: False
 Accept wildcard characters: False
 ```

changelog.md

@@ -177,16 +177,16 @@
           <maml:name>ProfileScript</maml:name>
           <maml:description>
             <maml:para>Specify the path to a profile script file.</maml:para>
-            <maml:para>hNormally, you do not have a traditional PowerShell profile script when you enter a remote PSSession. But you have the option to specify a profile script that will be executed in the remote session in place of a regular profile script. The form will look in your current session for a variable called ISERemoteProfile which is the path to a ps1 file with your remote profile script.</maml:para>
-            <maml:para>You can set this in your PowerShell ISE Profile script or you can use the Save script setting checkbox to store the current file in the variable.</maml:para>
+            <maml:para>hNormally, you do not have a traditional PowerShell profile script when you enter a remote PSSession. But you have the option to specify a profile script that will be executed in the remote session in place of a regular profile script. The command will look in your current session for a variable called ISERemoteProfile which is the path to a ps1 file with your remote profile script.</maml:para>
+            <maml:para>You can set this in your PowerShell ISE Profile script or you can use the Save script setting checkbox when running New-ISERemotTabForm to store the current file in the variable.</maml:para>
             <maml:para>Note that this variable is only for the length of your PowerShell session and does NOT update your ISE profile.</maml:para>
           </maml:description>
           <command:parameterValue required="true" variableLength="false">String</command:parameterValue>
           <dev:type>
             <maml:name>String</maml:name>
             <maml:uri />
           </dev:type>
-          <dev:defaultValue>None</dev:defaultValue>
+          <dev:defaultValue>$ISERemoteProfile</dev:defaultValue>
         </command:parameter>
         <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none">
           <maml:name>SessionOption</maml:name>
@@ -288,16 +288,16 @@
           <maml:name>ProfileScript</maml:name>
           <maml:description>
             <maml:para>Specify the path to a profile script file.</maml:para>
-            <maml:para>hNormally, you do not have a traditional PowerShell profile script when you enter a remote PSSession. But you have the option to specify a profile script that will be executed in the remote session in place of a regular profile script. The form will look in your current session for a variable called ISERemoteProfile which is the path to a ps1 file with your remote profile script.</maml:para>
-            <maml:para>You can set this in your PowerShell ISE Profile script or you can use the Save script setting checkbox to store the current file in the variable.</maml:para>
+            <maml:para>hNormally, you do not have a traditional PowerShell profile script when you enter a remote PSSession. But you have the option to specify a profile script that will be executed in the remote session in place of a regular profile script. The command will look in your current session for a variable called ISERemoteProfile which is the path to a ps1 file with your remote profile script.</maml:para>
+            <maml:para>You can set this in your PowerShell ISE Profile script or you can use the Save script setting checkbox when running New-ISERemotTabForm to store the current file in the variable.</maml:para>
             <maml:para>Note that this variable is only for the length of your PowerShell session and does NOT update your ISE profile.</maml:para>
           </maml:description>
           <command:parameterValue required="true" variableLength="false">String</command:parameterValue>
           <dev:type>
             <maml:name>String</maml:name>
             <maml:uri />
           </dev:type>
-          <dev:defaultValue>None</dev:defaultValue>
+          <dev:defaultValue>$ISERemoteProfile</dev:defaultValue>
         </command:parameter>
         <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none">
           <maml:name>PromptForCredential</maml:name>
@@ -364,16 +364,16 @@
           <maml:name>ProfileScript</maml:name>
           <maml:description>
             <maml:para>Specify the path to a profile script file.</maml:para>
-            <maml:para>hNormally, you do not have a traditional PowerShell profile script when you enter a remote PSSession. But you have the option to specify a profile script that will be executed in the remote session in place of a regular profile script. The form will look in your current session for a variable called ISERemoteProfile which is the path to a ps1 file with your remote profile script.</maml:para>
-            <maml:para>You can set this in your PowerShell ISE Profile script or you can use the Save script setting checkbox to store the current file in the variable.</maml:para>
+            <maml:para>hNormally, you do not have a traditional PowerShell profile script when you enter a remote PSSession. But you have the option to specify a profile script that will be executed in the remote session in place of a regular profile script. The command will look in your current session for a variable called ISERemoteProfile which is the path to a ps1 file with your remote profile script.</maml:para>
+            <maml:para>You can set this in your PowerShell ISE Profile script or you can use the Save script setting checkbox when running New-ISERemotTabForm to store the current file in the variable.</maml:para>
             <maml:para>Note that this variable is only for the length of your PowerShell session and does NOT update your ISE profile.</maml:para>
           </maml:description>
           <command:parameterValue required="true" variableLength="false">String</command:parameterValue>
           <dev:type>
             <maml:name>String</maml:name>
             <maml:uri />
           </dev:type>
-          <dev:defaultValue>None</dev:defaultValue>
+          <dev:defaultValue>$ISERemoteProfile</dev:defaultValue>
         </command:parameter>
         <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none">
           <maml:name>VMName</maml:name>
@@ -406,16 +406,16 @@
           <maml:name>ProfileScript</maml:name>
           <maml:description>
             <maml:para>Specify the path to a profile script file.</maml:para>
-            <maml:para>hNormally, you do not have a traditional PowerShell profile script when you enter a remote PSSession. But you have the option to specify a profile script that will be executed in the remote session in place of a regular profile script. The form will look in your current session for a variable called ISERemoteProfile which is the path to a ps1 file with your remote profile script.</maml:para>
-            <maml:para>You can set this in your PowerShell ISE Profile script or you can use the Save script setting checkbox to store the current file in the variable.</maml:para>
+            <maml:para>hNormally, you do not have a traditional PowerShell profile script when you enter a remote PSSession. But you have the option to specify a profile script that will be executed in the remote session in place of a regular profile script. The command will look in your current session for a variable called ISERemoteProfile which is the path to a ps1 file with your remote profile script.</maml:para>
+            <maml:para>You can set this in your PowerShell ISE Profile script or you can use the Save script setting checkbox when running New-ISERemotTabForm to store the current file in the variable.</maml:para>
             <maml:para>Note that this variable is only for the length of your PowerShell session and does NOT update your ISE profile.</maml:para>
           </maml:description>
           <command:parameterValue required="true" variableLength="false">String</command:parameterValue>
           <dev:type>
             <maml:name>String</maml:name>
             <maml:uri />
           </dev:type>
-          <dev:defaultValue>None</dev:defaultValue>
+          <dev:defaultValue>$ISERemoteProfile</dev:defaultValue>
         </command:parameter>
         <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none">
           <maml:name>PromptForCredential</maml:name>
@@ -519,16 +519,16 @@
         <maml:name>ProfileScript</maml:name>
         <maml:description>
           <maml:para>Specify the path to a profile script file.</maml:para>
-          <maml:para>hNormally, you do not have a traditional PowerShell profile script when you enter a remote PSSession. But you have the option to specify a profile script that will be executed in the remote session in place of a regular profile script. The form will look in your current session for a variable called ISERemoteProfile which is the path to a ps1 file with your remote profile script.</maml:para>
-          <maml:para>You can set this in your PowerShell ISE Profile script or you can use the Save script setting checkbox to store the current file in the variable.</maml:para>
+          <maml:para>hNormally, you do not have a traditional PowerShell profile script when you enter a remote PSSession. But you have the option to specify a profile script that will be executed in the remote session in place of a regular profile script. The command will look in your current session for a variable called ISERemoteProfile which is the path to a ps1 file with your remote profile script.</maml:para>
+          <maml:para>You can set this in your PowerShell ISE Profile script or you can use the Save script setting checkbox when running New-ISERemotTabForm to store the current file in the variable.</maml:para>
           <maml:para>Note that this variable is only for the length of your PowerShell session and does NOT update your ISE profile.</maml:para>
         </maml:description>
         <command:parameterValue required="true" variableLength="false">String</command:parameterValue>
         <dev:type>
           <maml:name>String</maml:name>
           <maml:uri />
         </dev:type>
-        <dev:defaultValue>None</dev:defaultValue>
+        <dev:defaultValue>$ISERemoteProfile</dev:defaultValue>
       </command:parameter>
       <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none">
         <maml:name>PromptForCredential</maml:name>

docs/New-ISERemoteTab.md

@@ -73,7 +73,7 @@ Function New-ISERemoteTab {
                     Throw "Cannot validate path $_"
                 }
             })]
-        [string]$ProfileScript
+        [string]$ProfileScript = $ISERemoteProfile
     )
 
     Begin {
@@ -223,7 +223,7 @@ Function New-ISERemoteTab {
                     }
                 } #Try
                 Catch {
-                    Write-Warning "Can't create remote tab to $computer. $($_.exception.Message)."
+                    Write-Warning "Can't create remote tab to $computer. $($_.exception.Message)"
                 }
             }) #foreach computer