# 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()
Jan 6, 2013
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