SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

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'm trying to deploy a delegate control in the same feature as some custom actions. All the actions are deployed and work correctly. However, the control is not being deployed. If I create a new project with only the delegate control, this works and is deployed right. Is there something I'm missing when mixing controls and custom actions in the same feature?

share|improve this question
can you provide your element.xml file contents.. – Vivek Oct 14 '10 at 2:33

Should work just fine, here is an example from one of our products.


<Feature Id="BD315B60-A1CD-4e64-8537-E4EE3FBFFAB3"
         ReceiverAssembly="Muhimbi.SharePoint.Audit, Version=, Culture=neutral, PublicKeyToken=c9db4759c9eaad12"
         RequireResources = "FALSE"

      <ElementManifest Location="TemplateAssocations\GlobalSiteTemplateStaple.xml" />
      <ElementManifest Location="CustomActions\ElementsShared.xml" />
      <ElementManifest Location="CustomActions\Elements.xml" />


<Elements xmlns="">    
  <!-- Delegate control that is included on every page for tracking audits -->
  <Control Id="AdditionalPageHead"
share|improve this answer
@Muhimbi. I think I'm doing just the same. However, I did not create the project with the custom actions. I'm trying to add my control to that existing project. Is there some configuration about paths or whatever than can be affecting this?? For some reason it just doesn't deploy – omar Oct 14 '10 at 13:57
@Muhimbi. Also, are you guys deploying something else in the same feature. If I do the deployment with only the control, it works. When adding something else is when it breaks. – omar Oct 14 '10 at 17:02
As you can see from the feature definition, we are deploying custom actions in 3 element files. – Muhimbi Oct 14 '10 at 19:39
up vote 0 down vote accepted

After a long time, I found that the error was that the manifest file --that ussually is generated automatically by Visual Studio-- was edited manualy by the person who created the project. So, the new files I added into the solution were excluded from it. I changed back the configuration to maintain the file automatically again and it worked.

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.