IMagickColor vs. MagickColor

[whugemann]

My console application reads a colour from a config file. Is either a string like "#AABBCCFF" or "auto", in which case my app chooses the colour automatically:

var perfColor = new MagickColor();
if (myColor == "auto")
{
   var onePixel = imgList[0].Clone();
   onePixel.Resize(1, 1);
   onePixel.Modulate((Percentage)100, (Percentage)40, (Percentage)0);
   perfColor = onePixel.GetPixels().First().ToColor() as MagickColor;
}
else
{
   perfColor = new MagickColor(myColor);
}

This codes compiles and works, although the else-path is somewhat crudely initiating perfColor anew.
As one can draw from the code, the result of
onePixel.GetPixels().First().ToColor()
is of type IMagickColor such that I explicity have to convert it to MagickColor.

This duality of ISomething vs. Something appears in many contexts, and I admit that the whole point of it escapes me ... I couldn't find a ready-made explanation anywhere and it's probably due to my lack of understanding of C# concepts. So could you (Dirk) point me into the right direction?

[dlemstra]

If you use IMagickColor instead var you don't need to perform the typecast. The type IMagickColor is an interface that is implemented by the MagickColor class.

p.s. If you have access to GitHub copilot or another generative AI solution you could probably ask those tools for help and information.