All geek questions in one place

Why does .Net care about assembly?

We had a situation when we had problems with the DLL, which was built in our office, which is located in the Central time zone, and then deployed to a server located on the west coast (Pacific time zone). We are having problems with "UTCDate out of range" when trying to get embedded resources from our DLL (via WebResource.axd). After we discovered this and updated the time of the DLL file to match the time of the web server, everything worked fine.

My question is: why .Net cares about the assembly?

Thanks.

+6
source share
3 answers

This behavior is related to the WebResource.axd caching algorithm .
You can also see a pleasant sensory solution to this problem .

+4
source

I believe the file creation time is used to see if the file needs to be replaced when creating the solution. Other than that, I don’t know.

0
source

If you are building through a network resource, then there are various security issues that .NET takes into account. You might want to learn Security Code Access.

0
source

Source: https://habr.com/ru/post/885754/

More articles:


All Articles