aphrody-labs/PowerShell
1
0 Fork 0
mirror of https://github.com/aphrody-labs/PowerShell.git synced 2026-10-17 04:36:39 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #1602 from alexandair/patch-2

Browse Source 
fixing casing and typos in windows-full.md
This commit is contained in:
Raghu Shantha [MSFT] authored and GitHub committed 2016-08-02 10:34:31 -07:00
2 parents ae67cc4676 0160488925
commit 1ee990ac0d
1 file changed
+4 -4
Download Patch File Download Diff File Expand all files Collapse all files
docs/building/windows-full.md
+4 -4
View File
@@ -74,12 +74,12 @@ What I can do with the produced binaries?
Creating a deployable package out of them is **not a supported scenario**.
The reason why we are building these binaries is
we have components (i.e. workflows) that are not currently available in the CoreClr version.
We want to make sure that CoreClr PowerShell changes don't introduce regressions in FullClr PowerShelll.
we have components (i.e. workflows) that are not currently available in the CoreCLR version.
We want to make sure that CoreCLR PowerShell changes don't introduce regressions in FullCLR PowerShell.
It's possible to run (for test purposes) the dev version of these binaries as follows.
Running Dev version of FullClr PowerShell
Running Dev version of FullCLR PowerShell
-----------------------------------------
Running FullCLR version is not as simple as CoreCLR version.
@@ -89,7 +89,7 @@ process, but all the interesting DLLs (such as
`System.Management.Automation.dll`) would be loaded from the Global
Assembly Cache (GAC), not your output directory.
Use `Start-DevPowerShell` helper funciton, to workaround it with `$env:DEVPATH`
Use `Start-DevPowerShell` helper function to workaround it with `$env:DEVPATH`
```powershell
Start-DevPowerShell -FullCLR