Feb 26, 2013
Jan 7, 2013
The feature being activated is a Site scoped feature which has a dependency on a Site Collection scoped feature which has not been activated. Please activate the following feature before trying again: SharePoint Server Publishing Infrastructure f6924d36-2fa8-4f0b-b16d-06b7250180fa
Some times while activating the Publishing feature in SharePoint through the options in Site Settings we will get this error:
The feature being activated is a Site scoped feature which has a dependency on a Site Collection scoped feature which has not been activated. Please activate the following feature before trying again: SharePoint Server Publishing Infrastructure f6924d36-2fa8-4f0b-b16d-06b7250180fa
Solution:
It can be done in many ways (2 ways mentioned below):
1. We can use the Site Settings -> Site Collection Administration -> Site Collection Features to enable this feature.
2. Then Site Settings -> Site Administration -> Site Features -> Enable this feature.
3. We can also achieve this using STSADM command as shown below:
The feature being activated is a Site scoped feature which has a dependency on a Site Collection scoped feature which has not been activated. Please activate the following feature before trying again: SharePoint Server Publishing Infrastructure f6924d36-2fa8-4f0b-b16d-06b7250180fa
Reason:
The reason being the "SharePoint Server Publishing Infrastructure" feature has to be enabled at SITE COLLECTION level, then it has to be activated at SITE LEVEL enable the feature. So that we can create Publishing pages in SharePoint.
Solution:
It can be done in many ways (2 ways mentioned below):
1. We can use the Site Settings -> Site Collection Administration -> Site Collection Features to enable this feature.
2. Then Site Settings -> Site Administration -> Site Features -> Enable this feature.
3. We can also achieve this using STSADM command as shown below:
STSADM.EXE -o deactivatefeature -id f6924d36-2fa8-4f0b-b16d-06b7250180fa -url "http://SiteURLHere/" -force
Then,
STSADM.EXE -o activatefeature -id f6924d36-2fa8-4f0b-b16d-06b7250180fa -url "SiteURLHere" -force
Hope this helps you!
Export SharePoint Group to Excel using PowerShell
$siteUrl="SiteURLHere" $groupName="GroupNametoExport" $Output = @("GroupName|Name|Login|Email|Department|Title") $web = Get-SPWeb $siteUrl $site = $web.Site $rootWeb = $site.RootWeb $UserList = $rootWeb.Lists["User Information List"] $web.SiteGroups[$groupName].Users|%{$user = $UserList.GetItemById($_.ID) if($user -ne $null) { $JobTitle = $user["JobTitle"] $Department = $user["Department"] } $Output += ($groupName+"|"+$_.Name+"|"+$_.UserLogin+"|"+$_.Email+"|"+$ Department +"|"+$JobTitle) } $rootWeb.Dispose() $web.Dispose() $site.Dispose() $Output > "D:\MembersExport.csv"
Import Excel to SharePoint List using PowerShell
# Import the .csv file, and specify manually the headers, without column name in the file $contents = Import-CSV ‘C:\Input.csv' -header("Employee ID", "Employee Name") # Web URL $webURL = “SITEURL here” $web = Get-SPWeb -Identity $webURL $listName = "ListNameHere" $list= $web.Lists["$listName"] # Iterate for each list column foreach ($row in $contents ) { $item = $list.Items.Add(); $item["Employee ID"] = $row.GroupName $item["Employee Name"] = $row.Permissions $item.Update() } Write-Host -ForegroundColor green "List Updated Successfully" $web.Dispose()
Jan 6, 2013
Import Users from Excel to SharePoint using PowerShell
# Import the .csv file, and specify manually the headers, without column name in the file $userList=IMPORT-CSV C:\UserToUpload.csv -header("GroupName","UserName") #Get the site name to the variable $web = Get-SPWeb SiteURLHere foreach ($user in $userList) { $groupName = $web.SiteGroups[$userList.group] $user = $web.Site.RootWeb.EnsureUser($userList.user) $groupName.AddUser($user) } Write-Host -ForegroundColor green "Users Added Successfully" } $Web.Dispose()
Add Users to SharePoint Group using PowerShell
#Get the site name to the variable $web = Get-SPWeb SitURLHere #Get the group name to the variable $groupName = $web.SiteGroups["Group Name Here"] #Assign user to variable $user = $web.Site.RootWeb.EnsureUser(“User ID Here”) #Add user to group $groupName.AddUser($user) Write-Host -ForegroundColor green "User Added Successfully";
Dec 18, 2012
SharePoint 2013 Certification
Below is the links to know about initial release for Certifications in SharePoint 2013:
Exam 70-331: Core Solutions of Microsoft SharePoint Server 2013 http://www.microsoft.com/learning/en/us/Exam.aspx?ID=70-331
Exam 70-332:Advanced Solutions of Microsoft SharePoint Server 2013 http://www.microsoft.com/learning/en/us/exam.aspx?ID=70-332
Exam 70-331: Core Solutions of Microsoft SharePoint Server 2013 http://www.microsoft.com/learning/en/us/Exam.aspx?ID=70-331
Exam 70-332:Advanced Solutions of Microsoft SharePoint Server 2013 http://www.microsoft.com/learning/en/us/exam.aspx?ID=70-332
Dec 12, 2012
Web Part with Custom Tool Part in SharePoint
To know about Basics of Creating a Custom Web Part with Validations and Deploying it in the SharePoint, read this article.
In this article, we will know how to create a custom web part in SharePoint with Custom Tool Part (Custom Properties).
Before creating a custom web part with custom tool part, we will know about the basics of Custom Tool Part in SharePoint.
Before creating a custom web part with custom tool part, we will know about the basics of Custom Tool Part in SharePoint.
What is custom tool part?
The Custom tool part is part of the web part infrastructure, which helps us to create a custom user interface for the web part properties which is different from default property pane.
Difference between Standard Tool Box and Custom Tool Part Properties
Below is the difference between the Sandbox and Custom Tool Part properties in a web part:
Sand Box Tool Box Properties:This is the tool box that comes by default and it contains Text Boxes, Check Boxes and Drop down lists to fill or select the data. But this tool box does not contain any dynamic controls for displaying the dynamic data from the SharePoint list or libraries. This is something like hard coding the values in the .cs file of the web part.
Custom Tool Part Properties:With the Custom tool part or tool box can contain any asp controls in it and it can bind the data to from the database or list and libraries. Hence displaying the dynamic values or data is possible using this tool box.
Below is the difference between the Sandbox and Custom Tool Part properties in a web part:
Sand Box Tool Box Properties:This is the tool box that comes by default and it contains Text Boxes, Check Boxes and Drop down lists to fill or select the data. But this tool box does not contain any dynamic controls for displaying the dynamic data from the SharePoint list or libraries. This is something like hard coding the values in the .cs file of the web part.
Custom Tool Part Properties:With the Custom tool part or tool box can contain any asp controls in it and it can bind the data to from the database or list and libraries. Hence displaying the dynamic values or data is possible using this tool box.
List of attributes used for creating a Custom Tool Part
Two Classes used in the Web Part Tool Pane Creation
CustomPropertyToolPart – used to show and modify the custom properties created in the web part.
Please feel free to share your thoughts and share this post if it helps you!
How does Ribbon in SharePoint 2010 works?
A file called CMDUI.XML stays at the web front end which contains the Out-of-Box site wide Ribbon implementation i.e. all the Ribbon UI for the entire site. In addition to this you have a CustomAction for each ribbon component.
These CustomActions have CommandUIExtentions block which has CommandUIDefinitions and CommandUIHandlers which make up the activity of the ribbon component.
So, when the ribbon is loaded the CommandUIDefinition merges with Out-of-Box definition in the CMDUI.XML
Dec 11, 2012
Consuming a web service using ASP .NET
To
know about basics of web service read this article.
Background:
Implementation:
To
know about creating a web service using ASP .NET read this article.
Background:
In the previous article we have learned about creating a web
service. Now in this article, we will learn how to consume a web service using
asp .NET.
Real Time Example:
Nowadays mobile application (Mobile Apps) are used widely
all the users. Take a scenario, we install the “Weather” gadget in our mobile
and check the weather of a particular place.
Think where we are receiving this weather information? It is
actually we are consuming the web services.
We will select the region/place to see the weather, a web
service will be called and the weather info is displayed.
Hence, Web Services are hosted somewhere and via internet we are
consuming the data through the web service.
Implementation:
1. Create an ASP .NET web application with a simple design as
shown below:
2. Now, we have to add the web service reference to this
Project (Here we use the web service created in the previous article). Click on
the Projects in solution explorer -> Add web reference -> give the url of
the web service
(Note: to access the web service in the client use the
appropriate machine/domain name)
Now, you will see the following screen:
3.
Click on Go and search the web service and then give the web reference name say
“Consume Service” in our example. Then click
Add Reference button.
4.
Now, in the solution explorer you will see the Web Reference being added as
shown below:
5.
We can use the methods exposed by the web service in our code and test the
result. Sample code is shown below:
public partial class _Default : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void btnToCelsius_Click(object sender, EventArgs e) { double x = Convert.ToDouble(txtValue.Text); if(txtValue.Text != string.Empty) { try { ConsumeService.Service service = new ConsumeService.Service(); lblOutput.Text = service.ToCelsius(x).ToString(); } catch (Exception) { throw; } } } protected void btnToFahreinheit_Click(object sender, EventArgs e) { double x = Convert.ToDouble(txtValue.Text); if (txtValue.Text != string.Empty) { try { ConsumeService.Service service = new ConsumeService.Service(); lblOutput.Text = service.ToFahreinheit(x).ToString(); } catch (Exception) { throw; } } } }
6. Build and run the code. Test the result
by giving some inputs as shown below:
The whole source code can be downloaded from this link.
Hope
the three articles about the web services explained about the basics of web
services, creating and consuming the web services using ASP .NET in a simple
way.
Please
free to comment which help me to write more.