How to detect if cached composition data is obsolete?

Let’s say my main assembly has version 1.0.1.0. I serialize its composition data to disk:

await cacheManager.SaveAsync(configuration, stream);

Then I update my assembly version to 1.0.2.0. Finally, I successfully (and a bit unexpectedly) deserialize the composition data from the previously saved cache:

var epf = await cacheManager.LoadExportProviderFactoryAsync(stream, resolver);

I expected this to fail, since the version has changed. Viewing the serialized data, I can see the old version number lurking around. Running the application seems to work, but I guess there could have been a problem if the dependencies had changed.

Not sure how to interpret these findings. What is the expected behavior, and why?

More importantly, is it possible to detect if a serialized cache is obsolete?

[znakeeye]

Thanks. I decided to serialize the scanned assembly timestamps together with the graph data. If the timestamps differs, the cache is invalidated.

[AArnott]

I agree. But the cache should be built on every build, so if the developer adds an Export, on the very next test run or debug launch they’ll be running with the new cache.