Posts

Download full source code. Want to learn more about Polly? Check out my Pluralsight course on it. In my previous post “A simple Polly example with WebApi 2” I showed how to make a request to an unreliable endpoint protected by a Polly retry policy.

Download full source code. Want to learn more about Polly? Check out my Pluralsight course on it. If you are calling APIs and you haven’t heard about The Polly Project, you should check it out.

Download full source code. When building a Web Api 2 application there is much unneeded MVC baggage that comes along with it. To start with all the css, html and javascript can go, then most of the packages, most of referenced dlls and almost all the C#.

Download full source code At first you think it’s going to be easy to download a file from Web Api, but as I discovered, it was not. In my case I wanted to load data from the database, perform some processing and return a subset of the data as a file.

I have two other posts on multiple GET methods, one for ASP.NET 5 Web Api, and another for Web Api 2. Download full source code. A few months ago I wrote a post explaining how to create a controller with multiple GET methods.

Full source code here. I wrote blog post in 2015 on using the Fluent Validation NuGet package for complex validation needs. In the post the validator checked that a create person request had at least one active primary phone and at least one active primary email.

I have two other posts on multiple GET methods, one for ASP.NET 5 Web Api, and another for Web Api 2. It seems that every version of Web API changes how it handles default routes or route prefixes or whatever the next name will be.

Edit - even though the steps described below related to an example with IIS, you can use this technique for any running process, it’s just a matter of identifying the process id.

Using Entity Framework I occasionally get the following error when reading from the database - `exceptionMessage=Value cannot be null. Parameter name: constructor` My Person class looked like this - 1 public class Person 2 { 3 public Person(string firstname, string lastname) 4 { 5 Firstname = firstname; 6 Lastname = lastname; 7 } 8 9 public Guid PersonId { get; set; } 10 public string Firstname { get; set; } 11 public string Lastname { get; set; } 12 public DateTime SomeDate { get; set; } 13 } There is no way for Entity Framework to know how to instantiate this object because there is no empty constructor.

Download full source code here. I thought this would be easy, there is a method called ExecuteSqlCommand which takes the stored proc name and an array of parameters. I wanted to pass in two parameters and get one back, no problem, I’ve done this with ADO.