James Turner

Yeah - so that bit of magic, the numeric values match up for the attributes I had defined so it _shouldn't_ be switch but yeah, you're seeing it so it...

`ManifestEntry` is used for the file cache layer - that shouldn't be impacting what we're seeing here.

Yeah, I'm puzzled too. What you described as a workaround sounds plausible but it sucks that you need to do that.

There is a bump in protobuf versions between 0.11.x to latest - may have been a bug introduced there? Previous: https://www.nuget.org/packages/CacheTower.Providers.Redis/0.11.3#dependencies-body-tab Latest: https://www.nuget.org/packages/CacheTower.Serializers.Protobuf/#dependencies-body-tab

 :(

This is with a slightly newer version of the Protobuf library (so I haven't isolated whether it is a bug there or in my code) but this works: 

> Next thing I would quickly check is if you define the RuntimeTypeConfig specifically with `CacheEntry` rather than the open-generic workaround. Then we have reduced it to it's simplest form?...


Oh, one thing with the test that I through together is wrong - `CacheEntry` will truncate an expiry down to the second so it may have given a false positive....

It is the missing `set` on the property that is breaking it...