I have a piece of code such as below:


In the above code, the Task object being passed in came from the 2nd level cache (I verified this by SQL profiling). However, the above code returns false, even though I know for sure, that the passed in task object is a member of this.Tasks. It appears to me, that after enabling the 2nd level cache, the objects retrieved from the cache are treated like "2nd class", which means that code written like above will fail.

Is the above behaviour expected?

Second-level cache gives back copies of objects, it does not do object uniquing, so that might be the problem you're hitting here.

Any suggestions as to how can I deal with this problem?

Basically, the problem I am trying to solve is:

I have some objects that I query by a property (not Id), and I want these to be cached, as these may be used a lot on every single page load.

So, even if the objects are stored in the 2nd level cache, there is no way to Get them out of the cache.

I tried manually putting these objects into cache, but I am getting a behaviour where the cached objects do not appear to be unique. Maybe because they are disconnected from the original session??

Any suggestions?

The easiest way would be to implement Task.Equals and use that instead of == in the method you posted. Then you can enable query caching for the query you use to load the objects by a property, this should also help a bit.