Caching issue in development

This points to a mismatch in the type of object being added to cache vs how it's being gotten from cache. The cache methods are strongly typed now, relying on generic methods for ensuring the same type is added/pulled from cache.

In particular:

// given an object of type nullable LastReadPostInfo...
FourRoads.VerintCommunity.ForumLastPost.Interfaces.LastReadPostInfo? lastReadPostInfo = null;
Telligent.Evolution.Extensibility.Caching.Version1.CacheService.Put("my-key", CacheScope.Process, lastReadPostInfo); ;

// Retrieve from cache with same nullable type
if (Telligent.Evolution.Extensibility.Caching.Version1.CacheService.TryGet<FourRoads.VerintCommunity.ForumLastPost.Interfaces.LastReadPostInfo?>("my-key", CacheScope.Process, out var cachedLastReadPostInfo))
{
    // do something with cachedLastReadPostInfo
}

Incidentally, we're reviewing our options with potentially de-obfuscating portions of logged exception stacks.

It's inside this method, which does what you are doing above, the key is quite complex, but I can't see how that would cause a cast issue

 

public T Get<T>(string key)
{
     CacheService.TryGet<T>(key, CacheScope.All, out T result);

     return result;
}

 

The Get is fine. But it still likely means it's being put in the cache as an Object, not a Nullable<LastReadPostInfo>. 

And as you're specifying CacheScope.All, make sure there's a corresponding IDistributedCacheSerializationProvider Plugin Type .

You are right, I assume as it's a struct it is boxing it and then it breaks

	public void Insert(string key, object value, string[] tags, TimeSpan timeout)
	{
        CacheService.Put(key, CacheScope.All, value, new PutOptions
        {
            ExpiresAfter = timeout,
            Tags = tags ?? Array.Empty<string>()
        });
	}

Tell me more about IDistributedCacheSerializationProvider and it's intent?

Correct. You'd want to use this generic version instead which doesn't box it as an object.

public void Insert<T>(string key, T value, string[] tags, TimeSpan timeout)
{
    CacheService.Put(key, CacheScope.All, value, new PutOptions
    {
        ExpiresAfter = timeout,
        Tags = tags ?? Array.Empty<string>()
    });
}

Robert Nash said:

Tell me more about IDistributedCacheSerializationProvider and it's intent?

Previous versions of caching relied on .NET's binary formatting when serializing/deserializing objects for the distributed cache. Binary formatting was removed as of .NET 9 due to security concerns.

The typical workaround is to use an explicit serialization format instead, JSON, MessagePack, etc.

IDistributedCacheSerializationProvider is a way for a plugin to define how a custom type can be serialized to and from a byte array, and the caching service looks for one if it's asked to serialize a type it doesn't know about for the distributed cache.

It's not required if only caching in-process, since those are just live, non-serialized, objects.

is there not a default platform IDistributedCacheSerializationProvider implimentation ?

There is built in support for all simple types and cacheable API types. But any custom object that needs to be put into cache needs a corresponding IDistributedCacheSerializationProvider.