From ed7af2addb236e1268d741c2f95d0304ea414f13 Mon Sep 17 00:00:00 2001 From: Christoph Wille Date: Sun, 22 Mar 2020 12:54:30 +0100 Subject: [PATCH] Windows: keep using Windows PowerShell, other OSs fall back on pwsh (to reduce deps to get up and running on Windows) --- ICSharpCode.Decompiler/ICSharpCode.Decompiler.csproj | 5 ++++- README.md | 1 - 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/ICSharpCode.Decompiler/ICSharpCode.Decompiler.csproj b/ICSharpCode.Decompiler/ICSharpCode.Decompiler.csproj index d7cd56cf4..2e73ea060 100644 --- a/ICSharpCode.Decompiler/ICSharpCode.Decompiler.csproj +++ b/ICSharpCode.Decompiler/ICSharpCode.Decompiler.csproj @@ -624,7 +624,10 @@ - + + powershell -NoProfile -ExecutionPolicy Bypass -File BuildTools/update-assemblyinfo.ps1 $(Configuration) + + pwsh -NoProfile -ExecutionPolicy Bypass -File BuildTools/update-assemblyinfo.ps1 $(Configuration) diff --git a/README.md b/README.md index 0a2486442..f9aa68fc0 100644 --- a/README.md +++ b/README.md @@ -45,7 +45,6 @@ Windows: - Workload "Visual Studio extension development" (ILSpy.sln contains a VS extension project) - Individual Component "MSVC v142 - VS 2019 C++ x64/x86 build tools (v14.23)" (or similar) - The VC++ toolset is optional; if present it is used for `editbin.exe` to modify the stack size used by ILSpy.exe from 1MB to 16MB, because the decompiler makes heavy use of recursion, where small stack sizes lead to problems in very complex methods. -- Make sure [PowerShell](https://github.com/PowerShell/PowerShell) is installed (formerly known as PowerShell Core) - recommended way of installation via [choco install powershell-core](https://chocolatey.org/packages/powershell-core) - Check out the ILSpy repository using git. - Execute `git submodule update --init --recursive` to download the ILSpy-Tests submodule (used by some test cases). - Open ILSpy.sln in Visual Studio.