CliWrap v3.4 Release Notes
-
- ➕ Added automatic resolving of script files on Windows (i.e.
.bat
and.cmd
files). Previously, if you didCli.Wrap("foo")
, the underlying implementation ofSystem.Diagnostic.Process
would try to findfoo
in several locations, including directories listed in the PATH environment variable. On Windows, however, this only worked for.exe
files, meaning that it wouldn't findfoo.cmd
orfoo.bat
even if they existed on the PATH. This was an issue withCli.Wrap("npm")
andCli.Wrap("az")
because those CLI tools are implemented as.cmd
scripts on Windows. CliWrap now attempts to resolves those paths itself. (Thanks @AliReZa Sabouri) - 👌 Improved exception thrown when the underlying process fails to start. It now contains the target file path, which can be helpful to identify the exact command that failed. (Thanks @Mohamed Hassan)
⚠ ⚠ Warning: the next major version of CliWrap (4.0) will drop support for legacy .NET Framework, .NET Standard, and .NET Core (prior to rebranding). Going forward, the library will only target .NET 5 and higher. If you have any questions, please comment on this issue.
- ➕ Added automatic resolving of script files on Windows (i.e.