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

spelling fixes: docs

Browse Source 
additional fixes to grammar in windows-full.md per alexandair
This commit is contained in:
Josh Soref committed 2016-08-25 17:43:20 +00:00
1 parent b375807d7f
commit de64180d56
5 files changed
+7 -5
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/building/windows-core.md
+1 -1
View File
@@ -85,7 +85,7 @@ You can run our cross-platform Pester tests with `Start-PSPester`.
Building in Visual Studio
-----------------------------
We do not recommend building the Poweshell solution from Visual Studio. This may lead to package version mismatches with errors similar to:
We do not recommend building the PowerShell solution from Visual Studio. This may lead to package version mismatches with errors similar to:
```
C:\dev\powershell\src\System.Management.Automation\project.json(142,77): error NU1001: The dependency Microsoft.PowerShe
ll.CoreCLR.AssemblyLoadContext >= 1.0.0-* could not be resolved.
docs/building/windows-full.md
+3 -1
View File
@@ -70,7 +70,9 @@ What can you do with the produced binaries?
**Important**: "We don’t support production deployments of these binaries on any platform". For PowerShell .NET (aka: FullCLR PowerShell) our recommendation is to continue using the PowerShell .NET version already shipping in Windows Client and Windows Server.
The primary reason to build the PowerShell FullCLR binaries is to test backward compatibility, and interoperability between .NET and CoreCLR. It is also important to mention some features like PowerShell Workflows are not currently available in the CoreCLR version. So we want to provide the ability for the Community to test CoreCLR PowerShell code changes while validating that these changes don't introduce regressions in .NET PowerShell (aka: as FullCLR PowerShell)
The primary reason to build the PowerShell FullCLR binaries is to test backward compatibility, and interoperability between .NET and CoreCLR.
It is also important to mention that some features like PowerShell Workflows are not currently available in the CoreCLR version.
We want to provide the ability for the Community to test CoreCLR PowerShell code changes while validating that these changes don't introduce regressions in .NET PowerShell (aka: as FullCLR PowerShell).
To run (for test purposes) the dev version of these binaries please follow the following steps: