Bill Menees

Same problem here as @derekchristensen. But thanks to his Jun 4, 2021 mention of `CancelOnProcessTermination` , I was able to workaround the problem by removing the call to `CancelOnProcessTermination`. Now,...

FWIW, my Menees VS Tools extension has a [FindResultsClassifier.cs](https://github.com/menees/VsTools/blob/master/src/Menees.VsTools/Editor/FindResultsClassifier.cs) to highlight Find Results like this:  Also, the **much** more popular [VSColorOutput](https://marketplace.visualstudio.com/items?itemName=MikeWard-AnnArbor.VSColorOutput) extension has a [FindResultsClassifier.cs](https://github.com/mike-ward/VSColorOutput/blob/master/VSColorOutput/FindResults/FindResultsClassifier.cs) to do something similar....

Text windows with ContentType == FindResults have a completely different set of "Fonts and Colors" than text windows with ContentType == CSharp. See my [FindResultsFormats.cs](https://github.com/menees/VsTools/blob/master/src/Menees.VsTools/Editor/FindResultsFormats.cs) for how I added my...

If anyone using Beta 4 arrives here, you'll find that `ParseResponseFileAs(ResponseFileHandling.Disabled)` mentioned in @elgonzo['s answer](https://github.com/dotnet/command-line-api/issues/1625#issuecomment-1035312635) is gone. The Beta 4-compatible way to treat @-prefixed arguments as something other than response...

Thanks for the update @elgonzo. I already dealt with a bunch of changes going from Beta1 through Beta4. I've been watching this repo for a few years now, and I've...

My .NET 7 app just hit this issue. 🙁 Since this won't be fixed until at least .NET 8, I'm going to remove use of `WindowsFormsApplicationBase` and go with a...

I agree. This is a great project, and it would be nice if it also filled in some of the new .NET instance methods via extensions. I use the [Microsoft.CodeAnalysis.NetAnalyzers](https://github.com/dotnet/roslyn-analyzers#microsoftcodeanalysisnetanalyzers)...

I like this idea. It'll take some work to implement it though, so I'm going to leave this issue open until I can get to it (which may be a...

The suggested possible fix of checking `if (buffer.Length < BlockSize)` won't be sufficient because several things downstream assume that the headerBuf array will be exactly 512 bytes. For example, TarHeader.ParseBuffer...

FWIW, after going back to v1.3.3, our test has been stable again for over a month, and no one has seen the "Header checksum is invalid" error again.