e3a004c036
It's to solve a side-by-side problem we have with powershell core. If a .NET Core version assembly has the same name as it's .NET ancestor in GAC, then even if you specify the file path to `Import-Module`, powershell core will still load the one in GAC because it tries 'Assembly.Load' first. Now we change it to use `Assembly.LoadFrom` first when a file path is given, so it works for modules that have side-by-side assemblies. |
||
|---|---|---|
| .. | ||
| common/markdown | ||
| csharp | ||
| docker/networktest | ||
| powershell | ||
| PSReadLine | ||
| shebang | ||
| tools | ||
| README.md | ||
| Test.Common.props | ||
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.