You may be familiar with the term rubber duck debugging [https://en.wikipedia.org/wiki/Rubber_duck_debugging]. This is the idea that in order to help a programmer solve a problem, s/he should explain it to some kind of inanimate object (most commonly a rubber duck), because in
Let's build the ultimate RestSharp client in ASP.NET, and show how we can use RestSharp to consume APIs simply and effectively.
A few weeks back I wrote about a very unusual bug that returned 500 errors for routes that should have been valid [https://www.exceptionnotfound.net/a-stupid-bug-and-a-plea-for-help/]. Recently my team and I, to our great relief, discovered the cause of this bug. Of course, that wasn't before we ended up
The Oracle Client (ODP.NET) that we are using to build a major web project put us in a really stupid bind last week, ultimately causing me to waste two days in search of something that wasn't really going to work in the first place. I'm on something of an
Let's modify RestSharp to handle timeouts with ASP.NET MVC and Web API!