I have a site page that was being deployed within a module that was initially part of one project. I deployed via wsp to my development server and everything was good.

During development I refactored it and moved the page to a different module within a separate project, updated the page and redeployed the wsp to the development server.

Unfortunately for some reason the updated page is not being deployed on development, but instead ignored. I think this is due to the original page being deployed as part of a different feature/module at first and then the same page being moved to a different feature/module.

When I deploy to production the new version of the page gets deployed each time, I believe this is due to the fact that the page was only ever deployed in one feature/module on production.

Has anyone seen this where SP does not deploy a page when it gets moved from one feature/module to another?

Here's what I have in my elements file:

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
    <Module Name="SitePages" Url="SitePages">
        <File Path="SitePages\PASSHome.aspx" Url="PASSHome.aspx" Type="GhostableInLibrary" ReplaceContent="TRUE" IgnoreIfAlreadyExists="TRUE" />
        <File Path="SitePages\WorkflowStats.aspx" Url="WorkflowStats.aspx" Type="GhostableInLibrary" ReplaceContent="TRUE" IgnoreIfAlreadyExists="TRUE" />

2 Answers 2


Did you try adding ReplaceContent="True" to your module XML? Maybe the problem lies in SharePoint ignoring the file as it already exists in the targeted folder.

  • I do have that in my module XML, along with IgnoreIfAlreadyExists="FALSE"
    – verbose
    Feb 25, 2015 at 18:13
  • Sorry I meant IgnoreIfAlreadyExists="TRUE"
    – verbose
    Feb 25, 2015 at 18:22

Deactivate your features and delete the pages. Reactivate the features and they'll be provisioned again.

My rule of thumb was if I was deploying assets, I had feature deactivation code to delete them. This made rapid development deployment possible by right clicking deploy in VS. The feature would retract, delete the deployed assets, be removed form the farm, reinstalled and then activated, thus deploying my updated assets.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

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