see changelog for v2.2.0

Author: jdhitsolutions

PSScriptTools.psd1

@@ -16,7 +16,14 @@ or in PowerShell Core:
 Install-Module PSScriptTools -scope currentuser
 ```
 
-Please post any questions, problems or feedback in Issues. Any input is greatly appreciated.
+Starting in v2.2.0, the module was restructured to better support Desktop and Core editions. It is recommended that you uninstall any version older than 2.2.0 and then install the latest version from the PowerShell Gallery.
+
+```powershell
+Uninstall-Module PSScriptTools -allversions
+```
+Any command that uses WPF will not run on PowerShell Core and is not exported.
+
+Please post any questions, problems or feedback in [Issues](https://github.com/jdhitsolutions/PSScriptTools/issues). Any input is greatly appreciated.
 
 ## [Add-Border](docs/Add-Border.md)
 
@@ -565,20 +572,20 @@ Use this command to compare module versions between what is installed against an
 PS C:\> Compare-Module | Where UpdateNeeded | Out-Gridview -title "Select modules to update" -outputMode multiple | Foreach { Update-Module $_.name }
 ```
 
-Compare modules and send results to Out-Gridview. Use Out-Gridview as an object picker to decide what modules to update.
+Compare modules and send results to `Out-Gridview`. Use `Out-Gridview` as an object picker to decide what modules to update.
 
 ## [Get-WindowsVersion](docs/Get-WindowsVersion.md)
 
 This is a PowerShell version of the `winver.exe` utility. This command uses PowerShell remoting to query the registry on a remote machine to retrieve Windows version information.
 
 ```powershell
-PS C:\> get-windowsversion -Computername srv1,srv2,win10 -Credential company\artd | format-table
+PS C:\> get-windowsversion -Computername srv1,srv2,win10 -Credential company\artd
 
-ProductName                             EditionID          ReleaseId Build      InstalledUTC          Computername
------------                             ---------          --------- -----      ------------          ------------
-Windows Server 2016 Standard Evaluation ServerStandardEval 1607      14393.2273 12/26/2018 4:07:25 PM SRV1
-Windows Server 2016 Standard Evaluation ServerStandardEval 1607      14393.2273 12/26/2018 4:08:07 PM SRV2
-Windows 10 Enterprise Evaluation        EnterpriseEval     1703      15063.1387 12/26/2018 4:08:11 PM WIN10
+ProductName                   EditionID          ReleaseId Build      InstalledUTC          Computername
+-----------                   ---------          --------- -----      ------------          ------------
+Windows Server 2016 Standard  ServerStandardEval 1607      14393.2273 12/26/2018 4:07:25 PM SRV1
+Windows Server 2016 Standard  ServerStandardEval 1607      14393.2273 12/26/2018 4:08:07 PM SRV2
+Windows 10 Enterprise Evaluat EnterpriseEval     1703      15063.1387 12/26/2018 4:08:11 PM WIN10
 ```
 
 ### [Get-WindowsVersionString](docs/Get-WindowsVersionString.md)
@@ -587,7 +594,8 @@ This command is a variation of `Get-WindowsVersion` that returns a formatted str
 
 ```powershell
 PS C:\> Get-WindowsVersionString
-Windows 10 Pro Version 1809 (OS Build 17763.195)
+BOVINE320 Windows 10 Pro Version Professional (OS Build 17763.253)
+
 ```
 
 ## [New-PSFormatXML](docs/New-PSFormatXML.md)
@@ -679,11 +687,12 @@ Position                        : Named
 ValueFromPipeline               : False
 ValueFromPipelineByPropertyName : False
 Type                            : System.String[]
+IsDynamic                       : False
 ParameterSet                    : __AllParameterSets
 ```
 
 ## Compatibility
 
 Where possible these commands have been tested with PowerShell Core, but not every platform. If you encounter problems, have suggestions or other feedback, please post an issue.
 
-*last updated 17 February 2019*
+*last updated 21 February 2019*

README.md

@@ -1,5 +1,19 @@
 # Change Log for PSScriptTools
 
+## v2.2.0
+
++ Code revisions in `ConvertTo-WPFGrid` (Issue #27)
++ Updated `Get-ParameterInfo` to reflect dynamic parameters (Issue #28)
++ Updated `Get-PSLocation` to better reflect locations and use a custom format file.
++ Updated `Get-WindowsVersion` with custom type for format file. Also better handling of non-Windows platforms.
++ Updated `Get-WindowsVersionString` to include the computername.
++ Updated `New-WPFMessageBox` to gracefully exit if running on PowerShell Core.
++ Updated `Test-ExpressionForm` to gracefully exit if running on PowerShell Core.
++ Updated `New-RandomFilename` to better reflect locations using `[environment]`
++ Modified manifest to be more aware of PSEdition and only load compatible commands.
++ Help updates
++ Updated `README.md`
+
 ## v2.1.0
 
 + Added parameter to allow user to specify a type name with `New-PSFormatXML` (Issue #26)

changelog.md

@@ -1,7 +1,7 @@
 ---
 external help file: PSScriptTools-help.xml
 Module Name: PSScriptTools
-online version: 
+online version:
 schema: 2.0.0
 ---
 
@@ -27,8 +27,7 @@ Add-Border [-TextBlock] <String[]> [-Character <String>] [-InsertBlanks] [-Tab <
 
 ## DESCRIPTION
 
-This command will create a character or text based border around a line of text.
-You might use this to create a formatted text report or to improve the display of information to the screen.
+This command will create a character or text based border around a line of text. You might use this to create a formatted text report or to improve the display of information to the screen.
 
 ## EXAMPLES
 
@@ -140,7 +139,7 @@ Insert blank lines before and after the text. The default behavior is to create
 ```yaml
 Type: SwitchParameter
 Parameter Sets: (All)
-Aliases: 
+Aliases:
 
 Required: False
 Position: Named

docs/Add-Border.md

@@ -79,6 +79,6 @@ Learn more about PowerShell: http://jdhitsolutions.com/blog/essential-powershell
 
 ## RELATED LINKS
 
-[Import-PowerShellDatafile]())
+[Import-PowerShellDatafile]()
 
 [Convert-HashtabletoCode](./Convert-HashtabletoCode.md)

docs/Convert-HashtableString.md

@@ -164,4 +164,3 @@ This was originally described at: http://jdhitsolutions.com/blog/2013/01/convert
 [About_Hash_Tables]()
 
 [Get-Member]()
-

docs/ConvertTo-HashTable.md

@@ -22,7 +22,7 @@ ConvertTo-WPFGrid [[-InputObject] <PSObject>] [[-Title] <String>] [[-Timeout] <I
 
 This command is an alternative to Out-Gridview. It works much the same way. Run a PowerShell command and pipe it to this command. The output will be displayed in an autosized data grid. You can click on column headings to sort. You can resize columns and you can re-order columns. You will want to be selective about which properties you pipe through to this command. See examples.
 
-You can specify a timeout value which will automatically close the form. If you specify a timeout and the Refresh parameter, then the contents of the datagrid will automatically refreshed using the timeout value as an integer. This will only work when you pipe a PowerShell expression to ConvertTo-WPFGrid.
+You can specify a timeout value which will automatically close the form. If you specify a timeout and the Refresh parameter, then the contents of the datagrid will automatically refreshed using the timeout value as an integer. This will only work when you pipe a PowerShell expression to ConvertTo-WPFGrid as one command. This will fail if you break the command in the PowerShell ISE or use a nested prompt.
 
 This command runs the WPF grid in a new runspace so your PowerShell prompt will not be blocked. However, after closing the form you may be left with the runspace. You can use Remove-Runspace to clean up or wait until you restart PowerShell.
 
@@ -46,7 +46,7 @@ PS C:\> Get-VM -computername $VMHost | Select Name,State,Uptime,
 ConvertTo-WPFGrid -title "VM Report $VMHost" -timeout 20
 ```
 
-Get Hyper-V virtual machine information and display for 20 seconds before automatically closing.
+Get Hyper-V virtual machine information and display for 20 seconds before automatically closing. Note that this would be written as one long pipelined expression. It is formatted here for the sake of the help documentation.
 
 ## PARAMETERS
 
@@ -84,8 +84,7 @@ Accept wildcard characters: False
 
 ### -Timeout
 
-By default the grid will remain displayed until you manually close it. But you can specify a timeout interval in seconds.
-The minimum accepted value is 5 seconds. If you use this parameter with -Refresh, then the datagrid will be refreshed with results of the PowerShell expression you piped to ConvertTo-WPFGrid.
+By default the grid will remain displayed until you manually close it. But you can specify a timeout interval in seconds. The minimum accepted value is 5 seconds. If you use this parameter with -Refresh, then the datagrid will be refreshed with results of the PowerShell expression you piped to ConvertTo-WPFGrid.
 
 ```yaml
 Type: Int32

docs/ConvertTo-WPFGrid.md

@@ -1,7 +1,7 @@
 ---
 external help file: PSScriptTools-help.xml
 Module Name: PSScriptTools
-online version: 
+online version:
 schema: 2.0.0
 ---
 
@@ -150,5 +150,4 @@ Learn more about PowerShell: http://jdhitsolutions.com/blog/essential-powershell
 
 ## RELATED LINKS
 
-[Get-Command]()
-
+[Get-Command]()

docs/Copy-Command.md

@@ -19,7 +19,7 @@ Find-CimClass [-Classname] <String> [-Exclude <String>] [-Computername <String>]
 
 ## DESCRIPTION
 
-This function is designed to search an entire CIM repository for a class name. Sometimes, you may have a guess about a class name but not know the full name or even the correct namespace. `Find-CimClass` will recursively search for a given classname. You can use wildcards and search remote computers.
+This function is designed to search an entire CIM repository for a class name. Sometimes, you may have a guess about a class name but not know the full name or even the correct namespace. Find-CimClass will recursively search for a given classname. You can use wildcards and search remote computers.
 
 ## EXAMPLES
 

docs/Find-CimClass.md

@@ -67,11 +67,8 @@ You can then import this xml file in another session to restore these variables.
 
 ```powershell
 PS C:\> function foo { . c:\scripts\get-myvariable2.ps1;$a=4;$b=2;$c=$a*$b;get-MyVariable -notypeinformation -scope 1 -verbose;$c}
-```
-
-This sample function dot sources the script with this function. Within the function, Get-MyVariable is called specifying scope 1, or the parent scope. Scope 0 would be the scope of the Get-MyVariable function. Here's the result.
 
-PS S:\> foo
+PS C:\> foo
 VERBOSE: Getting system defined variables
 VERBOSE: Found 49
 VERBOSE: Getting current variables in 1 scope
@@ -85,6 +82,8 @@ b                              2
 c                              8
 VERBOSE: Finished getting my variables
 8
+```
+This sample function dot sources the script with this function. Within the function, Get-MyVariable is called specifying scope 1, or the parent scope. Scope 0 would be the scope of the Get-MyVariable function. Here's the result.
 
 ### EXAMPLE 5