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

fixing casing and typos in windows-full.md

Browse Source 
Fixing casing for CoreCLR and FullCLR.
Fixing a couple of typos.
This commit is contained in:
Aleksandar Nikolić authored and GitHub committed 2016-08-02 18:17:04 +02:00
1 parent ae67cc4676
commit 0160488925
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**. Creating a deployable package out of them is **not a supported scenario**.
The reason why we are building these binaries is 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 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 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. 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. 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 `System.Management.Automation.dll`) would be loaded from the Global
Assembly Cache (GAC), not your output directory. 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 ```powershell
Start-DevPowerShell -FullCLR Start-DevPowerShell -FullCLR