I didn't mean to leave both of checks there. Thanks for pointing out it.

My preference would be to leave it in the property, just in case we would use ExpiresOn somewhere else, but I know that is unlikely.

Christophe Gijbels <notifications@github.com> wrote:
>> @@ -65,31 +80,27 @@ private bool TryGetCacheItemModel(DictionaryEntry
>currentCacheEntry, out CacheIt
>>  
>>              cacheItemModel.Key = currentCacheEntry.Key.ToString();
>>              cacheItemModel.Value =
>Serialization.GetValueSafe(currentCacheEntry.Value);
>> -
>> -            if (TypeCacheEntity == null)
>> +            cacheItemModel.CreatedOn =
>GetCacheProperty(ProcessInfoUtcCreated, cacheEntry) as DateTime?;
>> +            cacheItemModel.ExpiresOn =
>GetCacheProperty(ProcessInfoUtcExpires, cacheEntry) as DateTime?;
>> +            if (cacheItemModel.ExpiresOn == DateTime.MaxValue)
>
>This check will always return `false` because the property `ExpiresOn`
>does the same check and returns null :wink: 
>Maybe it is better to remove that check code from the property and
>leave the code here, which seems more appropriate. What do you think?
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/Glimpse/Glimpse/pull/672/files#r8309653