materialtest | Hi , its Vivz here from slidenerd | User Interface library

I think this has something to do with color spaces/gamma correction. My guess is that textures loaded via the SKTexture(imageNamed:) initializer aren't properly gamma corrected. You would think this would be documented somewhere, or other people would have noticed, but I can't seem to find anything.

Here's some code to swap with the last image in your linked sample project. I've force unwrapped as much as possible for brevity:

This is not an error with Autofac 5.2.0 and .NET Framework 4.6.2. In the exception it's telling you that the ShipPageObjects.PageObjects.Login.LoginResolvePage is not registered. It's likely that you're injecting it into something that you have registered and you haven't registered the LoginResolvePage.

Autofac is really good at telling you what is failing in these instances. You can either 1 by 1 go through and look at the exceptions and add as it tells you what needs added, or trace your injection back through and make sure everything is registered. I would recommend doing the latter and using the former to finish it up.

I found the answer later in the day, if any one is interested.

The correct syntax would be to create the filter using the Material model such as:

Is it possible to get the XamlWriter to save out the actual StaticResources instead of the resolved references (which it does now)?

No, I am afraid it's not. This is a known limitation of XamlWriter.Save that is documented on MSDN: https://docs.microsoft.com/en-us/dotnet/framework/wpf/advanced/serialization-limitations-of-xamlwriter-save

Common references to objects made by various markup extension formats, such as StaticResource or Binding, will be dereferenced by the serialization process. These were already dereferenced at the time that in-memory objects were created by the application runtime, and the Save logic does not revisit the original XAML to restore such references to the serialized output.