Stephen G Tuggy
Stephen G Tuggy
In .NET Core 2.1 and up, I believe the preferred pattern is to use `IHttpClientFactory.CreateClient()` every time you need an HttpClient instance. The default factory implementation then creates HttpClient instances...
> I think it would make more sense to have a custom IHttpClientProvider interface. Then we can implement this in a backwards compatible way with a `StaticHttpClientProvider" implementation that is...
And maybe give your IHttpClientProvider interface a read-only, boolean property that indicates whether or not user code should Dispose() of the IHttpClient it got after it's done with it. `ShouldDisposeAfterUse`...
@brebell Thanks for the information. That is helpful. I will let you know if I find that it fixes my issue.
So I tried changing the path syntax I was using for the OnAccessExcludePath clauses. I was still having a ton of trouble with on-access scanning though. And implementing these changes...
OK, trying those changes now. Thanks.
[This link](https://git-scm.com/docs/git-rebase#_recovering_from_upstream_rebase) should tell you all you need to know. I have personally experienced projects that I worked on, getting seriously messed up because I didn't know better than to...
@ryekerjh The project I was working on ended up with branch A that appeared to be based on branch B, but had additional code changes, with no record of those...
@DropsOfSerenity I can see the advantages of what you are describing. If I could be sure that `git rebase` wouldn't mess up the repos I worked on the way I...
@DropsOfSerenity BTW, you also made a very good point that the overall purpose of git history is strictly utilitarian. And that a literal snapshot of every single atomic change you...