Last week I published a post entitled Opinion Time: Should Developers ALWAYS Build an API? [https://www.exceptionnotfound.net/opinion-time-should-developers-always-build-an-api/] . I got quite a bit of useful feedback on that post, and so I decided that I needed to publish a followup post so that I could parse and interpret
There's been some talk in my office lately about the practicality of always building API (Application Programming Interfaces) backends for our apps. Some of my teammates argue that it ensures portability, that we can move to newer technologies more readily. Others agree, but say the primary reason is to provide
For the next part of my ASP.NET Core Demystified [https://www.exceptionnotfound.net/tag/asp.net-core-demystified] series, we're sticking with MVC and explaining how the model binding system works. As with all my Demystified series posts, there's a sample project over on GitHub [https://github.com/exceptionnotfound/AspNetCoreModelBindingDemo] which
Let's see how to route URLs to controller actions using both conventions and attributes in ASP.NET Core!
When companies put out ads glorifying workers who willingly sacrifice time for money, who wins? Hint: not you.