.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

In real time how Sharepoint site is deployed from Development to Production?

Posted By:      Posted Date: September 15, 2010    Points: 0   Category :SharePoint
in our company we are directly working on Production site so we never got scenario to deploy Site to Production Server , so i want to know the procedure to deploy SP site to production Server. in real time do they use any tool to deploy? kindly provide information on this.

View Complete Post

More Related Resource Links

Deploying Publishing SharePoint site from development to test and production environment.




I have created a Publishing Site in SharePoint 2010, with pages created from custom page layouts, content types and Publish Content areas which I have created using SharePoint Designer 2010.

Also, I created custom Lists, Libraries and workflows in my development environment.

I want to replicate the site in test/production environment.

Can you please suggest me the best way to package all, along with custom site settings from development environment so that I can migrate small changes to test/ production environment later also without creating .wsp as I have access to SharePoint designer 2010 only.

Abhijit Sil

Chapter 4: Branding Your SharePoint Site (Professional Microsoft SharePoint 2007 Development Using M

Learn how to create your own custom site pages and insert Silverlight content into these pages, customize SharePoint lists and views, and insert Silverlight content into existing list views and custom views.

Development and Production Server software information for Sharepoint 2010 ??

Need to ask my IT Team to get me softwares for Development machines to write code / develop sites which we can give to end customers for deploying in their Sp2010 Production farm . W.r.t to that i have following questions : For Development , a) Which Windows Server 2008 OS version is sufficient - Standard , Enterprise , R2 ? b) Which SQL Server Version is sufficient ? c) Which VIsual studio version ? d) Which Sp2010 license version ?   From Production environment perspective , have following questions - a) What should be a recommendation to client for Production Server - Widows 2008Server sp2 or R2 ? SQL Server 2008 Server Sp2 or R2 ? Which is better and why ?  

Migrating changes from the Development to Production Site (SP2010, SPD and Visual Studio 2010)

Trying to find the best (least error-prone) approach to updating a live site containing content (based Documents and Tasks mainly) with changes. This got to be a common issue - a Development environment containing new features needs to be migrated over to production but the existing data and workflows with the associated tasks should be preserved. I found this thread http://social.msdn.microsoft.com/forums/en-us/sharepointdevelopment/thread/2C524797-9737-4D11-BE19-3E407C5C83CE which seems to provide a rather negative take on a tool-based approach but it's for older Sharepoint. Anything improved since then?

SharePoint how does it know to use a feature default.aspx deployed instead of site definition defaul

I have created a feature which deploys a custom default.aspx page. The deployed file goes to the template\features{featureName} directory. How does SharePoint know to use this default.aspx page instead of the one that is located in SiteTemplates{Site Def name} directory?dave

Best way to update a Sharepoint 2007 custom list schema after it has been deployed to production


What is the best way to update a Sharepoint 2007 custom list schema file (that is deployed using a feature) after the list has been deployed to production.


Scenario: We have custom list based on a custom list definition and template that we have deployed to production. Users have added items to this list and also added their own new columns to this list apart from what we originally included. Now I want to update this list schema (add another custom column). Whats the best way to achieve that?

Also, a related question is that if a new <field> entry is added to an already deployed schema file, will pushing the new schema file to the right place be enough or will a feature deactivation/activation also be required? I have noticed that some changes to schema files are picked up without the need to deactivate/activate the feature. But whats the general practice for scenarios like this?

Sharepoint site getting time period expired



I am having a file which is contain 70,000 data. i try to upload this file into sql server table using front end sharepoint site.i am getting time out period expired error.

But i have added connection timeout=100000 property in connection string still i am facing the same problem

So please help me to solve this issue



Having Problems creating a development copy of a fairly complex live site, sharepoint 2007


Hi All,

I have inherited a sharepoint distribution from a previous set of contractors, which I am now trying to set up for a developer hired to fix a few bugs in custom code.
This sharepoint installation consists of a farm that includes the following: - Not Configured - Windows Sharepoint Services Incoming E-Mail, Windows Sharepoint  Services Web Application - Central Administration / Excel Calculation Services / Office Sharepoint Server Search / WSS Incoming email / WSS Web App - Office Sharepoint Server Search / WSS Incoming email / WSS web app

SQLCluster - WSS Database

I have a development machine with a single install of sharepoint / mssql 2005 that I would like to set up as a test server for code/database changes

I set out thus to export (stsadm -o export etc.) a copy of the live site, and import it into my test server. This gave me a lot of errors regarding features, which I looked up to be custom solutions that were not installed, so I installed those, and attempted the import again, this time another error regarding features missing. I checked the features/template directory and noticed on live there are a few features that are not listed in the solutions panel, these look to be mostly custom webparts

Site or Site Collection backup for first time Production deployment



I want to know if there is any issue using Site or Site Collection backup for first time Production deployment for either collaboration/Publishining site.



Changing the graphics on the home page of a SharePoint site

When you create a site in Microsoft Windows SharePoint Services by using the default Team Site template, the home page includes two default graphics. A Windows SharePoint Services graphic appears in the body of the page, and a picture of a house in a circle appears near the site title. You can change these graphics to customize your site. Changing the smaller graphic requires a Windows SharePoint Services compatible Web page editor

Take a tour of your SharePoint site

What is a SharePoint site for?
A SharePoint site is a Web site that provides a central storage and collaboration space for documents, information, and ideas. A SharePoint site is a tool for collaboration, just like a telephone is a tool for communication, or a meeting is a tool for decision making. A SharePoint site helps groups of people (whether work teams or social groups) share information and work together. For example, a SharePoint site can help you:

Coordinate projects, calendars, and schedules.
Discuss ideas and review documents or proposals.
Share information and keep in touch with other people.

Six easy ways to customize your site using Web Parts in SharePoint

Becoming familiar with Web Part customization techniques gives you a range of page-customization choices. For example, you can customize your site's home page so that it displays the specific information that your team needs. You can rearrange the list items on the home page, add lists, and even change the images on the home page. As you become more familiar with Web Part Page customization techniques, you can build interactive Web Part Pages that makes the data in lists more dynamic and useful, and you can add new Web Parts that provide access to external data and Web services.

SharePoint Application and Site Pages - Part 1 of 2

In this first part of the two part series, Steven covers the differences between Site and Application pages in SharePoint 2007, why each may be used in various circumstances, and prepares for the construction of a menu located application page. After a brief introduction he examines the concept of Site Pages and Application Pages separately in detail with supported screenshots.

SharePoint Application and Site Pages - Part 2 of 2

As the second article in a two part series, Steven examines the attributes and details of a SharePoint 2007 application page, including the construction and feature deployment of the same page based project. Since this is a WSS level objective, as opposed to MOSS, you will not need MOSS to work with the code included in this project. Windows Server 2003, WSS, and Visual Studio 2005 are all that is needed, with no additional add-ons. He provides a detailed analysis of each step involved in the creation and deployment of the project.

Easier Silverlight Development against SharePoint

I have been spending quite a bit of time lately working with Silverlight 3 and SharePoint. One of the first big shifts for me is that Silverlight Development is Client development. Silverlight runs in the browser, but it runs on the client, so no SharePoint Object Model code. You have to access all of the goodness that is SharePoint through its web services.

First Look: Visual Studio 2010 Tools for SharePoint Development


This article provides a first look at tools in Visual Studio 2010 designed to support development and deployment of SharePoint 2010 solutions. The article provides an example of designing and deploying a visual Web part.

Steve Fox

MSDN Magazine October 2009

Office Space: Automated SharePoint Site Branding


Here's a custom branding solution for SharePoint sites that integrates Master Pages and CSS files at the level of the site collection.

Ted Pattison

MSDN Magazine July 2008

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend