You're using HttpClient wrong and it is destabilizing your software — great blog post that told me that we should avoid the use of the “using statement” when working with an HttpClient instance. And that's because disposing it after say a one time use, like doing one API call and then immediately disposing, will leave open/pending socket connections. Do this often enough and you'll accumulate a number of those open/pending socket connections and that will slow down your app. The better approach is to use a single static HttpClient instance in your app.

The always-recent guide to creating a development environment for Node and React (with Babel and Webpack) — good guide to setting up a full-stack JavaScript development environment on your local, with an eye toward ReactJS.

Good blog posts on how to create Windows Services using .NET Core:

• Creating Windows Services In .NET Core – Part 1 – The “Microsoft” Way
• Creating Windows Services In .NET Core – Part 2 – The “Topshelf” Way

Combining multiple changes into one commit is a bad idea, because then you cannot revert the single change that you want to revert, without reverting all the other changes that came along with it.

Inadvertently discovered a way to find out who is running a specific process on a server. This is useful if you cannot remote into the server, like say because the connections are full. Using Visual Studio, you can do “Attach to Process” on a server. Assuming that server is setup with remote debugging, doing so will get you a listing of the apps/processes running on that server, plus which user are running those apps/processes.

And now you know where I got the name for this blog as well.

Tags: #DevNotes #Bookmarks #DotNet #Caching #HttpClient #ReactJS #WindowsServices #SourceControlBestPractices #TroubleshootingWindowsProcesses

Discuss... or leave a comment below.