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 have a standard WSP package with a single assembly that is deployed to the GAC.

We have 2 versions of packages, both with the same assembly version and assembly file version.

Version 1 installs fine, deploying the assembly to gac.

Version 2 installs fine in test, however in production the assembly is not actually being deployed to the GAC on any of the WFE servers.

The ULS Logs contains the event saying "Deploying MyAssembly.dll to the GAC" but it never does. When I redeploy the version 1 solution to production, it deploys to the GAC fine.

I have confirmed that when the package is removed the assembly is correctly removed from the global assembly cache.

Has anyone come across something like this before, what could be preventing our assembly from being deployed to the GAC?

Any help is much appreciated! Thanks :)

share|improve this question
up vote 1 down vote accepted

We eventually concluded that there must have been a reference between the two assemblies or this could not have happened. We redeployed both WSP packages again and it is working sweet.

Lessons learnt were to formalise and test deployment processes, and to more vigilantly use labels and tags in source control to identify versions.

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.