All geek questions in one place

What happens in the assembly purgatory?

When the .NET assembly is deployed to the GAC and the target file is locked, Windows keeps it in what I can best guess, this is a kind of "clean up assembly" - c:\windows\assembly\temp.

Using Process Explorer, this can be easily seen when looking for a suspicious DLL:

Search in the process explorer http://alexangas.com/blog/wp-content/uploads/2009/07/peasmlist.png

Once I complete the file locking process (in this case OWSTIMER.EXE), it is magically deployed to the GAC correctly.

I'm curious what Windows actually does. How does he know when a file lock was locked? Where does it keep a record of locked files? Did he ever give up?

+3
source share
1 answer

Tempand tmp- temporary folders used when installing and removing the GAC assembly. tmpused for installation, and Tempused for removal. Source: GAC Temp and Tmp

The .NET ( mscorsvw.exe) runtime optimization service probably checks the files from time to time to see if they are closed, in order to [un] install pending assemblies.

, , , , WinAPI , /. . Windows - ( , ), , , , , .

+1

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

More articles:


All Articles