CODEWITHSUNDEEP
.net
ExitusLSU
ExitusLSU

Reputation: 81

Why does .Net care when an assembly was built?

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.

Upvotes: 6

Views: 154

Answers (3)

Avram
Avram

Reputation: 4259

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

Upvotes: 4

Erik Funkenbusch
Erik Funkenbusch

Reputation: 93424

If you are executing the assemblies over a network share, then there are various security issues that .NET takes into account. You might want to look into Code Access Security

Upvotes: 0

m4tt1mus
m4tt1mus

Reputation: 1641

I believe the time the file was created is used to see if the file needs to be replaced when building a solution. Other than that I don't know.

Upvotes: 0

Related Questions