Why does .Net care when an assembly was built?

Question

We had a situation where we were having issues with a DLL that was build in our office which is located in the Central time zone and then deployed onto a server located on the west coast (Pacific time zone). We'd have issues with "UTCDate out of range" when trying to retrieve embedded resources from our DLL (via WebResource.axd). Once we discovered this and updated the DLL's file time to match the web server's time, everything worked fine.

My question is: Why does .Net care when an assembly was built?

Thanks.

Answer 1

This behavior connected to WebResource.axd caching algorithm.
Also you can look at nice touch solution of this problem.