See the details of every Exception thrown when debugging in Visual Studio
When debugging your .NET application with Visual Studio, you will come along Framework- or Application-Exceptions. In specific cases you see the line where the Exception was thrown (line 132 in the following screenshot) but you cannot see the content (message, stacktrace, etc.) of the Exception. To find this information simple type the following in the watch list area of Visual Studio:
How to keep the IIS Application Pools always awake
When working with “9 to 5” web applications you deal with idle time periods where the users submit few or no requests to specific services of your application. In that cases the first request landing to a service hosted on IIS will take much longer than usual because the service was in sleep mode for better management of resources.
We can avoid this behavior and keep our services in an always-running mode by applying the following three configurations in IIS:
How to use Postman when testing .NET Core WebAPI actions with FromBody and FromForm attributes
Postman requires no introductions and plenty of resources about this tool can be found online. However, while testing I recently noticed, that the binding of JSON objects to C# primitive types or POCO classes is not documented in detail.
We are going to see different scenarios of binding while we test against a .NET WebAPI and try to answer the question “why my action is not getting called when everything is set up in Postman?”.