Moving a Site Collection to Its Own Content DB in SharePoint 2013

Moving a Site Collection to Its Own Content DB in SharePoint 2013

I wanted to move a site collection to its own content DB and not have any other site collections added. This was for migration purposes but eventually the new content DB will be used for other sites.

The first step to create a new empty content database. Therefore from Central Admin, under Application Management, select Manage content databases in the Databases section:

On the Content Databases page, click on the Add a content database link:

 

 

 

 

On the New Content Database page, enter the new database name and click OK:

Back on the Content Databases screen, click the link of the new content database you created. The Manage Content Database Settings page appears. Change the Database status to Offline:

 

This is such that nobody can add new site collections and have them stored in your new content database. Click OK.

Next, on the server, open SharePoint 2013 Management Shell and issue the following statement:

          Move-SPSite <<http://server/sites/SiteCollection>> -DestinationDatabase <<NewContentDBName>>

 

Run IISReset per the message.

 

Refresh your Content Databases screen and you should see 1 site collection in your new content database, and 1 less in the original content database:



Reference

http://stevemannspath.blogspot.in/2013/03/sharepoint-2013-moving-site-collection.html

Create Site Collection in a Specific Content Database

Create Site Collection in a Specific Content Database

Whenever we create site collection by default it will get stored in a content database which you all know.

But in some scenarios we need sitecollection to be stored in a specific content database. Why? What is reason for storing the site collection in a separate or a specific content database?.

To answer the above question, we need to know that one web application can support multiple content databases and you can store only 200GB of content in one content database. Please see the Software boundary limits for SharePoint 2013.

In real world scenarios you will have to store or create sitecollection into a separate content Database. For example if you have a large number of team sites which may increase in numbers and leads to the size in future to 500GB to 1TB or even more. So you need to create additional content databases for a particular web application.

Example: If you are building portal for a customer and his company have different departments like Finance, marketing, Sales etc. Where you need to store more amount data, in those cases you need to create multiple content databases in a single web application.

Try to use below naming conventions to maintain the databases in a long term prospective for SQL guys who are maintaining your SharePoint databases.

For finance team "Finance_Team_site_Content_Database" , for marketing "Marketing_Team_site_Content_Database" and for Sales "Sales_Team_site_Content_Database" etc.

To achieve our goal perform below steps.

Step 1: Add content Database to web application:

From Central administration screen and under "Application Management" click on Manage Content Databases”.

Click on "Add a Content database".

For example enter Database Name as "Finance_Team_site_Content_Database" under "Database Name and Authentication section" in "Add a Content database" section, leave remaining fields as it is and click ok.

The field Database Capacity Settings can be used, if you want to limit how many sitecollections you can create in a particular content database and give a warning message to the end user while creating the content database.

Please see the below Figure :Add Content Database to add the content database.

Figure:Add Content Database

For each content Database you add from central administration it will create a database in SQL server.

You can check if you have access to it or ask your SQL DBA if it’s managed environment, if it is a local VM then its up to you :) you can test whatever you want.

Add few more content databases for testing. I have added four content databases here. "Finance_Team_site_Content_Database", "Marketing_Team_site_Content_Database", "Sales_Team_site_Content_Database" and "SharePoint_Journey_2013_Content_Database".

If i create a new site collection from the central administration screen I want to store or create site collection need to store in a particular Content Database, this is our goal correct.

Let’s say I want one Team site template sitecollection for SharePoint-Journey Sales, when I create a site collection with the name of SharePoint-Journey sales it has to store in "Sales_Team_site_Content_Database" content Database.

You can see Database status field in the Figure: Content Databases List shows as started for all the databases.

Figure: Content Databases List

Step 2: Manage Content database settings:

Before creating sitecollection you have to change the status of each content database status to stopped and only required content database should show started. In our example "Sales_Team_site_Content_Database" content database should be started.

See the below Figure:Database settings , click on all Database names and change Database status from ready to offline except "Sales_Team_site_Content_Database" and click ok.

Figure:Database settings
You can see the Figure : Content Databases where only one database status is Started all other remaining are in Stopped status and oberve the "Current number of site collections" against the "Sales_Team_site_Content_Database" is zero.

Figure :Content Databases

Step 3: Create sitecollection:

In the final step we will create sitecollection and try to find in which Content Database it will get stored.

Please use post on how to create a sitecollection in SharePoint 2013. After creating a site collection go to manage Content Databases under Application management section, you can see that "Current number of site collections” is showing "1" against "Sales_Team_site_Content_Database" content Database. See the below Figure. Content Databases

Figure.Content Databases.

After completion of above steps don’t forget to change the other databases settings to Ready i.e. started. To change the status click on Database name and change Database status from offline to ready and click ok. Repeat this step for all the Content databases those are offline.

Congratulation you have completed all the required steps.

Before concluding the topic, one question here is what will happen if you change the status from Ready to offline?.

The answer is during offline You can open the sites in that particular content database but write operation are not possible.

- See more at: http://www.sharepoint-journey.com/create-sitecollection-specific-content-database.html#sthash.AQFFqSAa.dpuf

Reference

http://www.sharepoint-journey.com/create-sitecollection-specific-content-database.html

Create Custom Master Page in SharePoint Designer 2010 step by step

Create Custom  Master Page in SharePoint Designer 2010  step by step

1 Create Web Application

Create a web application where we will make some modifications. Choose any name for it, and be sure that it works correctly. I created mine in my test environment http://master.Spdev.local:888

You don’t have to fill this page with any data or document since we will only change the style of this page.

2 SharePoint Designer

SharePoint Designer is used for the management of SharePoint sites and lists, for creating and managing internal and external data sources, creating views and forms to work with data, creating workflows in order to represent business processes and finally SharePoint Designer is used for branding sites by customizing the look feel.

SharePoint Designer 2010 can be downloaded for free from Microsoft while SharePoint Designer 2007 wasn’t free of charge at the release of SharePoint 2007 which changed during time. While SharePoint Designer 2007 offered you the ability to edit SharePoint and non-SharePoint sites this has changed with the version published in 2010: You can only edit SharePoint 2010 sites using SharePoint Designer 2010.

SharePoint Designer 2010 is available in a 32bit and a 64bit version. If you intend to use SharePoint Designer 2007 besides the 2010 version you need to install the 32bit version of SharePoint Designer 2010.

One major complaint with the 2007 version was the difficult lockdown of SharePoint Designer 2007 which has changed with SharePoint Designer 2010: You can now easily manage the capabilities at the web application or site collection level.

2.1 SharePoint Designer 2010 download

Here are the downloads including Service Pack 1:

• Download: Microsoft SharePoint Designer 2010 (32-bit)
• Download: Microsoft SharePoint Designer 2010 (64-bit)
• Download: Service Pack 1 for SharePoint Designer 2010 (32-bit)
• Download: Service Pack 1 for SharePoint Designer 2010 (64-bit)
• Download: Product Information SharePoint Designer 2010

3 Install SharePoint Designer

The first step in this process of course, is to get SharePoint Designer installed. To do so, I am starting from the first site I have created in my new environment.

Since I do not already have Designer 2010 installed, a dialog window pops up, basically letting me know that I do not have it installed, and I can do so. Just like SharePoint Designer 2007, SharePoint Designer 2010 will be free for all users. And since the Beta is all that is around now, that’s what it will install for me

I select the language I want to install SharePoint Designer in (German, Spanish, Japanese, French, Russian, and Chinese are other available languages that can be selected, in addition to English, as shown above), and choose my platform. Even though SharePoint 2010 is only 64-bit, SharePoint Designer 2010 is available in both 32 and 64 bit, as it is intended to be run from the desktop, and many of us still run 32 bit desktops, as we probably will for a long time to come.

Once done, selecting the Download button goes out and fetches the right download, and prompts me to run and/or save it.

It’s sizeable for my options as I've chosen (English 64-bit) at 277MB, so I'm happy that I have a nice and fast connection.

Once it’s up and running, the installer will extract the files, and then move on.

You have the usual EulA; agree and continue

Once accepted, you really cannot miss what is needed on the next screen. Microsoft made sure of that.

However, you can customize your installation by clicking on the Customize button, setting a new installation directory, setting your user information, and adding or removing features from the install. With the default installation, it’s a fairly hefty installation at 1.03G, but, I have a feeling it will be well worth it…

The installation begins (of course after you have clicked the Install Now button). And that’s it. You’re done!

4 Basic Designs

4.1 Active features

Where do you set the master page / page layouts if you create a Team Site / non publishing site collection? Well, Microsoft obviously knew that people would want to use the publishing features with the non-publishing enabled site collections, so this is an example of where the feature framework really works well. To resolve the “problem” simply complete the following steps:

• Navigate to the landing page of your newly created site collection
• Click on “Site Actions”
• Click on “Site Collection Features”
• Enable “SharePoint Server Publishing Infrastructure”

Enable on site collection level

• Click on “Site Actions”
• Click on “Manage site features”
• Enable “SharePoint Server Publishing”

Enable on a site level

Once completed, you can again access the master pages and page layouts via site settings as you would normally do for a publishing portal.

4.2 Leave Default Master Pages in Peace

SharePoint 2010 comes with three out-of-box Master Pages – v4.master (the default SP2010 design), is the default.master In this tutorial we will create a new masterpage using the v4.master as a template and then connect the newly created custom Master Page to our site. It is a good idea to leave the default Master Pages untouched (at least for the examples in this post).

First we need to clone the v4.master file. Open SharePoint Designer 2010, and from the Sites tab select the Open Site icon and enter your site URL.

The site root will be opened in SharePoint Designer 2010. Now select Master Pages from the left menu, click on the v4.master file and press CTRL+C and CTRL+V to create a copy of the .master file.

Name your master page – click on the Rename icon in the ribbon and enter your custom name (for example myCustom.master).

Using the newly created master page we are now ready to make the modifications. Users of your SharePoint site will not notice that we are changing anything, and if you break something – it will be the custom master page, not the one users are seeing.

4.3 Create a Custom CSS to Add Branding

Next we need a CSS file which overrides the default core4.css style definitions. To see some changes to our customizations, we will include the fixed width style for our new master page.

Open SharePoint Designer 2010, select All files from the left menu and then enter the Style library.

To create a new css file, right click on the Style Library and select New > CSS from menu.

Name this file myCustom.css, just to keep the naming schema consistent with our custom Master Page.

Right click the newly created .css file and select the Edit file in Advanced Mode option.

Now enter some code in the css file. One thing we will do in this tutorial is to render the SharePoint site with a fixed width of 1024 pixels (making a site fixed width is actually a very difficult task using just SharePoint 2010). Additionally, we will also change the ribbon background color and the site background color.

Enter the following code in your css file:

---

 

#s4-bodyContainer {

width: 1024px !important;

margin-left:auto;

margin-right:auto;

}

body #s4-ribbonrow {

background-color:#865102;

}

body.v4master {

overflow: visible;

background-color:black;

}

.ms-cui-ribbonTopBars {

width: 1024px !important;

margin-left:auto;

margin-right:auto;

}

.ms-cui-ribbonTopBars > div {

border-bottom:1px solid transparent !important;

}

---

We now have a custom CSS in the Style Library and a custom Master Page. Now we need to associate the css file with the custom Master Page.

Open the myCustom.master file with SharePoint Designer (in advanced editing mode). You will see the site preview, because by default it will open your Master Page on the Design tab.

Click the Code tab on the bottom of the editor. You will see the entire Master Page code and content, with many placeholders, Server Ribbon code etc. Fortunately, you don’t have to learn all of these to do some serious branding and modification.

First, we need to connect our Master Page with the css file. Within the <head> tag, we need to add a link to our custom CSS file:

<link href=”/Style%20Library/myCustom.css” rel=”stylesheet” type=”text/css” />

Now modify the s4-workspace area so it will read our css file properly:

Find the line:

<div id=”s4-workspace”>

and replace it with:

<DIV id=”s4-workspace” class=”s4-nosetwidth”>

This will add the class attribute to s4-workspace tag. Without this, our fixed size setting in the CSS file will be overridden by the default inline CSS.

Now we can test our Master Page, before we link it to our production site. The best way is to create a new test page from the selected Master Page. Go back to the Master Pages item in the left menu, and right-click our myCustom.master file, then select the New from Master Page option.

Give the site a name such as myCustom_Site and select where it should be created – the default Site Pages is fine.

After a while a new page will be created and SharePoint Designer will open it for editing (in code view). Click the Preview icon on the ribbon to see your changes.

4.4 Going Live with Your Custom SharePoint Master Page

If we have ensured that the newly created Master Page looks fine we can now connect it with our live production SharePoint site.

Open SharePoint Designer 2010, navigate to the Master Pages option in the left menu, right click the myCustom.master file and select Set as default Master Page.

Now, if you go to your main site (in my SP farm it’s http://master.spdev.local:888/) you should see the changed layout

Reference

https://www.nothingbutsharepoint.com/sites/eusp/pages/create-custom-css-and-master-page-in-sharepoint-2010.aspx

 

SharePoint 2010 Deploy & set Custom Masterpage per Feature

SharePoint 2010 Deploy & set Custom Masterpage per Feature

Good Article by Karsten Pohnke

http://www.ilikesharepoint.de/2013/03/sharepoint-2010-deploy-set-custom-masterpage-per-feature/

 

Deploy SharePoint 2010 Branding as a Farm Solution

Deploy SharePoint 2010 Branding as a Farm Solution


how to package and deploy SharePoint Branding as a farm solution. I will also walk you through how to add CSS and JavaScript files to custom master page. We can develop custom master pages with the help of SharePoint development tools in Microsoft Visual Studio 2010.
If you have multiple web front end servers/ if you have a requirement to apply custom branding across entire farm / if you want to have a consistent branding across multiple site collections, farm solution is the ideal approach. For larger SharePoint implementations it is recommended that you deploy branding as a farm solution. This approach will let you store all the branding files (CSS, Images) at one centralized location on the file server within 14 hive and it deploys all of the custom branding files to the correct location on each web front end server.
The farm solution should work for both SharePoint Foundation 2010 and Microsoft SharePoint Server 2010. There is no need to enable SharePoint Server Publishing infrastructure and SharePoint Server publishing feature. FYI, Publishing features are available only in SharePoint Server 2010 (standard and enterprise), but not in SharePoint 2010 Foundation.
Note: You have to be a farm administrator in order to deploy the farm solutions.

Creating SP2010Branding Project

Let’s get started! Open Visual Studio 2010, Choose “Empty SharePoint Project” and name it as SP2010Branding as shown in Figure 1.

Figure 1: Empty SharePoint 2010 Project
When you create the new SharePoint project, the SharePoint Customization Wizard prompts you to provide a URL to a local SharePoint site and to select either Deploy as a sandboxed solution or Deploy as a farm solution. Be sure to select Deploy as a farm solution, as shown in Figure 2. (After you enter the local site URL, click on “validate” to make sure you are connected to SharePoint)

Figure 2: Deploy as a farm solution
In the Solution Explorer right click on “SP2010Branding” node, select Add and then New Item. In the dialog box, select Module Item and name it as MyCustomMasterPages as shown in Figure 3.

Figure 3: Create SharePoint Module Item
If you have a look at the solution explorer now, it will contain the items as shown in the figure below:

The SharePoint Module Item that you just added comes with two files named Elements.xml and Sample.txt. Rename Sample.txt file to CustomBranding.master. Now open Elements.xml, the module inside elements tag will read as below:

<Module Name="MyCustomMasterPages">
  <File Path="MyCustomMasterPages\CustomBranding.master" Url="MyCustomMasterPages/CustomBranding.master" />
</Module>

Since all the SharePoint master pages are stored at http://yoursharepointsite/_catalogs/masterpage, we have to add our custom master page to the same location. In order to do that, we have to replace the above module element with the following one.

<Module Name="MyCustomMasterPages" Url="_catalogs/masterpage">
  <File Path="MyCustomMasterPages\CustomBranding.master" Url="CustomBranding.master" Type="GhostableInLibrary">
    <Property Name="UIVersion" Value="4" />
    <Property Name="ContentTypeId" Value="0x010105" />
  </File>
</Module>

We are almost there with the initial set up that is required! After making the above changes your elements file should look like the following.

If you want add multiple custom master pages to the solution you can add your master page under MyCustomMasterPages node and more importantly you have to modify the Elements.xml file. For each master page that you add, you should modify the inner File Element corresponding to that particular master page like how we did above.
The next step is to replace the contents of the CustomBranding.master file. The best way to start is copy the contents from v4.master (which is located at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\GLOBAL\v4.master) and paste it into our CustomBranding.master.
Currently, your custom master page is exactly similar to the standard SharePoint 2010 master page (v4.master). At this point, we will make some modification to our master page so that you see the visual difference.

Adding Image Files and CSS

Right click on SP2010Branding project node and Add then SharePoint “Images” Mapped Folder as shown in the Figure 4. Since we are adding these files to 14 hive Visual Studio will automatically add a sub folder named SP2010Branding (typically it will be your project name) to the Images folder to ensure that we are not overwriting/modifying any files that exist in 14 hive. Now go ahead and add an image called background to the SP2010Branding Subfolder (Don’t get confused with the SP2010Branding project node, add the image to SP2010Branding Subfolder which is under Images folder).

Figure 4: Adding SharePoint Images Folder
Now we are ready to add some CSS Files to our project. For that you need to right click on SP2010Branding project node Add then SharePoint “Layouts” Mapped (Refer to Figure 4). Then locate Layouts folder in the solution explorer and under that you will find SP2010Branding sub folder (Added by default) then right click on that SP2010Branding folder and Add then New Folder as shown in Figure 5.

Figure 5: Adding SharePoint mapped folders to store CSS and JS files
Now name the newly added folder as CustomCSSFiles and under that folder add a CSS file named changeribbonbg.css . Here we will add some code to change ribbon back ground image by using CSS. Open the changeribbonbg CSS file and place the following code into it:

body #s4-ribbonrow,
.ms-cui-topBar2 {
  /* default color was #21374c */
  background-image:url('/_layouts/Images/SP2010Branding/background.png');
  min-height:43px;
}

It’s important to keep an eye on how we are referencing the Image. Now we should link this CSS file to our custom master page. In the solution explorer locate and open the CustomBranding.master file and try to find </head> and then add the following line of code just before the </head> tag:

<SharePoint:CssRegistration ID="CssRegistration1" name="/_layouts/SP2010Branding/CustomCSSFiles/changeribbonbg.css" After="corev4.css" runat="server"/>

Adding JavaScript to the Master Page

Let’s add some JavaScript to the solution, go to SP2010Branding subfolder which is under Layouts folder and then add one more sub folder as shown in Figure 5 and name it as CustomJavaScripts. Next step is to add a JavaScript file named sp101.js to the CustomJavaScripts folder. Now open the sp101.js file and paste the following code into it:

alert("JavaScript linked successfully, click OK to see your custom branding !");

Now we will link sp101.js JavaScript file to our custom master page. In the solution explorer locate and open the CustomBranding.master file and try to find <asp:ScriptManager></asp:ScriptManager> then you will find the following line:

<asp:ScriptManager id="ScriptManager" runat="server" EnablePageMethods="false" EnablePartialRendering="true" EnableScriptGlobalization="false" EnableScriptLocalization="true" />

Now replace the above with the following:

<asp:ScriptManager id="ScriptManager" runat="server" EnablePageMethods="false" EnablePartialRendering="true" EnableScriptGlobalization="false" EnableScriptLocalization="true">
  <Scripts>
    <asp:ScriptReference Path="/_layouts/SP2010Branding/CustomJavaScripts/sp101.js"></asp:ScriptReference>
  </Scripts>
</asp:ScriptManager>

If you want to add multiple JavaScript files to the master page, add those scripts to CustomJavaScripts folder in the solution explorer and then in the master page add additional <asp:ScriptReference></asp:ScriptReference> reference tags corresponding to those scripts. If you have followed the post correctly, your solution explorer should look like below.

It’s been a long post I know! But if you are really curious you can deploy the solution, you will find the custom master page in the site that you have deployed the solution to. But you have to manually change the master page to see the custom branding/visual difference. I am not a big fan of manual effort. So we will develop a feature to activate the custom branding! Sounds good?
Finally it’s time to write some code, let’s get started. In the solution explorer expand the features section; right click on Feature1 and then Add Event Receiver as shown in the Figure 6.

Figure 6: Adding Event Receiver
Now we will write some code to apply the custom master page when the feature is activated and also we will remove all the custom branding to apply v4.master when the feature is deactivated. Alright, let’s add some flavor to our project! Open the Feature1.EventReceiver.cs file and paste the following methods into it:

// Uncomment the method below to handle the event raised after a feature has been activated.
 
public override void FeatureActivated(SPFeatureReceiverProperties properties) {
  using (SPWeb curWeb = properties.Feature.Parent as SPWeb) {
    Uri masterUri = new Uri(curWeb.Url + "/_catalogs/masterpage/CustomBranding.master");
    curWeb.MasterUrl = masterUri.AbsolutePath;
    curWeb.CustomMasterUrl = masterUri.AbsolutePath;
    curWeb.UIVersion = 4;
    curWeb.Update();
  }
}
 
// Uncomment the method below to handle the event raised before a feature is deactivated.
 
public override void FeatureDeactivating(SPFeatureReceiverProperties properties) {
  using (SPWeb curWeb = properties.Feature.Parent as SPWeb) {
    Uri masterUri = new Uri(curWeb.Url + "/_catalogs/masterpage/v4.master");
    curWeb.MasterUrl = masterUri.AbsolutePath;
    curWeb.CustomMasterUrl = masterUri.AbsolutePath;
    curWeb.Update();
  }
}

Updating the CustomMasterUrl property is important only in publishing sites that contain publishing pages inside the Pages document library. The CustomMasterUrl property is used to reassign the master page for publishing pages. Assigning a new value to the CustomMasterUrl property in a SharePoint Foundation site has no effect nor does it cause any problems.
One last piece of information that I would like to share is feature scopes. There are 4 different levels of scopes that are available in SharePoint 2010 and they are described in the following table.

Scope	Description
Web	A Web Site scoped Feature is the one that can be activated only at the individual web site level and is specific to that particular web site.
Site	A Site Collection scoped Feature is the one that can be activated at the site collection level and contains all web sites in a site collection as a whole.
WebApplication	A Web Application scoped Feature is the one that can be activated at the web application level for all the web sites in a web application.
Farm	A Farm scoped Feature can be activated at the server farm level for an entire server farm.

Now in the solution explorer double click Feature1, change the Title and Description according to your needs as shown in the Figure 7.

Figure 7: Feature Scope and Description
You can change the scope of the feature if you want to. Most commonly used feature scopes are site and web. For our solution Site/Web scope should suffice!
Site features apply to a whole site collection and can be managed by going to the Site Actions > Site Settings > Site Collection Administration > Site collection Features.
Web features apply to a specific web site and can be managed by going to the Site Actions > Site Settings > Site Actions > Manage Site Features
Wohoo.. We are done. Right click solution and Deploy!
So depending upon the scope that you choose, you can find SP2010 Branding feature either in Site collection features or in Manage Site Features section and you can activate/deactivate the feature to test our solution as shown in the Figure 8.

Figure 8: Activate/Deactivate Feature
Once you activate the feature, ideally you should see the following alert message as shown in Figure 9.

Figure 9: JavaScript Alert on Successful deployment
Click OK and finally you will see the custom branding as shown in the Figure 10. Notice that ribbon has a new back ground image.

Figure 10: Deployed Custom Branding
We successfully finished deploying our branding solution, but it’s just the beginning. To make your SharePoint site attractive you have to edit your master page and CSS files according to your design. I hope you’ve enjoyed my blog post! Feel free to email me if you have any questions.
Please download the attached file to access the SP2010 Branding Solution.


Reference

https://captechconsulting.com/blog/amarender-peddamalku/deploy-sharepoint-2010-branding-farm-solution


 

Deploy Master Page using Visual Studio Solution Project and Set it as Default Master Page

Deploy Master Page using Visual Studio Solution Project and Set it as Default Master Page



how to add a master page using a Visual Studio solution project. Also setting the same master as a default for site.

STEP 1 : Adding a Master Page using Module

1. Open a visual studio 2010
2. Add new project
3. Empty Sharepoint Project > Deploy as Farm Solution > Finish.
4. Add New Item > Select "Module" > I named it as "MasterPage".
5. Delete the "Sample.txt" which gets added in the module by default.
6. Add new MainMasterPage.master. Do whatever change you want to it.
7. Open the elements.xml file of "MasterPage" module. You will have to make some modification shown below.
   
   
   

   <?xml version="1.0" encoding="utf-8"?>
   <Elements xmlns="http://schemas.microsoft.com/sharepoint/">
       <Module Name="MasterPage" List="116" Url="_catalogs/masterpage">
           <File Path="MasterPage\MainMasterPage.master" Url="MainMasterPage.master" Type="GhostableInLibrary">
               <Property Type="string" Name="Title" Value="My Main Master Page"/>
           </File>
     </Module>
   </Elements>

8. Please verify the below given text i made change in the original one. This is MOST IMPORTANT!!!.

   List="116" Url="_catalogs/masterpage"

   Url="MainMasterPage.master" Type="GhostableInLibrary"

9. Once this is set just deploy the project.

STEP 1.1 : Verify the file got uploaded

1. Open the site in SharePoint Designer 2010.
2. All Files > _catalogs > MasterPage
3. The file should be at this location because if you see the element.xml above in the url we have given the path of "_catalogs/masterpage". That's it we now achieved the first step of adding a master file to the site.

STEP 2 : Apply the page as a default master page

1. In the visual studio solution project select "Features > Feature1 > Feature1.feature".
2. Right click "Add event receiver".
3. Put this code.
   
   

   /// <summary>
   /// Set the MainMasterPage.master as default master for site.
   /// </summary>
   /// <param name="properties"></param>
   public override void FeatureActivated(SPFeatureReceiverProperties properties)
   {
       SPSecurity.RunWithElevatedPrivileges(delegate
       {
           using (SPWeb _web = ((SPSite)properties.Feature.Parent).RootWeb)
           {
               Uri _siteMaster = new Uri(string.Format("{0}/_catalogs/masterpage/MainMasterPage.master", _web.Url));
               _web.MasterUrl = _siteMaster.AbsolutePath;
               _web.CustomMasterUrl = _siteMaster.AbsolutePath;
               _web.Update();                   
           }
       });
   }

4. Right click the project and deploy the solution.

I hope this helps you with the deployment of master page and setting it as a default.

PROBLEM :- There is a problem with the current process. For the first time this will work but if you make any changes to the master page and re-deploy the same solution will not deploy this new master page with the changes on the server. Please read my next blog "Sharepoint 2010 Master page issue with re-deployment with new changes from Visual Studio solution" for the solution.

One step remaining.The developer must go into SharePoint Designer and set the new master as the default master. This cannot be accomplished in the deployment in VS.

Reference

http://maulikdhorajia.blogspot.in/2011/09/sharepoint-2010-deploy-master-page.html

 

Deploying a custom master page in SharePoint 2010

Deploying a custom master page in SharePoint 2010

Today I created a Module. A module can be used to deploy files to your SharePoint environment and the scenario I came up with was to use a module to deploy a master page.

• I started out by creating an Empty SharePoint project. This can have any name you like and it can be both a farm and a sandboxed solution
• Next add an new item to the project and choose a module
• You can rename the module if you want to, I will leave the name at Module1
• After the module is created it contains an elements.xml file and a sample.txt file. The sample.txt file can be renamed to sample.master.

Project structure after adding a module and renaming the sample file to sample.master
I’m not a designer, so I wasn’t interested in creating a brilliant new design (good job, because I wouldn’t be able to do that!).
For the purpose of this example I just took the standard SharePoint 2010 master page contents.

• Open up SharePoint Designer and open the site you are working on
• Choose Master Pages on the left side
• Open v4.master

Don’t let SharePoint fool you. There is a default.master, but this is the old SharePoint 2007 master page that is used if you perform a visual upgrade. When creating a site in SharePoint 2010 the master page that will be used by default is v4.master. I know it’s a bit confusing, but if you have been working with SharePoint for a while you won’t be surprised by this.

• Copy the contents of v4.master and past them in your sample.master file in Visual Studio. Make the changes you want to.
• Note how the elements.xml file has changed to reference the sample.master rather than the sample.txt

 
The contents of the elements.xml file

• Make sure the module is added to a feature in your project that is scoped at the site (= site collection) level

You could stop here and this solution will deploy your sample.master master page to the master page gallery of your site collection.
This will not apply the master page to the site collection when the feature gets activated though. It will only make it available for selection.

• If you the master page to be applied when the feature gets activated you right click on the Feature1 and you add an event receiver. This will add a feature receiver file to the feature.
• In this file we will add some code that will apply the sample.master master page when the feature gets activated and it will apply the v4.master when the feature gets deactivated.

[Update 10/12/2010]: Code updated because of improperly disposed SPSite and SPWeb objects. Thanks Donald Hessing and Rhys for pointing it out.

 
Code used in the feature receiver
Now if you activate the feature the code in the feature receiver will run and will apply sample.master to the site. As you can see we change both the MasterUrl and the CustomMasterUrl. The MasterUrl is used on all pages that are not publishing pages. This means it is used on the pages in the sitepages library and on the pages in the _layouts directory like the settings page for instance. The CustomMasterUrl is only used on pages that are stored in the Pages library. This library is created when the SharePoint Server Publishing Infrastructure features is activated on the site collection and the SharePoint Server Publishing feature is activated on the site.
You can also use the SharePoint user interface to apply a new master page. The Site Master Page is the equivalent of the CustomMasterUrl and the System Master Page is what the object model calls the MasterUrl.

Changing the master page using the SharePoint user interface 

Reference

http://sharepointchick.com/archive/2010/03/26/deploying-a-custom-master-page-in-sharepoint-2010.aspx
 

Some Free WebParts for SharePoint 2013 and SharePoint 2010

Some Free WebParts for SharePoint 2013 and SharePoint 2010

 Note :  As these web parts caters different platforms ( SP 2013 and SP 2010) , the developer has not provided source code in codeplex. Source can be downloaded from sky drive links that are available at the bottom of the blog posts

Sl.No	Web Part	Particulars	Platform
1	Script Box WebPart	Easily refer JavaScript and CSS style sheets in SharePoint Application with Script Box WebPart (This not OTB Script Editor WebPart)	SharePoint 2013, SharePoint 2010
2	Muti WebPart Tab Pages WebPart	Combine multiple Web Parts placed in a SharePoint 2013 Page into Tab Pages with the help of this Muti WebPart Tab Pages WebPart. This WebPart accepts web part titles as input parameter and convert those WebParts into Tab Pages	SharePoint 2013
3	Tab Pages Web Part	Muti Tab Pages WebPart in SharePoint 2013 with jQuery Easy Tabs Plugin. No more combining multiple web parts into Tab Pages. You can create tab pages in a single web part itself with this Multi Tab Pages WebPart. Source code is provided for SharePoint 2013, but it can be easily converted to SharePoint 2010	SharePoint 2013
4	Feature Manager WebPart for Office 365	Feature Manager web part for public facing SharePoint 2013 website of Office 365. As there is no Manage Features option available in public facing site of Office 365, this web part would help to manage features.	Office 365, SharePoint 2013
5	Twitter Feed WebPart	Twitter Feed WebPart based on Twitter API 1.1.This web part has the capability to render the content in default Twitter Timeline mode based on Twitter Widget ID and also has a custom rendering mode	SharePoint 2013
6	Flip Book WebPart	Flip Book WebPart transforms the web part content to a book with cover that can be flipped page by page.	SharePoint 2013, SharePoint 2010
7	Announcement Slider Web Part	Create a Slider based on the items available in your Announcement list.	SharePoint 2010
8	Image Carousel Web Part	Image carousel web part is based on highly popular Nivo slider plugin. This web part supports all configuration option provided by Nivo Slider. These configuration settings can be set via properties of web part	SharePoint 2013
9	Data List Web Part	This is a grid web part based on jQuery plugin data tables. This plugin provides extensive options to sort, filter and search grid items.	SharePoint 2013
10	News Ticker Web Part	A news ticker in SharePoint 2013.	SharePoint 2013
11	Change Password Web Part	Change Password WebPart for Active directory Users in SharePoint 2010	SharePoint 2010
12	Twitter Feed Client Web Part	SharePoint 2013 Napa App which renders tweets based on a Twitter handler	SharePoint 2013 NAPA
13	Access Denied Web Part	This web part can be configured to redirect users to access denied page or to a custom URL irrespective of their privileges available for that page.	SharePoint 2013, SharePoint 2010
14	Metro UI Live Tiles Web Part	Live Tiles Web Part based on  Metro UI	SharePoint 2013, SharePoint 2010
15	Dynamic Promoted Links	Promoted Links WebPart with dynamic data feed	SharePoint 2013
16	Share Point Dynamic Forms	This is a separate codeplex project , which has the capability to create data entry forms dynamically based on the configuration details set in the web part or in a separate configuration file.	SharePoint 2010

http://sharepointdirect.blogspot.in/

http://list.ly/list/3GG-free-webparts-for-sharepoint-2013-and-sharepoint-2010

http://www.ashokraja.me/post/Listed-my-10-plus-free-Web-Parts-for-SharePoint-2013-and-2010-in-Codeplex-and-listly.aspx

Thanks to Ashok Raja for sharing these webparts