Home/ Questions/Q 627429
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T19:31:39+00:00

I’ve been given the task of content migration from another CMS system to SharePoint

  • 0

I’ve been given the task of content migration from another CMS system to SharePoint 2010.

The data in the old system is fairly easy to capture and the page hierarchy is simple so I’m not worried about that.

However, I am completely flummoxed about how to even create a page in code. I’m using the Microsoft.SharePoint.Client namespace as I do not have sharepoint installed on my system and am wanting to code this up as a console application and so I’m using I’m using ClientContext. (On the other hand, I am willing to go into other solutions if necessary).

My end-game: To get a page uploaded into some folder hierarchy which uses a master page, has the page title in a header web part, and a big ol’ content-editable web part in the body so any user can come along and edit the content.

Things I’ve tried so far:

  • Using FileCollection.Add() to add an aspx file to the folder “Site Pages”. This renders the html in the browser but doesn’t enable any features for the user to edit the page
  • Using ListItemCollection.Add() to add a page to the site, but I didn’t know what fields I needed. Also I remember it came up with a runtime error saying I should use FileCollection.Add()
  • Uploading to ‘Site Pages’ instead of ‘Pages’
  • So many others… ow my head 🙁

The only plausible thing I can see on the net is to use the PublishingPage type along with PublishingWeb. However, PublishingWeb can only be constructed from an SPWeb object which requires me to be actually hosting the sharepoint application on my workstation.

If anyone can lend a hand that would be greatly appreciated 🙂

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I don’t see a way of creating a publishing page without the actual publishing methods.

    When you create a new article page it will only create a few xml parameters inside the page, the layout itself lives in the /_catalogs/masterpage/article-XXXX.aspx file.

    You can try downloading a native file created in the Pages document library, understand its structure, fill the XML with your data and then uploading it back to the Pages document library using the FileCollection — that’s my only guess.

    Edit: sample Article Page

    <%@ Page Inherits="Microsoft.SharePoint.Publishing.TemplateRedirectionPage,Microsoft.SharePoint.Publishing,Version=12.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c" %>
<%@ Reference VirtualPath="~TemplatePageUrl" %> 
<%@ Reference VirtualPath="~masterurl/custom.master" %>
<html xmlns:mso="urn:schemas-microsoft-com:office:office" xmlns:msdt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882"><head>
&nbsp;<!--[if gte mso 9]><xml>
<mso:CustomDocumentProperties>
<mso:PublishingContact msdt:dt="string">1073741823</mso:PublishingContact>
<mso:display_urn_x003a_schemas-microsoft-com_x003a_office_x003a_office_x0023_PublishingContact msdt:dt="string">System Account</mso:display_urn_x003a_schemas-microsoft-com_x003a_office_x003a_office_x0023_PublishingContact>
<mso:PublishingContactPicture msdt:dt="string"></mso:PublishingContactPicture>
<mso:PublishingContactName msdt:dt="string"></mso:PublishingContactName>
<mso:ContentTypeId msdt:dt="string">0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF390078FB5FE740F6714B9595501175ECD8F000727044016EAB3B45B9E104498E366C85</mso:ContentTypeId>
<mso:Comments msdt:dt="string"></mso:Comments>
<mso:PublishingContactEmail msdt:dt="string"></mso:PublishingContactEmail>
<mso:PublishingPageLayout msdt:dt="string">http://dmserver008/_catalogs/masterpage/ArticlePage.aspx, EstudoAndre</mso:PublishingPageLayout>
</mso:CustomDocumentProperties>
</xml><![endif]--><title>New Article</title></head>

    To grab one, hit the Pages library => Content Menu => Send To => Download a Copy

    • 0