History

Steve Lee 5dc7a6cb07 Add Windows Compatibility Pack 2.0.0 to PS Core and adopt the official .NET Core 2.1 (#6958 ) To support PowerShell modules built with .NET Windows Compatibility Pack, we decided that it was best to ship the WCP assemblies with PS Core. This also adds many new .NET APIs be default while only adding ~3.5 MB additional disk footprint (to a ~137 MB install currently). Also update the build to adopt the official .NET Core 2.1.		2018-06-03 22:06:26 -07:00
..
common/markdown	Remove extraneous SSH and install docs from the 'demos' folder (#6628 )	2018-04-13 15:50:54 -07:00
csharp	Add Windows Compatibility Pack 2.0.0 to PS Core and adopt the official .NET Core 2.1 (#6958 )	2018-06-03 22:06:26 -07:00
docker/networktest	Update copyright and license headers (#6134 )	2018-02-13 09:23:53 -08:00
hosting	Add tests for PowerShell hosting API to verify MyGet packages (#6737 )	2018-04-27 13:25:33 -07:00
packaging/windows	Simplify the paths the MSI uses (#6442 )	2018-04-02 10:47:29 -07:00
powershell	Cleanup FileSystem provider (#6909 )	2018-06-04 10:00:56 +05:00
shebang
tools	Add Windows Compatibility Pack 2.0.0 to PS Core and adopt the official .NET Core 2.1 (#6958 )	2018-06-03 22:06:26 -07:00
README.md
Test.Common.props	Update PowerShell to build with .NET Core SDK 2.1.300-rc1-008662 (#6718 )	2018-05-02 16:58:39 -07:00

README.md

Testing

The tests are organized by testing language. Thus Pester tests, which are written in the PowerShell language, are in ./powershell and xUnit tests, written in C#, are in ./csharp. The sanity tests for the Full .NET build of PowerShell are in ./fullclr, and the third-party shebang test is in ./shebang.