September 1st Team meeting today. Management is pushing us hard to seal the deal with this customer we're meeting on the 4th. So, obviously, we're going to make that deal. The company needs it, so it's my job to make it happen. We need a win. September 4th Meeting with
Up until recently I hadn't really used any Dependency Injection (DI) [https://en.wikipedia.org/wiki/Dependency_injection] frameworks in my ASP.NET projects, largely due to them being rather intimidating to set up the first time. I mean, I barely grasp the concept of DI, so the thought of
My coworkers Rajit and Dave [http://www.exceptionnotfound.net/simpler-is-subjective-how-bad-assumptions-about-architecture-kicked-my-ass/] and I have been spending an inordinate amount of time over the last few days looking for a really annoying error in one of our apps. The exception message reads like this: > Could not load file or assembly 'Oracle.DataAccess'
I often give technical demos at my work about various topics, and the most recent one was an introduction to ASP.NET Core 1.0 that spawned a lot of blog posts [http://www.exceptionnotfound.net/tag/asp-net-core/]. Overall, this class was well-received (at least I believe so, given that
Validation is one of the key components in any web app. After all, we should never trust any input to our applications, ever [http://stackoverflow.com/a/2794089/106356]. Up until now, my group has been building MVC-based web apps, in those apps we've been content to use built-in or