Moving Files From Development Server To Production Server Using Office SharePoint Designer 2007 - SharePoint Buzz - Your SharePoint Community Resource

SharePoint Buzz on Twitter

    sptechcon 2010


    Moving Files From Development Server To Production Server Using Office SharePoint Designer 2007 

    Need a good tutorial on how to move files from development server (master pages, page layouts, cascading style sheets, JavaScript, etc.) using Office SharePoint Designer 2007 to production (or any other environment), well Andrew Connell has a post just for that. Here's a preview of his post: When you create files in your Publishing site (aka: WCM site) in a development environment, the files are stored within the site's content database, not on the file system. We call these types of pages "customized" (WSS v2 folk know this as "unghosted"). While this is fine and good for development, you're going to have some challenges in a real MOSS environment where you'll have developers working on developer machines, a shared development environment (aka: build server), a test environment and a production environment. Why? Because you will only get those files in the content database into the different environments in one of two ways... Well written, don't you think? We think its good enough for posting on Sharepoint BUZZ. Need further proof, Andrew goes further to point out few advantages that using features with Office Sharepoint Designer 2007 has over the two methods described in his post:
    • Ability to leverage a rich source control management solution: Because everything is now on the file system, this is no different than your non-SharePoint ASP.NET 2.0 Web projects, or class libraries, etc... they are just files on the file system so you can easily add them to your source control management system of choice! This is HUGE!
    • Ability to package up the feature (and all it's files) in a SharePoint solution: See where I'm going? If you package up your feature and it's files into a SharePoint solution file (*.WSP) which you can then use to...
    • Deploy to all SharePoint web front end (WFE) servers in your farm at one time: Solution deployment can be scheduled to run at a future time... and the best part: SharePoint's solution framework will automatically deploy the feature to ~all~ your WFE's in the farm at that time. But that's not the only advantage of solutions
    • (list continues ... )
    Definitely a worthy read, click here to go to the post.
     
    Posted on 21-Dec-06 by Kanwal Khipple
    0 Comments  |  Trackback Url  |  Link to this post | Bookmark this post with:        
    Tags:
     

    Links to this post

    Comments

    Name:
    URL:
    Email:
    Comments: