SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am working on a big SharePoint project. We have 4 solutions with around 40 projects. So in my development environment, when ever I am deploying a modified project, I am not sure whether the newly deployed code is working or not. Sometimes the dll is new but while debugging I am able to see the existing code. For timer jobs we have an option to clear the cache. Is there any way to clear the cache or get a new dll properly every time to run.

share|improve this question
up vote 1 down vote accepted

I have a link that explains in full on the cashing and how to clear them, I use stsadm and sometime wspbuilder has that option too whats nice and easy when deploying or upgrading.

At my work we develop on VPC make it good and working then we test on dev server - then test on int server and then I would upload it to SVN as a working copy. From that anyone else can take it from SVN (obviously update ;) ) and do the same process :)

Also for webparts you can try WSPBuilder! its a good tool that builds and deploys wsp from Visual studios. You can even recycle AppPools and Recycle Services Timer.

share|improve this answer

I have experienced the same many number of times. Deactivating and then activating the feature refreshes the solution. You can use the powershell command to deactivate/activate the feature.

Disable-SPFeature –Identity Featurefoldername –url http://yoursite

Enable-SPFeature –Identity Featurefoldername –url http://yoursite

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.