We recently started using CliWrap in a project, and… 👍
Glad you liked it 🙂
Hi!
Just thought it was quite cool how the piping model in CliWrap (a library I made) enables you to think about the problem using completely different paradigms.
You can read about piping with CliWrap here
Just took a quick glance at the image. Did you overload | or is this a bitwise “or” as expected?
Also what’s the purpose of CliWrap?
We’ve integrated CliWrap into a new DAG based dev-tool building framework at my company and it has treated us VERY well! Thank you!
Very cool. Also I have to say I feel your flair so much lol
Love CliWrap. Been using it for a year now and its made calling external executables so much easier. Even as background tasks triggered from a webapi. Thank you!
Now I just have to figure how to pipe the stdout to a blazor server side webapp. Similar to Azure’s webjobs logging console 🙂
Glad you liked it!
Worst case scenario, you can always pipe to a delegate and take it from there 😉
I like the interface. Is this open source?
Yes: https://github.com/Tyrrrz/CliWrap
I know some disagree, but I very much dislike your usage of var here. What type is cmd? What type is result? stdOutLines in the second approach is clear.
C# devs
null reference exceptions