Timeline for answer to Echo equivalent in PowerShell for script testing by Richard
Current License: CC BY-SA 3.0
Post Revisions
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Mar 9, 2018 at 19:28 | history | suggested | Jacktose | CC BY-SA 3.0 |
links to MS docs (additional section still needs citation)
|
| Mar 9, 2018 at 18:13 | review | Suggested edits | |||
| S Mar 9, 2018 at 19:28 | |||||
| Jul 22, 2013 at 7:07 | history | edited | Richard | CC BY-SA 3.0 |
Better formatting
|
| Jul 26, 2012 at 14:17 | history | edited | Richard | CC BY-SA 3.0 |
Better markup
|
| Jan 15, 2010 at 11:50 | history | edited | Richard | CC BY-SA 2.5 |
Added note on -verbose and -debug switches.
|
| Nov 2, 2009 at 7:11 | comment | added | Jaykul | You also want to get familiar with Out-String, because with any non-trivial object, you'll need to use that to convert the object to a display-able string before using any of those three Write-* cmdlets. | |
| Apr 2, 2009 at 20:04 | comment | added | JasonMArcher | The nice thing about Write-Debug and Write-Verbose is that you can leave your debug statements in your code, and just turn on the output when you need it using the appropriate preference variable. Saves time and is a nice feature for other users of your functions. | |
| Apr 1, 2009 at 23:28 | vote | accept | phill | ||
| Apr 1, 2009 at 22:59 | history | answered | Richard | CC BY-SA 2.5 |