Sharepoint timer jobs, GAC and development

by Martin 27. maj 2009 11:16

I've been developing a feature that contains a list, a webpart (a customized CQWP) to display the contents of the list and a timerjob. For the last part (the timerjob) I create an assembly, which deploys to the GAC. This is all swell untill the point where I'm no longer satisfied with functionality of the dll and change the code. Redeploying to GAC, upgrading solution, nothing helps... :( Even resetting the IIS!! The dll still stays in the GAC cache. It appears to be removed from the GAC when reinstalling, but the functionality is still that of the old code...

What to do is, that you have to use gacutil. One simple command: "gacutil.exe -cdl".
After this I recommend you you delete your temporary ASP.NET files. For me, running a Windows 2k8 64-bit this is done by running this command: 'rmdir "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files" /s /q'.
This might be troublesome if your apppool still has handles in the GAC, so you might need to recycle your apppools before issuing the last command, or, sometimes even better yet, run an IISRESET.

My co-worker Ulrich pointed me to an interesting post which led to above solution: http://social.msdn.microsoft.com/Forums/en-US/clr/thread/4bdd28d0-af2b-4ddf-bf9c-efaeee023139

EDIT 090722: If the above still doesn't seem to do the trick, try to restart the "Windows SharePoint Services Timer" in Services. Then you might be good to go

Tags: , , , ,

MOSS

Tilføj kommentar

  Country flag

biuquote
  • Kommentar
  • Eksempel
Loading

Page List

About

Take a look at my LinkedIn-profile.

DISCALIMER: The content on this blog is in NO way affiliated with my employer. The opinions expressed on this blog are solely my own and in NO way endorsed by my employer.

Recent comments

Comment RSS

Month List