fixed the broken links and other minor updates due to the recent learning-powershell path changes.

This commit is contained in:
Jianyun Tao committed 2016-08-01 11:21:55 -07:00
1 parent bc4fe11888
commit 1e7a49600d
7 files changed
+17 -21

No files matched your search

+2 -2
View File
@@ -139,7 +139,7 @@ Additional references:
our [CI system (Travis CI and AppVeyor)][ci-system]
will run a suite of tests and automatically update the status of the pull request.
#### Pull Request / Code Review
#### Pull Request - Code Review
* After a successful test pass,
the area maintainers will do a code review,
@@ -179,7 +179,7 @@ please follow the [PowerShell Request for Comments (RFC)](https://github.com/Pow
Common Engineering Practices
----------------------------
Other than the guidelines for ([coding](../docs/coding-guidelines/coding-guidelines.md),
Other than the guidelines for ([coding](../docs/coding-guidelines.md),
the [RFC process](https://github.com/PowerShell/PowerShell-RFC) for design,
[documentation](#contributing-to-documentation) and [testing](../docs/testing-guidelines/testing-guidelines.md)) discussed above,
we encourage contributors to follow these common engineering practices:
@@ -1,10 +1,3 @@
author: Jason/Andy
> meaning of label, assignees, etc.
> triage process
> requirements for resolving (timing), closing...
## Long-living issue labels
### Feature areas
+6 -6
View File
@@ -52,11 +52,6 @@ Click on the following link to create your first PowerShell script.
- [Using Visual Studio Code (VS Code)][use-vscode-editor]
On Windows, you can also use [PowerShell Integrated Scripting Environment (ISE)][use-ise-editor] to edit PowerShell scripts.
[use-vscode-editor]:./using-vscode.md#editing-with-vs-code
[use-ise-editor]:./using-ise.md#editing-with-ise
PowerShell Debugger
----
@@ -66,11 +61,16 @@ Click on the link below to learn more about debugging:
- [Using Visual Studio Code (VS Code)][use-vscode-debugger]
- [PowerShell Command-line Debugging][cli-debugging]
On Windows, you can also use [ISE][use-ise-debugger] to debug PowerShell scripts.
On Windows, you can also use [PowerShell Integrated Scripting Environment (ISE)][use-ise-editor] to edit or debug PowerShell scripts.
However it is not supported if you are using PowerShell installed from the [PowerShell package][get-powershell] or directly [built][building-the-repository] from GitHub.
[use-vscode-editor]:./using-vscode.md#editing-with-vs-code
[use-ise-editor]:./using-ise.md#editing-with-ise
[use-vscode-debugger]:./using-vscode.md#debugging-with-vs-code
[use-ise-debugger]:./using-ise.md#debugging-with-ise
[cli-debugging]:./debugging-from-commandline.md
[get-powershell]:../../README.md#get-powershell
[build-powershell]:../../README.md#building-the-repository
PowerShell Testing
@@ -23,7 +23,7 @@ Write-Host "$result Celsius"
**1. Setting a Breakpoint on a Line**
- Open a [PowerShell editor](learning-powershell.md#powershell-editor)
- Open a [PowerShell editor](README.md#powershell-editor)
- Save the above code snippet to a file. For example, "test.ps1"
- Go to your command-line PowerShell
- Clear existing breakpoints if any
@@ -54,7 +54,7 @@ At /home/jen/debug/test.ps1:5 char:1
[DBG]: PS /home/jen/debug>>
```
- The PowerShell prompt now has the prefix **[DBG]:** as you may noticed. This means
- The PowerShell prompt now has the prefix **[DBG]:** as you may have noticed. This means
we have entered into the debug mode. To watch the variables like $celsius, simply type **$celsius** as below.
- To exit from the debugging, type **q**
- To get help for the debugging commands, simply type **?**. The following is an example of debugging output.
@@ -7,7 +7,7 @@ We recommend that you open a PowerShell console/session and type along with the
Launch PowerShell Console/Session
---
First you need to launch a PowerShell session by following the [Installing PowerShell Guide](./learning-powershell.md#installing-powershell).
First you need to launch a PowerShell session by following the [Installing PowerShell Guide](./README.md#installing-powershell).
Getting Familiar with PowerShell Commands
@@ -213,7 +213,7 @@ PS /> Get-Help -Name Get-Process
It displays the examples how to use the Get-Process cmdlet.
```PowerShell
PS />**Get-Help -Name Get-Process -Examples**
PS />Get-Help -Name Get-Process -Examples
```
If you use **-Full** parameter, for example, `Get-Help -Name Get-Process -Full`, it will display more technical information.
+3
View File
@@ -1,6 +1,7 @@
Using PowerShell Integrated Scripting Environment (ISE)
====
The PowerShell ISE only works on Windows. If you are not using Windows, please see [Using Visual Studio Code](./using-vscode.md).
Please note the ISE is not supported if you are using PowerShell installed from the [PowerShell package][get-powershell] or directly [built][building-the-repository] from GitHub.
Editing with ISE
---
@@ -72,3 +73,5 @@ PS C:\test>
See [How to Debug in ISE][debug] for more information.
[debug]:https://msdn.microsoft.com/en-us/powershell/scripting/core-powershell/ise/how-to-debug-scripts-in-windows-powershell-ise#bkmk_2
[get-powershell]:../../README.md#get-powershell
[build-powershell]:../../README.md#building-the-repository
+2 -2
View File
@@ -8,7 +8,7 @@ Here we choose VS Code as a PowerShell editor as an example.
You can use VS Code on Windows with PowerShell V5 by using Windows 10 or by installing [Windows Management Framework 5.0 RTM](https://www.microsoft.com/en-us/download/details.aspx?id=50395) for down-level Windows OSs (e.g. Windows 8.1, etc.).
Before starting it, please make sure PowerShell exists on your system.
By following the [Installing PowerShell](./learning-powershell.md#installing-powershell) instructions you can install PowerShell and launch a PowerShell session.
By following the [Installing PowerShell](./README.md#installing-powershell) instructions you can install PowerShell and launch a PowerShell session.
Editing with VS Code
----
@@ -109,4 +109,4 @@ There are a few blogs that may be helpful to get you started using PowerShell ex
PowerShell Extension for VS Code
----
PowerShell extension source code can be found [GitHub](https://github.com/PowerShell/vscode-powershell-ops)
PowerShell extension source code can be found [GitHub](https://github.com/PowerShell/vscode-powershell-ops).