Comments on: Debugging file locking in the GAC

By: Alex Angas

Alex Angas — Sun, 20 Feb 2011 00:29:00 +0000

Thanks Ryan, I hadn’t thought about it from the uninstall perspective. That definitely sounds right. Glad to help!

By: Ryan Wheeler

Ryan Wheeler — Fri, 18 Feb 2011 23:37:00 +0000

I’ve posted a question on StackOverflow that may be of interest – http://stackoverflow.com/questions/5047694/sharepoints-owstimer-service-keeping-references-to-feature-receiver-assemblies

By: Ryan

Ryan — Fri, 18 Feb 2011 23:27:00 +0000

Fantastic Alex! This is just haunting me at the moment, damn OWSTIMER!

Minor point – looks like assemblies are moved to c:windowsassemblytemp when Fusion *uninstalls* an assembly from the GAC but its still being used by OWSTIMER – see http://blogs.msdn.com/b/junfeng/archive/2006/11/17/gac-temp-and-tmp.aspx

I’ve verified this with process explorer and a feature receiver. On install OWSTIMER’s handle is to the normal GAC localation but after uninstall its moved to temp.

By: Anders Rask

Anders Rask — Wed, 07 Oct 2009 14:27:14 +0000

Sometimes when assemblies arent upgraded, i find it usefull to delete temporary asp net files:

rd c:windowsmicrosoft .netframeworkv2.xxxxtemporary asp net filesroot /q /s

you need to do an iisreset -timeout:0 before being able to delete the root folder

By: AndersR

AndersR — Wed, 07 Oct 2009 04:57:14 +0000

By: Peter B

Peter B — Mon, 31 Aug 2009 14:49:40 +0000

I was using the very handy Application Pool Manager (http://harbar.net/articles/APM.aspx), but set it to use Warm Up scripts - which can lock a DLL on the W3WP process.