Skip to main content

ASP.NET Core Implicit Cast

While doing a code review I noticed the following code inside an ASP.NET(Core) controller:

// GET api/products
[HttpGet]
public ActionResult<IEnumerable<Product>> Get()
{
_logger.LogInformation("Getting all products");
using (var uow = _unitOfWorkFactory.Create())
{
var products = _repository.GetProducts();
return products;
}
}
view raw GetProducts.cs hosted with ❤ by GitHub
public interface IProductRepository: IRepository<Product>
{
List<Product> GetProducts();
}

Do you notice something special?

No? Let’s give you a hint. Take a look at the return type; ActionResult<IEnumerable<Product>> and then take a look at the type that is actually returned; List<Product>. Although both types don’t match this code compiles and runs perfectly.

What is the magic happening that is happening here? This all works thanks to the fact the ActionResult<T> type supports implicit casting.

Now what happens if we update the code to the following:

[HttpGet]
public ActionResult<IEnumerable<Product>> Get()
{
_logger.LogInformation("Getting all products");
using (var uow = _unitOfWorkFactory.Create())
{
var products = _repository
.GetProducts()
.Where(p=> p.Discontinued=false);
return products;
}
}
public interface IProductRepository: IRepository<Product>
{
List<Product> GetProducts();
}
view raw gistfile1.txt hosted with ❤ by GitHub

This time you get a compiler exception:

Cannot implicitly convert type 'System.Collections.Generic.IEnumerable<eShopExample.Product>' to 'Microsoft.AspNetCore.Mvc.ActionResult<System.Collections.Generic.IEnumerable<eShopExample.Product>>'

Whoops! Why this no longer works?

The reason is that where before we were returning a concrete type (List<T>), now we are returning an interface (IEnumerable<T>). C# doesn't support implicit cast operators on interfaces.

To fix this we can add a ToList() to convert the interface to a concrete type.

Popular posts from this blog

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...