There's a new testing framework in town. Here's how to use it.
There's a new kid in the Visual Studio testing environment, though it's only for your .NET Core projects. You don't have to use it, but here are some reasons you'll want to.
If someone tells you that LINQ doesn't support subqueries ... well, they're not wrong. But they're also not entirely correct, either. With LINQ you can meet many of the goals of SQL subqueries including the ability to build complex queries out of simpler ones.
ASP.NET Web API and ASP.NET MVC have similar (but not identical) mechanisms that allow you to customize how your requests and responses are processed. Not surprisingly, ASP.NET Web API's implementation is both easier and more flexible than ASP.NET MVC.
You have at least two options for adding processing to multiple controllers without duplicating code in each of the Controllers.
If screaming speed in data access is the most important thing in your life, SQL Server's durable in-memory, memory-optimized tables are your answer. They were good in SQL Server 2014 and they're even better in SQL Server 2016, 2017 and Azure.
If, in your "need for speed," you're looking to access and update your data as fast as possible, you can get to that goal by combining memory-optimized tables with compiled procs.
You have a bunch of options for debugging Android applications built with Xamarin. Unfortunately, only one of them has worked well for Peter in all scenarios. Here are all your options with Peter's opinion on each and a recommendation on the best one.
You're not a DBA but you're responsible for managing your organization's SQL Server installation. Here are some tips on what you can do to speed up all your data access.
The OpenAPI (Swagger) technology suite includes a file that describes your Web API service. Peter thinks it's the slickest tool available to ensure that clients can access your services.
If you want to speed up your SQL Server queries you need to know how your application and your users actually use your database.
There are five design patterns you'll use every time you create a smartphone application. One is imposed by the environment and one is a pattern that you've probably been avoiding when creating other kinds of applications.
That understanding should drive how you deal with testing, including how to turn it into a value-added task.
If you want to impress your boss (or client) with your diligence in generating documentation for your Web Service, then you need Swagger. That it will also make it easier for you to run tests on your service and check for typical errors is just icing on the cake.
Testing is a necessary but not a value-added task. To put it another way, while testing is something we have to do, our users would be just as happy if we could produce quality software without it. Understanding that leads to a realistic approach to testing.