sharepoint 2010 jumpstart · sharepoint designer 2010 visio 2010 5. what are the new features in...
TRANSCRIPT
SharePoint 2010 Jumpstart [Go Green Paperless Office- SharePoint 2010 Interview Capsule]
EBook 4 Page 0 Vishal Gupta [MCTS, MCP, MCSD, MCSE, MCSE +I, CNA, NCIM, NCIBS, BPP, MCA, MASE] [email protected]
LinkedIn: Http://in.linkedin.com/in/vishalguptasharepoint twitter.com/vguptadelhi
SharePoint 2010 Interview Capsule Intent SharePoint as a product is easy to understand, install and configure but when it comes to giving or taking interview it becomes very difficult to find the precise questions one can ask or study. This eBook appraises SharePoint 2010 developers, administrators, architects, users and interviewers about the key terms and precise questions to remember in SharePoint 2010.The frequently asked question during interviews are stated in simple language. The user will also come to know about
SharePoint Basic Questions.
SharePoint Customized Questions.
SharePoint Advance Questions.
All the questions listed are important and one must go through and remember all of them but then as per industry definition role, one can ponder the questions like this:
SharePoint Basic Questions- SharePoint 2010 Users/ Developers/ Architects/Administrators
SharePoint Customized Questions- SharePoint 2010 Developers/ Architects
SharePoint Advance Questions- SharePoint 2010 Users/ Developers/ Architects/Administrators
Author Information Vishal Gupta, having experience of 15 yrs. using Microsoft Technologies. Since last eight years working on creating solutions using SharePoint 2003, Moss 2007 and SharePoint 2010.The solutions involves creation and designing of internet & intranet Portals for various small, medium & large-scale organizations. Being an architect for mission critical assignments, created the architecture to meet functional as well as non-functional business requirements. I am Microsoft Certified [MCP, MCSE, MCSE+I, MCSD, MCTS]. I Love to enable organizations to implement SharePoint. Where to find Vishal Gupta online: Website: http://vishalguptasharepointblog.blogspot.com/ Twitter: vguptadelhi Facebook: Facebook profile-vgup LinkedIn: http://www.linkedin.com/in/vishalguptasharepoint MySpace: http://www.myspace.com/568552837 Blog: http://vishalguptasharepointblog.blogspot.com/ Mail:[email protected]
0. Introduction The aim of writing SharePoint Interview capsule is to list SharePoint 2010 interview questions. This eBook contains questions in simple language with scenarios to enable user to remember easily.
0.1 Basic Questions
1. What is SharePoint 2010? SharePoint was born out of a simple idea: “Sharing Documents”. Microsoft developed family of software products called “SharePoint”, to perform features like File Sharing, Collaboration, and Web Publishing. In simple terms, SharePoint acts as the single platform to share, communicate, store, and collaborate the content, documents, and records.
2. What does SharePoint 2010 family of products consists of? 1. SharePoint Foundation 2010 2. Search Server 2010 Express 3. SharePoint Server 2010 4. Search Server 2010 5. FAST™ Search Server 2010 for SharePoint 6. SharePoint Designer 2010
3. What is the History of SharePoint?
SharePoint Products
Site Server V 1.0 (1996)
Site Server V 3.0 (1998)
SharePoint Portal Server (SPS) in 2001
SharePoint Portal Server
2003
Office SharePoint Server 2007
SharePoint Portal Server
2010
Microsoft Frontpage
SharePoint Team Services (STS) in 2001
Windows SharePoint Services 2.0
Windows SharePoint Services 3.0
SharePoint Foundation Server 2010
SharePoint Designer 2007
SharePoint Designer 2010
4. What are Features of SharePoint?
Communities: The new version of SharePoint allows users to work together in different ways. Microsoft has enhanced the social feature of SharePoint 2007 in SharePoint 2010 and has made it look better. Communities allow people to collaborate in groups, share knowledge, and find information on various topics easily. Content: SharePoint content shifts SharePoint 2010 from a departmental solution to an enterprise solution. There has been massive improvement in content wherein users can add a significant number of documents to SharePoint. They can even use external data storage options to store more data. Search: Microsoft SharePoint 2010 has acquired FAST search server, which improves the search tremendously for users. Now, users not only can search for content, but also people. User can opt for better language options with thumbnails and previews. User can even sort out the search queries and study similar search to get relevant search results. Insights: with the help of SharePoint insights, users can access information through different data sources like dashboards, scorecards, reports and more. To help users, Microsoft has introduced performance point server to the SharePoint platform. It is also known as Performance point services for SharePoint. It helps users discover right people and expertise to make better business decisions. Compositions: SharePoint being a complete platform helps users in creating their code solution on premises or in the cloud. Complex application can be developed with the help of well-known tools like:
InfoPath
SharePoint designer 2010
Visio 2010
5. What are the new features in Sharepoint? 1- Access Services: Use Access Services in Microsoft SharePoint Server 2010 to edit, update, and
create linked Microsoft Access 2010 databases that can be viewed and manipulated by using an Internet browser.
2- Business Connectivity Services: SharePoint Server 2010 include Microsoft Business Connectivity Services, which is a set of services and features that provide a way to connect SharePoint-based solutions to sources of external data and to define external content types based on that external data
3- Central Administration: Central Administration has been redesigned in SharePoint Server 2010 to provide a more familiar experience
4- Digital Asset Management: SharePoint Server 2010 includes a new asset library specially designed for managing and sharing digital assets such as audio, video, and other rich media files.
5- Enterprise Search (Fast Search): With the new capabilities in SharePoint Server 2010, search administrators can configure an optimal search infrastructure that helps end users find information in the enterprise quickly and efficiently.
6- Excel Services: Excel Services in SharePoint 2010 can be used to publish Excel client workbooks on SharePoint Server 2010
7- Health Monitoring: SharePoint Server 2010 includes an integrated health analysis tool called SharePoint Health Analyzer that enables SharePoint Server to automatically check for potential configuration, performance, and usage problems
8- Managed Metadata: The Managed Metadata Service supports the use of managed metadata, as well as the sharing of content types across the enterprise.
9- Performance Point Services: Performance Point Services in Microsoft SharePoint Server 2010 provides flexible, easy-to-use tools for building dashboards, scorecards, and key performance indicators (KPIs
10- Records Management: In SharePoint Server 2010, user can manage records in an archive, or can manage records in the same document repository as active document
11- Sandboxed Solutions: User can deploy sandboxed solutions to quickly and more securely solve business problems. Sandboxed solutions are like farm solutions except in the following ways: they are rights-restricted and have a more permissive deployment policy than farm solutions; they are limited to the site collection to which they are deployed;
12- Social Computing: SharePoint Server 2010 includes social networking tools such as My Site Web sites and social content technologies such as blogs, wikis, and really simple syndication (RSS). These features are built upon a database of properties that integrates information about people from many kinds of business applications and directory services
13- Upgrade: 13.1: Visual Upgrade: A new feature that is available with upgrade allows the server administrator or site owner to determine when and if the new look for SharePoint Server 2010 is used for a particular site collection. Server administrators can choose to adopt the new look and feel for all sites during upgrade, let site owners make the choice after upgrade, or keep the old look and feel for all site 13.2: Feature Upgrade: SharePoint Foundation 2010 provides new members and types that make it possible for user to upgrade custom Features through versioning and declarative upgrade actions. User can update any Features created for Office SharePoint Server 2007 to work with SharePoint Server 2010 by using these members.
14- Visio Services: The Visio Graphics Service is a service on the SharePoint Server 2010 platform that enables users to share and view Visio diagrams and enables data-connected Microsoft Visio 2010 diagrams to be refreshed and updated from a variety of data source
15- Windows Power Shell: Windows Power Shell is the new command-line interface and scripting language specifically designed for Admin
16- Client Object Model: Microsoft SharePoint Foundation 2010 introduces three new client APIs for interacting with SharePoint sites: from a .NET managed application, from a Microsoft Silverlight or from ECMAScript (JavaScript, JScript) that executes in the browser. The new client object models provide an object-oriented system for interoperating with SharePoint data from a remote computer easier to use existing SharePoint Foundation Web services.
6. What are the key differences between Windows Shared Services 3.0 and MOSS 2007?
Feature Name / Area WSS (3.0) MOSS 2007
Collaboration
Standard site templates Inc. Inc.
Social networking web part N/A New
Wikis Inc. Inc.
Blogs Inc. Inc.
Email integration Inc. Inc.
Document collaboration Inc. Inc.
Real time presence and communication Inc. Inc.
Enterprise Portal N/A
My site personal site N/A New
User profiles N/A New
Feature Name / Area WSS (3.0) MOSS 2007
Audience targeting N/A New
Site Manager N/A New
Mobile device support Inc. Inc.
Colleagues and membership web parts N/A New
Privacy & Security N/A New
Content syndication N/A New
Integration with SharePoint designer (FrontPage technology)
Inc. Inc.
Integration with outlook 2007 Inc. Inc.
Integration with access, excel, PowerPoint, word 2007
Inc. Inc.
Enterprise search
Search results Inc. Inc.
Enterprise content sources N/A New
People search N/A New
Business data search N/A New
Indexing controls N/A New
Administration management N/A New
User interface Inc. Inc.
Enterprise content management
Business document workflow support N/A New
Document information panel Inc. Inc.
WYSIWYG web content editor N/A New
Page layouts N/A New
Navigation controls N/A New
Content authoring N/A New
E-mail content as records N/A New
Records repository N/A New
Business process forms
Browser based forms N/A New
Centralized forms management and control
N/A New
Compatibility checker N/A New
Integrated deployment model for “No code” forms
N/A New
Form import wizard N/A New
“Design once” development model N/A New
Business intelligence
Business data catalog N/A New
Key performance indicators N/A New
Integrated business intelligence dashboards
N/A New
Web based business intelligence using excel services
N/A New
Feature Name / Area WSS (3.0) MOSS 2007
Data connection libraries N/A New
Business data web parts N/A New
Platform services
Notification service N/A New
Single sign on N/A New
Excel spreadsheet developer reuse and extensibility
N/A New
Workflow Inc. Inc.
Support for ASP. Net 2.0 Inc. Inc.
7. What are the key differences between Windows Shared Services 3.0 and Microsoft SharePoint
Foundation 2010?
Feature Name / Area WSS (3.0) Foundation 2010
Business Connectivity service N/A New
Windows PowerShell N/A New
Sandboxed solutions N/A New
Claims based authentication N/A New
Central administration N/A New
Client object model N/A New
Ribbon Interface N/A New
ULS Logging N/A New
Service application framework N/A New
Upgrade N/A New
Health monitoring N/A New
Audience targeting N/A New
Silverlight web parts N/A New
Browser based customization N/A New
Workflows N/A New
SharePoint designer N/A New
Microsoft synch framework N/A New
InfoPath form services N/A New
8. What are the key differences between SharePoint Server 2007 vs. SharePoint Server 2010?
Feature Name / Area SharePoint Server 2007 SharePoint Server 2010
Sites
Office Integration Inc. Imp
Line-of-Business Integration Inc. Imp
Enterprise Management Operations Inc. Imp
Management tools and reporting Inc. Imp
Feature Name / Area SharePoint Server 2007 SharePoint Server 2010
Web Analytics N/A New
Mobile Connectivity Inc. Imp
Full-fidelity viewing N/A New
Editing to mobile N/A New
Contextual Ribbon N/A New
Microsoft Silverlight N/A New
Office Web Applications N/A New
Tagging N/A New
Audience Targeting Inc. Imp
Communities
People profiles Inc. Imp
Photos and presence N/A New
Micro blogging N/A New
Note Board N/A New
Recent activities N/A New
Organization Browser N/A New
Add colleagues Inc. Imp
Social bookmarks N/A New
Tags N/A New
Blogs Inc. Imp
Wikis Inc. Imp
Enterprise Wikis N/A New
Ratings N/A New
Colleague suggestions Inc. Imp
Keyword suggestions N/A New
Content
Compliance Everywhere N/A New
Flexible Records Management N/A New
Shared Content Types and Managed Metadata Service
N/A New
Content Organizer N/A New
Rich Media Management N/A New
Document Sets N/A New
Word Automation Services N/A New
Support for Accessibility Standards N/A New
Search
People and expertise search Inc. Imp
Search from Windows7 and Windows Mobile
Inc. Imp
Common connector framework for indexing and federation
Inc. Imp
Scale and performance via Imp topology architecture
Inc. Imp
Ability to build search-powered applications
Inc. Imp
Refinement panel and sorting N/A New
Feature Name / Area SharePoint Server 2007 SharePoint Server 2010
Social behavior improves relevancy N/A New
Thumbnails, previews, and view in browser
N/A New
Advanced content processing with strong linguistics
N/A New
Insights
KPI details N/A New
Dashboard Designer Inc Imp
Enhanced navigation, including filtering and sorting
N/A New
Publish more workbooks N/A New
JavaScript Object Model N/A New
PowerShell scripting N/A New
Richer fidelity with Excel workbooks N/A New
Support for Analytical Services formatting
N/A New
Additional data sources, including external lists and "Power Pivot" workbooks (naming to come)
N/A New
Imp strategy map connection and formatting
N/A New
Seamless management of dashboard content
Inc. Imp
Integrated filter framework N/A New
Calculated KPIs N/A New
Imp visualizations N/A New
Chart Web Parts N/A New
Business Intelligence Centre N/A New
Composites
Browser-based customizations Inc. Imp
Business Connectivity Services N/A New
SharePoint Designer Inc. Imp
Human workflow Inc. Imp
Form Services Inc. Imp
Visio Services N/A New
Access Services N/A New
Sandboxed Solutions N/A New
9. What are the key differences between SharePoint Foundation 2010 vs. SharePoint Server 2010?
Feature Name / Area SharePoint Foundation 2010 SharePoint Server 2010
Excel Services N/A New
Visio Services N/A New
Web analytics N/A New
Windows PowerShell Inc. Inc
Feature Name / Area SharePoint Foundation 2010 SharePoint Server 2010
Multilingual interface Inc Inc
Ribbon interface Inc Inc
Enterprise search N/A New
Performance Point services N/A New
Word automation services N/A New
Sandboxed solutions Inc Inc
Business connectivity services Inc Inc
Audience targeting Inc Inc
Mobile connectivity Inc Inc
User profiles and social data N/A New
Enterprise content management N/A New
InfoPath forms services Inc Inc
Workflows Inc Inc
Query enhancements Inc Inc
10. What are the key differences between NET vs. SharePoint?
Feature Name / Area .NET SharePoint
Creation Code need to be written even to achieve simple functionality
Lots of pre-defined web parts and elements available no need to write the code.
Time Takes time to create the code and test
Very less time required
Skilled Professionals Skilled professionals are required to create the functionality
Even novice professionals can do so easily
License Requirement Not required at the time of deployment of solution
Free versions available, but in case of extensive requirements License is required
11. What is Site collection?
SharePoint site collection is a logical grouping of multiple SharePoint site or hierarchical site structure. For e.g. Sites of various teams or departments of an organization can be grouped logically in one site collection. A site collection consists of a top-level site and one or more sites below it. Each top-level site and any sites below it in the site structure are based on a site template and can have other unique settings and content. Hence, SharePoint site collection is a hierarchical set of sites that can be managed together. Sites within a site collection have common features, such as shared permissions, galleries for templates, content types, and Web Parts, and they often share a common navigation. A sub site can inherit permissions and navigation structure from its parent site or these can be specified and managed independently. Creation of sub sites can be delegated to users of a site collection, but a service administrator must perform creation of site collections
12. What is Site? Site is a collection of web pages used to store information in an organized manner. It stores a list of documents, discussions, events, tasks, and many other types of information. Site provides controlled access to share information among users, i.e. authorize users are allowed to access the site & its elements. User can configure following elements in SharePoint site: 1. Templates: Template acts as stencils, used to create similar attribute elements. 2. Language: SharePoint has ability to create multilingual sites. Language packs are installed on the
server to translate the portal in other languages. User can select a language-specific site template while creating new site.
3. Security: User can define unique user groups and permissions for each site as well as site elements.
4. Navigation: Site navigation reflects the relationships among the sites in a site collection. User can fine-tune site's navigation experience by configuring unique navigation links in each part of site's hierarchy. Therefore, planning navigation and planning sites structures are closely related activities.
5. Web pages: Web pages in sites or site collection are used to display information. 6. Site layouts: Site Layout dictates the overall look and feel of the SharePoint site. 7. Themes: Themes specify the appearance of site in terms of Color & font. 8. Regional settings: Regional settings are specific to particular country or geography, such as locale,
time zone, sort order, time format and calendar type. 9. Search: User can make each site having unique search settings. For example, user can specify
that a particular site never appear in search results. 10. Content types: A content type defines the attributes of a list item, a document, or a folder. 11. Workflows: Workflow defines the action or series of actions that has to be performed on the
occurrence of event.
13. What is Sub Site? A sub-site is a single SharePoint site within a site collection. A sub-site can inherit permissions and navigation structure from its parent site or can be specified and managed independently.
14. What is List? A SharePoint list is a collection of records related to an entity like a student, employees, etc. Records in lists are termed as items. A list contains columns or fields that define the item data or metadata. Lists are created using a GUI interface by defining the metadata types. Once the Lists are created, it becomes very easy to add, edit, delete, and search items in it.
15. What is Document Library? A Document library allows users to easily store, upload, share, collaborate, and track documents or files. Users can also store the properties related to documents called metadata to make the documents easily searchable.
16. What is Picture library? A Picture library allows users to easily store, upload, share, collaborate and track images or digital pictures. Users can also store the properties related to images called metadata to make the images easily searchable.
17. What is Check-out? Check-out ensures that only one person can edit a document at a time. To edit a document, a user would first have to check out a document. This prevents anyone else from editing the document until that user check the document back in. During the period that the document is checked out, other users can only view a read-only version of the document.
18. What is Check-in? Check in a file means that user is uploading the modified file to the library and it is now available for edit by other users. Once the document is checked in, the document becomes available again to be checked out by someone else. In addition, all changes made by the person who checked in the document are now visible to others.
19. What is Versioning? Versioning allows updates, restoring and tracking of the items in a list or in a library when they are changed. Versioning makes use of version numbers to keep track of changes.
20. What is Site Columns?
A site column is a reusable column definition, or template that user can assign to multiple lists across multiple SharePoint sites. Site columns are useful if user organization wants to establish some consistent settings across lists and libraries.
21. What are the various built in columns available in SharePoint 2010? 1. Single line of text 2. Multiple lines of text 3. Choice (menu to choose from) 4. Number (1, 1.0, 100) 5. Currency ($, ¥, €) 6. Date and Time 7. Lookup (information already on this site) 8. Yes/No (check box) 9. Person or Group 10. Hyperlink or Picture 11. Calculated (calculation based on other columns) 12. Full HTML content with formatting and constraints for publishing 13. Image with formatting and constraints for publishing 14. Hyperlink with formatting and constraints for publishing 15. Summary Links data 16. Rich media data for publishing 17. Managed Metadata
22. What is Content Type? A content type is a reusable collection of metadata (columns), workflow, behavior, and other settings for a category of items or documents. Content types enable user to manage the settings for a category of information in a centralized and reusable manner. A content type defines the attributes of a list item, a document, or a folder. Each content type can specify properties to associate with items of its type.
23. What is rating? Rating provides user the ability to rate content (of any type, lists, documents, pages on a site, and
even content types) and stores that rating information in the database. It is an assessment or classification of content on a scale according to how well the content meets specific criteria. Ratings show an average score that can range from 1 to 100.
24. What is Audience targeting?
The content inside lists, libraries, web parts, etc., can be targeted to appear only for the users who are members of a particular group or audience. The audience can be identified via SharePoint groups, distribution lists and security groups.
25. What are views? User can use views to see the items in a list or library that are most important to user or that best fit a purpose. For example, user can create views of the files that were created most recently, of the list items that apply to a specific department, or of the files created by one person. After creating a view, it is always available when user looks at a list or library. User can create personal views and public views. A personal view is available only to user while looking at a list or library. A public view is available when anyone looks at a list or library. To create a public view, user must have permission to change the design of the list or library. User can make a public view the default view for a list or library.
26. What are the various types of views? 1. Standard This view displays list items or files like a traditional list on a Web page. Standard view
is the default for most types of lists and libraries, and user can customize it in several different ways.
2. Calendar This view displays the calendar items in a visual format that is similar to a desk or wall calendar. User can apply daily, weekly, or monthly views in this format. For example, user can create a calendar to track the team's deadlines for a project or holidays for the organization.
3. Datasheet This view provides data in a format that user can edit, such as a table in a database or spreadsheet. This view can be helpful if user need to perform large editing tasks or customization, or export data to a spreadsheet or database program. Datasheet view requires a
control or program that is compatible with Windows SharePoint Services, such as Office Access 2007, and ActiveX control support.
4. Gantt This view provides a visual view of data, with bars that track progress, if data is based on a time interval. A Gantt view can help user manage projects and see a quick overview of the data. User can use this view, for example, to see which tasks overlap each other and to visualize overall progress.
27. What is Task list?
A task list in SharePoint displays a collection of tasks that has to be performed. Users can also add columns or metadata to store additional information about the tasks.
28. What is Document Set? Document Set enables users to group multiple documents that support a single project or task, together into a single entity. All documents in a Document Set share the metadata and the entire set can be versioned. Document sets are built on SharePoint 2010 content types, and user can create multiple unique document set content types as part of their implementation.
29. What is Drop-Off Library? The Drop Off Library will be the default destination when a user tries to upload a document to this site. This is used when user does not know that where should the document be uploaded in the site. In that case, user uploads the document in this library and the document is routed automatically to the specific library.
30. What is Routing Rules List? The Routing Rules list, as its name implies, contains the rules for how a document is to be routed to its final destination. These rules are written to route the documents to their final and proper destination.
31. What is Blogs? Blogs is a type of website, usually maintained by an individual with regular entries of commentary, description of events, or other material such as graphics or video. It can be used to post ideas, observations, thoughts and expertise on which comments can be done.
32. What is Enterprise wiki? An enterprise wiki is a publishing site for sharing and updating large volumes of information across an enterprise. Enterprise wiki can be used as a central repository for large organizations to store and share unstated information.
33. What is Tagging? Tagging is the ability to tag documents that enables user to search document easily with keywords. Tags cloud webparts enable users to display tagging keywords.
34. What is Recent activity? The recent activity is a helpful way to understand what the person has been working on recently.
35. What is Survey?
Survey is used when user want to collect the responses from various people, across the organization about any event, any activity or any other thing. It is a list that allows user to collect the responses in various ways. User can ask the questions and they can answer those questions and then result can be analyzed by taking it to the excel sheet or through graphical summary or by watching all responses at once.
36. What is My site? My Site is the individual mini sites and acts as a central location to view and manage all of a user’s documents, tasks, etc. My Sites enables users to easily share information about themselves and their work. This sharing of information encourages collaboration, builds and promotes information about expertise, and targets relevant content to the people who are interested.
37. What is enterprise Metadata Management? Enterprise metadata management (EMM) is a set of features introduced in Microsoft SharePoint Server 2010 that enable taxonomists, librarians, and administrators to create and manage terms and sets of terms across the enterprise. There are two key principles in the use of metadata: 1. Use of tags: It is easy for a site to use enterprise wide tags and taxonomies, and easy for users to
apply them. 2. Application of tags in SharePoint 2010: The document libraries are configured to use metadata
as a primary navigation pivot and improves search.
38. What is Web part? Web Parts are customizable plug and play components that empower information workers to create personalized user interfaces by simply dragging and dropping them on a Web page. Web parts allow customization at both design time and run time. There are two types of web parts.
1. In-built web parts – Web parts that are included in SharePoint. Developers can drag them from web part galleries and drop them into web part zones.
2. Custom web parts – Web parts that are created by the user using visual studio is called custom web parts.
A Web Part is composed of the following entities: 1. The Web Part description file (.dwp) is a portable container of default and personalized property
values for the Web Part. 2. The Web Part assembly file (.dll) contains the logic and code for the Web Part, and is installed on
the server running Windows SharePoint Services. 3. Resource files that support the Web Part; these are also stored on the server. 4. Tables in the Windows SharePoint Services database are used to store current values of the Web
Part properties.
39. What is RSS Viewer? RSS viewer is a web part that provides a good way of adding interesting content to SharePoint site pages.
40. What is a Record Center? The Records Center is intended to serve as a central repository in which an organization can store and manage all of its records such as legal or financial documents. The Records Center supports the entire records management process, from records collection through records management to records disposition. The Records Center site template is a pre-configured site designed specifically to help organizations implement their records management and retention programs. Versioning, auditing, metadata management, eDiscovery, and customizable record routing are built-in features that can help user to manage records more effectively.
41. What is Document Center? Document Center is a site on which user can centrally manage documents in an enterprise. A large-scale library useful as an enterprise knowledge base or historical archive includes features to help users navigate, search, and manage many documents in a deep hierarchy by using a set of specialized Web Parts.
42. What is Digital asset management? SharePoint server 2010 includes a new asset library specially designed for managing and sharing digital assets such as audio, video, and other rich media files known as Digital Asset Management.
43. What is Social networking? Social Networking Connects public to MySite pages to help establish connections between colleagues with common interests.
44. What is a recycle bin in SharePoint? Whenever user will delete something, it goes to recycle bin in SharePoint. User can restore items that have been deleted from the site from the recycle bin.
45. What is Publishing feature? Publishing feature enables the delivery of content for both internal and external users. User need to turn on the Publishing feature on a site. Checked in and Checked Out feature in a Site gets enabled and if user don’t Checked-in the change version then older version of pages are shown to users .Users can then brand the site so that it has the corporate look and feel, and can enable other users to edit the corporate site within the context of the Web. On a site with the Publishing functionality turned on, user can also create a multilingual site by creating a source site and then translating the site into other languages, which can be published as separate sites.
46. What is Branding? Branding means to create and design the portal according to the organizational norms, by changing the title, logo, header, footer, and content to provide the look and feel that suite the organization. Creating custom-designed UIs, either on a traditional HTML page or in Microsoft SharePoint Server 2010, is known as branding. Branding of portals is done to achieve the unique corporate identity of an organization across the market.
47. What are Master page? Master pages are template that other pages can inherit from to keep consistent functionality. The pages that inherit from master pages are referred to as content pages. Master pages allow developers to keep consistent, reusable, web based code (html, CSS, JavaScript, etc.) at one high level place, so that the content pages can concentrate on their specific web based code. A content page refers to a master page and the ASP. Net framework merges the two pages together to make one page.
48. What are the various types of master pages? There are three types of master pages in SharePoint 2010: 1- V4.master
Default team site master page. Provides ribbon bar and other editing features using UI. 2- Default.master
Sites upgraded from SharePoint 2007 use this unless they are changed to use a v4 version. 3- Minimal.master
These trimmed-down custom master pages are commonly referred to as Starter Master Pages in SharePoint 2010.
49. What are Content pages?
Content pages implement a master page. Content pages contain an attribute, which informs the compiler that the page should be, merged with a master page. This attribute is part of the page directive tag called the MasterPageFile.
50. What is Page Layout? Page layout dictates the overall look and feel of a web page. A page layout relies on a content type to determine the kind of content that can be stored on pages. Page layout contains field controls and web part.
51. What is Site definition? Site definitions are the foundations on which all sites and user templates are built. These are the collection of XML or ASPX files. Site definition contains information of web parts, lists, libraries, features, and navigation bars to be included in the site.
52. What is Site template? A site template provides the basic component and layout of a new site created under SharePoint. A site template contains specific design information about a site, including the list that is part of the site, web part pages used in the site, the site’s themes and borders, changes to the quick launch bar,
as well as some site content (such as document libraries). Site templates are used to allow the rapid creation of websites and basic content in a SharePoint system. Following is a list of site templates available in SharePoint 2010.
Template Purpose Category in Site Collection
Category in Site
Assets Web Database
An assets database to keep track of assets, including asset details and owners.
N/A Web Databases
Basic Meeting Workspace
A site on which user can plan, organize, and capture the results of a meeting. It provides lists for managing the agenda, meeting attendees, and documents.
Meetings Meetings
Basic Search Center
A site that provides basic search functionality. The site includes pages for search results and advanced searches. Use this template if user does not require people search or publishing features.
Enterprise Search
Blank Meeting Workspace
A blank meeting site that user can customize based on requirements.
Meetings Meetings
Blank Site A blank site that user can customize based on requirements.
Collaboration Blank & Custom
Blog A site on which a person or team can post ideas, observations, and expertise that site visitors can comment on.
Collaboration Content
Business Intelligence Center
A site for presenting business intelligence data. It provides document libraries for storing documents, images, data connections, and dashboard Web Parts. It also provides lists for linking content from PerformancePoint Services.
Enterprise N/A
Charitable Contributions Web Database
A database to track information about fundraising campaigns including donations made by contributors, campaign-related events, and pending tasks.
N/A Web Databases
Contacts Web Database
A contacts database to manage information about people that team works with, such as customers and partners.
N/A Web Databases
Decision Meeting Workspace
A site on which user can track status or make decisions at meetings. It provides lists to create tasks, store documents, and record decisions.
Meetings Meetings
Document Center
A site on which user can centrally manage documents in the enterprise.
Enterprise Content
Document Workspace
A site on which colleagues can work together on a document. It provides a document library for storing the primary document and supporting files, a tasks list for assigning to-do items, and a links list to point to resources.
Collaboration Collaboration, Content
Enterprise Search Center
A site that provides the search functionality. The welcome page includes a search box that has two tabs: one for general searches and another for searches for information about people.
Enterprise Search
Enterprise Wiki A site on which user can publish knowledge that users capture and want to share across
Publishing Content
the enterprise. It provides an easy content editing experience in a single location for co-authoring content, for discussions, and for managing projects.
FAST Search Center
A site for delivering the FAST search experience. The welcome page includes a search box with two tabs: one for general searches and another for searches for information about people. User can add and customize tabs to focus on other search scopes or result types. A refinement option provides a count of each query refiner.
Enterprise Search
Group Work Site
This template provides a groupware solution that teams can use to create, organize, and share information. It includes the Group Calendar, Circulation, Phone-Call Memo, document library and other basic lists.
Collaboration Collaboration
Issues Web Database
An issues database to manage a set of issues or problems. User can assign, prioritize, and follow the progress of issues from start to finish.
N/A Web Databases
Multipage Meeting Workspace
A site on which user can plan a meeting and capture decisions and other results from the meeting. It provides lists for managing the agenda and meeting attendees. It also provides two blank pages that user can customize based on the requirements.
Meetings Meetings
My Site Host A site that hosts personal sites (My Sites) and the public People Profile page. This template has to be provisioned only once per User Profile Service Application. This template is available only at the site collection level.
Enterprise N/A
Personalization Site
A site for delivering personalized views, data, and navigation from this site collection to My Sites. It includes Web Parts that are specific to personalization and navigation that is optimized for My Sites. This template is available only at the site level.
N/A Blank & Custom
Projects Web Database
A project-tracking database to track multiple projects, and assign tasks to different people.
N/A Web Databases
Publishing Portal
A starter site hierarchy that user can use for an Internet site or a large intranet portal. User can use distinctive branding to customize this site. It includes a home page, a sample press releases site, a Search Center, and a logon page. Typically, this site has many more readers than contributors, and it is used to publish the Web pages by using approval workflows. It also restricts the rights of anonymous users so that they can see only content pages, and they cannot see SharePoint Server 2010 application pages.
Publishing N/A
Publishing Site A blank site for expanding the Web site and quickly publishing Web pages. Contributors can work on draft versions of pages and publish them to make them visible to readers. This site includes document and image libraries for storing Web publishing assets.
N/A Content
Publishing Site with Workflow
A site for publishing Web pages on a schedule by using approval workflows. It includes document and image libraries for storing Web publishing assets. By default, only sites that have this template can be created under this site. This template is available only at the site level when the Publishing Portal template is used to create the top-level site.
N/A Content
Records Center A site that is designed for records management. Records managers can configure the routing table to direct incoming files to specific locations. The site also enables user to manage whether records can be deleted or modified after they are added to the repository.
Enterprise Data
Social Meeting Workspace
A site on which user can plan social occasions. It provides lists for tracking attendees, providing directions, and storing pictures of the event.
Meetings Meetings
Team Site A site on which a team can organize, author, and share information. It provides a document library, and lists for managing announcements, calendar items, tasks, and discussions.
Collaboration Collaboration
Visio Process Repository
A site on which teams can view, share, and store Visio process diagrams. It provides a versioned document library for storing process diagrams, and lists for managing announcements, tasks, and review discussions.
Collaboration Content
53. What are the key differences between Site template and site definition?
Site Definitions Site Templates
Site Definitions are the foundations on which all sites and user templates are built. Site Definition is collection ox XML and .aspx file. Site Definitions are predefined components needs to be included when a site was created in SharePoint server. Site Definition contains information of Web Part , Lists, Features and navigation bars to be included in the site
Site template approach for SharePoint Site Creation is easier, and just requires the use of the Web interface and occasionally Microsoft FrontPage. Content can be saved with site template
Files are on disk, better performance. Files are in content database, less efficient.
Highly customizable and extensible (XML and .NET code is much more flexible than UI)
Not easily extensible (users are limited by what UI offers)
Can provision multiple webs Can only provision one web
54. What is ONET.xml?
ONET.xml file is present in TEMPLATE\SiteTemplates\XML\Onet.xml location, which defines the setup of the site definition, such as which Features to load, where the web parts go and what they will perform and which document library templates to assign and many more.
55. List all the types of custom templates in SharePoint 2010? Custom templates are of four types:
List Templates List templates contain the files, views, fields, Web Parts, and, optionally, the content that is associated with a list. Users create list templates on the Save as Template page for a list or through code, that uses the SaveAsTemplate method of the SPList class. When saved, list templates are stored in the List Template Gallery of the top-level site in a site collection, where they become available to all sites in the site collection that derive from the same site definition and language as the site on which the list was originally created
Library Templates A library template contains several types of libraries like asset library, document library, form library, record library, picture library, wiki page library. Each type of library displays a list of files and key information about the files, such as who was the last person to modify the file, which helps people to use the files to work together.
Page Templates Page template contains web part page, publishing page, and a normal html page. These templates are easily customizable and are used for sharing content.
Site Templates Site templates contain the same type of data as list templates, but site templates include data for the entire site. Like list templates, site templates may also include the content of the site.
56. What is Theme? SharePoint theme represents a collection of graphics and cascading style sheets that can modify how a website looks. Using themes, we can change font and color scheme of the sites.
57. What is Navigation in SharePoint 2010?
Site navigation provides the primary interface for site users to move around on the sites and pages on the site. Microsoft SharePoint Server 2010 includes a set of customizable and extensible navigation features that help orient users of the site so they can move around on its sites and pages.
58. What are the various options for Navigation available in SharePoint 2010? 1. Navigation controls on master pages
Top link bar navigation Quick Launch navigation Breadcrumb navigation Tree view navigation Metadata navigation
2. Navigation controls on page layouts Summary Links Table of Contents Content Query
3. Navigation Web Parts
Categories
Site Aggregator
Site in Category
Tag Cloud The following navigation Web parts are available only on Publishing sites:
Summary Links
Table of Contents 59. What is Ribbon interface?
Ribbon Interface act as the UI enhancement in the product. It provides the commands to be executed in the form of Icons and tabs.
60. What is a workflow?
A workflow consists of a sequence of connected steps. It is a depiction of a sequence of operations, declared as work of a person, a group of persons, an organization of staff, or one or more simple or complex mechanisms.
61. Explain .Net Workflow and SharePoint workflow? 1. .Net Workflow: Windows Workflow Foundation (WWF) is a new programming framework
introduced in .NET 3.0 for creating reactive programs. A reactive program typically represents a set of procedures or instructions used to capture and automate a specific business process. Windows Workflow Foundation supports publishing a workflow as an ASP.NET Web service on a Web server or server farm running ASP.NET on Internet Information Services (IIS) 6.0. Because Windows Workflow Foundation Web service support is based on ASP.NET 2.0, it inherits most of the features of a standard ASP.NET Web service.
2. SharePoint Workflow: SharePoint workflows are built on top of WWF. WSS extends the WWF. WSS extends the WWF by introducing the concept of a workflow template. The main purpose of the workflow template is to integrate WWF programs into WSS so that they can be installed, configured and parameterized for use. A workflow template is created by adding a Workflow element to a feature that is scoped to the level of the site collection.
62. What is Single sign-on?
Single Sign-on allows users to log on to a variety of applications with the single username and password and user has to enter the details only once for all the applications.
63. What is ULS Logging?
ULS Logging captures and writes events to trace logs.
0.2 Customization Questions 64. What is Sandbox solution?
When user writes custom code, the code is not trusted, its failure can influence entire site. So the sandbox solution concept is used. In that case, program is only written for particular site & solution is uploaded in the same site. The solution size limit is decided at the time of site creation & if size increases or code shows bad performance then it will be easy for the administrator to stop the working of solution.
65. What can be deployed as a Sandbox solution in SharePoint 2010?
Users can deploy the below four things as sandboxed solutions: 1. WebParts. 2. Event Receivers. 3. List Definitions. 4. Workflows.
66. What are the Visual Studio 2010 Tools for SharePoint?
Visual Studio 2010 includes SharePoint-specific project types and project item types, and includes powerful packaging, deployment, and debugging features that help increase the efficiency as a SharePoint 2010 developer. Some of the Templates available are:
1. Visual Web Part project template. 2. List definition template. 3. Content Type template. 4. Empty Project template. 5. Event Receiver template. 6. Some workflow template. 7. the Site Definition template
And many more....
67. What is SharePoint Designer? SharePoint Designer is a specialized HTML editor and web design freeware for creating and modifying Microsoft SharePoint sites and web pages. It is a part of Microsoft SharePoint family products.
68. How does Client object model works?
When developer use SharePoint client API’s to perform a specific task, the SharePoint 2010 managed client object model bundles up these uses of the API into XML and sends it to the server that runs SharePoint Foundation. The server receives this request, and makes appropriate calls into the object model on the server, collects the responses, forms them into JavaScript Object Notation (JSON), and sends that JSON back to the SharePoint Foundation 2010 managed client object model. The client object model parses the JSON and presents the results to the application as .NET Framework objects (or ECMAScript objects for ECMAScript).
69. How many types of Client Object model extension are available in 2010 and when would a
developer use one or the other. To develop rich client side solutions, three set of client-side APIs has been introduced in the Microsoft.SharePoint.Client namespace. The three APIs are targeted for three different types of clients. 1. .Net Managed applications – These are used when we have to create console applications or
window applications, web applications which are not running inside SharePoint Context. 2. For Silverlight applications 3. ECMAScript – It is a client object model extension for using with JavaScript or JScript. This is used
for creating applications, which are hosted inside SharePoint. For example, web part deployed in SharePoint site can use this JavaScript API for accessing SharePoint from browser using JavaScript.
70. How does user access ECMAScript object model API’s?
The ECMAScript library is available in a number of JS files in the LAYOUTS folder. The main file among number of .js files is SP.js. When developer includes this file in the APSX page using a ScriptLink control, all other required JS files are loaded automatically. By linking SP.js to the page, the SP namespace is registered. SP is the SharePoint namespace that contains all objects. For debugging purposes, every js file also has a ‘debug’ equivalent in the same folder.
71. What are the Authentication methods for the client object model application?
A developer can use three authentication options while working with the Client Object Model in SharePoint 2010: 1. Anonymous 2. Default 3. FormsAuthentication Developer can specify clientContext.Authentication = Anonymous\Default\FormsAuthentication, If developer do not choose an authentication method in the code, the application will by default start using the client’s Windows Credentials (DefaultCredentials).
72. How can a developer write efficient and better performing client object applications? Developer can always use Lambda expressions in their queries to return only specific properties that will be used in the block. Developer can also use LoadQuery() method and specify multiple levels of properties to load for e.g. while returning specific properties of the lists using LoadQuery(), developer can also specify the fields to return from each list to optimize the data access.
73. What is difference between Load() and LoadQuery() methods? Load method populates the client object directly with what it gets data from the server i.e. a collection object like ListItemCollection etc. but LoadQuery returns the data as a completely new collection in IEnumerable format. Other major difference is that the Collections that user load using the Load() method are eligible for garbage collection only when the client context variable itself goes out of scope whereas, in these collections go out of scope at the end of IEnumerable<List> list.
74. What is the purpose of calling clientContext.ExecuteQuery()?
ExecuteQuery gives developer the option to minimize the number of roundtrips to the server from the client code. All the components loaded into the clientcontext are executed in one go.
75. What is REST? How it is used in SharePoint 2010? REST (Representational State transfer) is a protocol (powered by ADO.NET services) which is used for getting data out of SharePoint via URL. It is mostly used to access data from SharePoint even when user is not in the SharePoint context.
76. What data type does REST return? REST does not return an object of type SharePoint Site\List. Instead, it returns an XML output.
77. What is the GAC? Global Assembly Cache folder on the server hosting SharePoint. Users place their assemblies here for web parts and services.
78. What is CAML? CAML stands for Collaborative Application Markup Language and is an XML-based language that is used in Microsoft Windows SharePoint Services to define sites and lists, including, for example, fields, views, or forms, but CAML is used to define tables in the Windows SharePoint Services database during site provisioning.
79. Why would a developer use LINQ over CAML for data retrieval?
Unlike CAML, with LINQ to SharePoint provider, developers are working with strongly typed list item objects. For example, an item in the Announcements list is an object of type Announcement and an item on a Tasks list is an object of type Task. Developer can then enumerate the objects and get the properties for their use. In addition, developer can take benefit of LINQ syntax and the LINQ keywords built into C# and VB for LINQ queries.
80. What are the Disadvantages of Using LINQ in the Code? LINQ translates the LINQ queries into Collaborative Application Markup Language (CAML) queries thus adding an extra step for retrieving the items.
81. What does AllowUnsafeUpdates do? If developer is trying to modify Windows SharePoint Services data using code, developer may need to allow unsafe updates on the Web site, without requiring a security validation. For this, developer needs to set AllowUnsafeUpdates property to true.
82. What does RunWithElevatedPrivileges do? There are certain object models that call another model that require site-administration privileges. To bypass access-denied error, we use RunWithElevatedPrivileges property when a nonprivileged user initiates request. We can successfully make calls into the object model by calling the RunWithElevatedPrivileges method provided by the SPSecurity class.
83. How is a Content Type created?
We can create column and content types in three ways: 1. Using the SharePoint Foundation user interface. 2. Using the SharePoint Foundation object model. 3. Deploying a Feature that installs the content type based on an XML definition file.
84. How is a Content type deployed?
Content Type can be deployed and associated with list using feature. Inside the Feature, the feature.xml file contains references to all the element manifests within that Feature. Content type definitions are element manifests.
85. What is the scope of a content type?
A site content type becomes available to lists and document libraries within the site in which the content type is created and to the lists and document libraries in any child site.
86. What is an ancestral type and what does it have to do with content types?
An ancestral type is the base type that the content type is deriving from, such as Document (0x0101). The ancestral type will define the metadata fields that are included with the custom content type.
87. Can a list definition be derived from a custom content type? Yes, a list definition can derive from a content type, which can be seen in the schema.XML of the list definition in the element.
88. When creating a list definition, how can a user create an instance of the list? User can create a new instance of a list by creating an instance.XML file
89. What is ghosted page?
A ghosted page is a page in SharePoint website which is not stored in the database instead it reference to a file which exists in the server’s file system. These reference files are common for all the website/site collection within that SharePoint server, i.e., if user modify a reference file then that change will reflect in all the websites/site collections within that SharePoint server automatically.
90. What is Un-ghosted page? All the pages in a SharePoint website, which are stored in the content database, are referred to as un-ghosted pages. All the un-ghosted pages are specific to that SharePoint website only, i.e., changes done in an un-ghosted page will not reflect in other websites within that SharePoint server.
91. What are the types of pages available in SharePoint 2010?
There are two types of pages that are available in SharePoint, which are as follows: 1- Application page. 2- Site page.
92. What are application pages?
An application page is the best type of page to create, when there is need to add custom code. Application pages are stored on the file system of the front-end Web server in the %Program Files\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\LAYOUTS directory. They allow in-line code without restriction. They cannot use dynamic Web Parts or Web Part zones or be modified using SharePoint Designer. Application pages are not tracked in the content database. They never run in safe mode. Since application pages must be deployed inside the SharePoint Root directory hence, they cannot be used within sandboxed solutions.
93. When to use application pages? 1. These are generally used as administrative pages. 2. These pages can be used where we want to capture data. 3. These pages can be used for configuration pages. 4. These pages can be used where we want to restrict the users to customize the page. 5. Application pages can be used with any site or site collection or web application on same server. 6. These pages are used when we want to add custom code or inline code to the page.
94. List the folders and files added while creating an application page?
When developer creates an application page, Visual Studio adds the following folders to the project:
Folder Description
Layouts Maps to the _layouts virtual directory of the SharePoint file system.
Layouts subfolder
Contains the files that make up the application page. By default, this folder has the same name as project. This folder can be renamed at any time. At the time of running of the project, Visual Studio deploys this folder to the _layouts virtual directory of the SharePoint file system.
Visual Studio adds the following files to the project:
95. What is the difference between Site page and application page?
96. Can web parts and web zones be added to an Application page? No, since Application pages does not support edit mode so web part zones and web parts cannot be added using SharePoint. However, static web parts can be added by editing then in Visual Studio, as web parts are nothing but controls with some extra functionality.
97. How to edit an Application page? An application page can only be edited either by opening the page in Visual Studio or in Notepad. However, in both the ways, the application page needs to be deployed again for further usage.
98. What is difference between an Application page and a Custom aspx page in SharePoint 2010? Application Page – Developer would typically use an application page when developer need some content that is merged with SharePoint master page. A master page enables application pages to share the same appearance and behavior as other pages on a site. Application page generally is deployed in _layouts and inherits the look and feel of the site that developer is using. A Custom .net aspx page on the other hand would need content and master page tags in the page to make it inherit the look and feel of the site.
99. If a page with some code has to be deployed, which type of page should be selected? Developer must select to deploy an application page with code as it is much easier and built-in templates are available in VS 2010.
File Description
ASP.NET page file (.aspx)
Contains XML markup that defines the page.
Application page code file
Contains code behind the application page. Add code that handles events to this file.
Application page designer code file
Contains code that is generated by the designer. Do not directly edit this file.
S. No Site Pages Application Pages
1 Site pages are stored in the Content database of SharePoint.
Application pages are stored in the server’s file system.
2 Site pages can be edited by using SharePoint Designer tool
SharePoint Designer tool cannot be used with application pages.
3 Site pages are used within Sandboxed solutions.
Application pages cannot be used within sandboxed solutions.
4 A site page can be customized and modified by end user.
An Application page cannot be customized and modified by end user, instead a developer is required.
5 Site pages cannot contain inline code. Applications pages can contain inline code.
100. How to create a custom master page?
There are multiple ways to create custom master page files 1- By copying and editing existing master page. 2- By SharePoint Designer. 3- By editing minimal.master using editor.
101. How to apply a custom master page?
There are two ways to apply a custom master page 1. Custom Master Page can be deployed using SharePoint Feature by which master page gets
uploaded to the master page gallery. 2. Custom master page can be uploaded directly in master page gallery library and apply the same
master page using site and system master page option in Site Settings page by selecting Master Page option.
102. Can developer use the custom master page with the application pages in SharePoint 2010? With 2010, developer can now set whether the pages under _Layouts use the same Master Page as the rest of the site. Developer can enable or disable this functionality through the web application settings in Central Administration. This however, is not applicable to the custom application pages. If developer wants the custom application page to inherit the site master page, he must derive it from Microsoft.SharePoint.WebControls.LayoutsPageBase class.
103. How to link the custom CSS file in the master page?
Custom CSS files can be linked to the master pages with the help of a class called Sharepoint:CssRegistration.
104. What is the best method on working with CSS? The best method to work with css is to create a new css file, store the file in any document library, and then provide the alternate CSS URL to the site by navigating to the master page option in the Look and Feel.
105. If a developer creates a new CSS file then where should the file be stored? The css file can be stored in two locations, either in the document library or in the layouts folder.
106. How will user deploy a CSS file in SharePoint 2010? The most preferable way to deploy files in SharePoint is by using the solution package. In SharePoint 2010, developer can create an empty project with VS 2010 and then add a new SharePoint Mapped folder in it. This will give the desired location in 14 hive where developer can then add a file to deploy.
107. If multiple css files are used in the same master page then how can a developer order the files to be applied to the master page? The ordering of the css files can be done with the help of the CssRegistration class. Suppose if there are four css files to be linked namely 1.css, 2.css, 3.css and 4.css then the “after” attribute of the CssRegistration class can be used. Firstly, apply 1.css and use after attribute with value Corev4.css and then link 2.css file and use after attribute with value 1.css and so on.
108. How to create custom Themes? Custom themes can be created for SharePoint by two ways. 1- Creating a theme in Microsoft PowerPoint. 2- Themes can also be created with the help of Visual Studio.
109. What does safe control means?
SharePoint application runs in Full Trust mode. For Web Parts to work properly in SharePoint Sites, its entry in web.config file assures Full Trust to SharePoint Site as it is registered in the file as safe.
110. What is Custom Control? Custom controls have a file extension as “.ascx”, and are shared across web applications. There is no visual designer for creating custom controls hence, user cannot drag and drop custom controls.
111. What is User Control? User controls are created using a designer’s tool, having file extension as “.ascx”. User controls cannot be shared across web applications.
112. How to use user control in SharePoint? Suppose there is a user control MyControl.ascx. This file has to be deployed to the SharePoint server along with its binary. If developer is using a Smart Part, the ascx file must be copied to a folder called User Controls located in the root of the web sites folder (by default c:\inetpub\wwwroot\wss\VirtualDirectories\80. I recommend creating of own web part to host the user control that will work with any application. SharePoint itself puts all user controls in the TEMPLATES folder in the 14 hive (C:\Program Files\Common Files\Microsoft shared\Web Server Extensions\14).
113. What is a web part zone? Web part zones are the zones where the web part resides in and helps categorizing the web parts while designing a page.
114. What is Content Editor Web part? Content Editor Web part is a universal plug in adapter. It is used to connect SharePoint pages to the rest of the world. User can use content editor web part to add html/CSS/JavaScript, embed videos or widgets, formatted text, tables, hyperlinks, images, and display content from other SharePoint sites to a web part page.
115. How can a user add content to the content editor web part? There are three ways to add content to the content editor web part. 1. Rich Text Editor: It allows user to add formatted text automatically without prior knowledge of
HTML syntax. 2. Source Editor: The source editor is a plain text editor and it is intended for users who are familiar
with HTML syntax. It allows user to add scripts, HTML and styles to a web part page. 3. Content link: It is used to link existing content by entering a hyperlink to a text file that contains
HTML source code.
116. What is Content query web part? Content query web part displays a dynamic set of items based on a query that user build by using a web browser. The query displays selected items. User can set presentation options to determine how these items are displayed on the finished page.
117. How to create a web part? A web part can be created through visual studio 1. Using visual studio template for SharePoint web parts. 2. Add console application, add xml and aspx page, and then deploy.
118. How to debug a web part? A web parts can be debugged in visual studio using following steps. 1. Set the break points 2. Attach the ASP.Net w3wp.exe process 3. Debug by tracing, change trace level in web.config
< Trace enabled ="true" pageOutput = "true"/>
119. How to deploy a web part?
We can deploy a web part using three methods 1. Using Feature 2. copy dll in bin(wss directory) or Assembly(window) and upload web part file in web part gallery
and then populate 3. Using Windows PowerShell.
120. How to deploy a WebPart Using Windows PowerShell?
At the Windows PowerShell command prompt (PS C:\>), type the below command : Install -SPWebPartPack -LiteralPath “FullPathofCabFile” -Name “Name of WebPart”
121. Can a modal dialog be displayed from a webpart? Yes, a modal dialog can be displayed from within a webpart code since it is a JavaScript block that can be registered on the page.
122. While creating a Web part, which is the ideal location to initialize the web controls? Override the CreateChildControls() method to include web controls. Developer can control the exact rendering of the controls by calling the Render method.
123. How will developer use WebParts or other solutions created in SharePoint 2007 in SharePoint 2010? In SharePoint 2010 the 12 hive is now replaced by 14 hive, so developer will rewrite and recompile any code that refers to files and resources in “12″ hive. In addition to developer must recompile custom code written for Windows SharePoint Services 3.0 and Office SharePoint Server 2007 that does not run on IIS.
124. What is SharePoint designer workflow? One of the most powerful features of SharePoint designer is the ability for non-programmers to easily create business tailored workflow to improve business process management. SharePoint designer workflow is an easy, cheap, and somewhat limited entry point to workflow development. They are easy because most end users and administrators can become workflow developers without too much training.
125. Can Developer modify the Out-of-Box workflows in SharePoint 2010? In SharePoint 2010, developer has an option to customize the Out-of-Box workflows. The four most popular workflows in SharePoint Server 2010 — the Approval, Collect Feedback, Collect Signatures, Publishing Approval workflows — have been completely rebuilt as declarative reusable workflows, meaning that they are now fully customizable in SharePoint Designer 2010.
126. When is workflow forms created? And how to customize it? SharePoint Designer 2010 automatically generates the forms, but user can customize them by going to the settings page for the workflow, in the Forms section, click the form user want to customize. Workflow forms are either InfoPath or ASP.NET pages. They are stored on the SharePoint site with the workflow source files.
127. Where are the InfoPath forms published in SharePoint?
InfoPath forms are published in the Manage Form Template in Central Administration site or to a list or a form library in a site collection.
128. What is Features in SharePoint? Feature is a functional component, which contains various SharePoint elements. Features have their own receiver architecture, which allow user to trap events such as when a feature is installed, uninstalled, activated, or deactivated. User can define several element types in features like menu command, template, page instance, event handler, workflow, list instance, list definition, and link commands. Features in SharePoint allow users to easily package up functionality that can be deployed and installed across the server farm. Features provide a mechanism by which user can package the
files that a solution needs, such as content types, Web Parts, lists, and site definitions, master page. Inside the Feature, the feature.xml file contains references to all the element manifests within that Feature, pluggable behavior for installing or uninstalling Features within a deployment, pluggable behavior for activating or deactivating Features at a given scope, scoped property bag for storing data required by a Feature within its scope.
129. What is the scope of feature activation? Feature can be activated or deactivated at various scopes throughout a SharePoint instances, such as farm level, web application level, site collection level, web level, etc.
130. What is the difference between feature definition and feature instance? The feature definition is the set of source files in the Visual Studio 2010 project that is deployed using a solution package. Once deployed, a feature definition is a set of template files and components that reside on each front-end Web server. A feature instance is what is created when a user activates the feature definition.
131. What are the minimum files required for a feature? Every feature directory should contain at least one file namely feature.xml and should be placed in the root of the directory. But a feature directory can contain one or more xml files as well as resource files such as image files, css files or js files. A feature.xml file contains attributes like Id, Title, Description, Version, Scope, Hidden, and ImageURL.
132. What is hidden attribute in a feature? Hidden attribute will take the value of True or False. If it is set to False, after installation the feature definition can be seen by administrators only.
133. What is Elements.xml file in Feature in SharePoint 2010? Elements.xml file contains the actual feature element. It can contain elements like ListInstance, Field, ContentType, ListTemplate, Workflow, WorkflowActions etc.
134. What is Feature Receiver in SharePoint 2010, its base class along with the methods that needs to be override? A Feature Receiver allows user to write event handlers in a managed programming language such as C# or Visual Basic. These event handlers are executed during feature specific events such as feature activation and feature deactivation. The base class is SPFeatureReceiver. The methods to be overridden are: FeatureActivating, FeatureActivated, FeatureDeactivating,FeatureDeactivated etc.
135. How are features created? Feature can be created by creating a new Empty SharePoint project from VS 2010 and then add new item named feature. After user has created the project, right click on the "Features" node in "solution explorer" and "add feature". This will create a new feature with the title "Feature1". User can rename it or leave it as it is. On double clicking the name of the feature, the properties of the feature will appear, such as title, description and the scope. Right click on the "feature1" in solution explorer and click on "Add feature Receiver" to add it. After the file has been created, uncomment (as required) the "on activate" and/or “on deactivate" and put code in there.
136. How can a feature be deployed? There are two ways for deploying a feature 1- WSP builder via Visual Studio and activate solution from central admin. 2- Using STS Command, firstly install and then activate.
137. Where the feature receiver file needs to be deployed? The feature receiver file needs to be deployed in Global Assembly cache (GAC).
138. What is a Manifest.xml File in SharePoint 2010?
Manifest.xml file contains the Meta data of a solution package. At the time of deployment, SharePoint inspects manifest.xml file to determine which template files it needs to copy into the SharePoint root directory.
139. Can a page be displayed as a modal dialog? Yes, any page can be displayed as modal dialog. A Modal dialog takes options as a parameter and developer can specify the URL for any page usually saved in _layouts.
140. What is New in SPALerts? In SharePoint 2007, alerts were sent only through e-mails, but in SharePoint 2010, users can also send an alert to mobile devices as SMS Message. A New property DeliveryChannels is introduced to indicate, whether the alert is delivered as E-mail or as an SMS Message.
0.3 Advanced Questions
141. What is Claims based authentication? Claims based authentication provides a new authentication model that supports any corporate identity system like active directory domain services, LDAP-based directories, application-specific databases, etc. The purpose of claims-based authentication is to make authentication simple for all users. For example, user may want to setup a SharePoint site that is accessible by both internal and external users, such as clients. Internal users might use one mechanism such as Windows-based authentication and external users might want to use another method, such as forms-based authentication. No matter what authentication protocol was used, the SharePoint application gets a signed set of claims so it has the information it needs about the user.
142. What is Classic-mode authentication? In the classic authentication mode, only mixed-mode authentication is available. In mixed-mode authentication, a single SharePoint web application has to be extended to additional IIS applications with different URLs and authentication providers. The same content is used for the different URLs, but the different authentication providers can change the access users have, and their permissions.
143. Which type of IP Addresses does SharePoint 2010 support?
SharePoint 2010 Products support the following environments:
Pure IPv4 environment
Mixed IPv4 and IPv6 environment
Pure IPv6 environment
144. List the steps how SharePoint interacts with IIS? Steps of SharePoint interaction with IIS are as follows: 1. User sends a request over the internet 2. The HTTP Protocol Stack (HTTP.sys) intercept the request and passes it to the Svchost.exe 3. Svchost.exe contains the Windows Activation Services (WAS) and the Worldwide Web Publishing
Service (WWW Service) 4. WAS requests configuration information from the configuration store, applicationHost.config.
This maps virtual directories to physical directories. 5. WWW Service receives configuration information, such as application pool and site configuration 6. WWW Service uses the configuration information to configure HTTP.sys 7. WAS starts a worker process for the application pool to which the request was made 8. Authentication is done and Request comes in for an ASP.NET Page. 9. The request is given to the SharePoint14Module. 10. The page handler is unable to find a precompiled version of the page class on disk, so it must grab
the file and give it to the ASP.NET engine for parsing. 11. The SharePoint14Module contacts either the file system or the content database for the
appropriate page class information. 12. The ASP.NET Page engine parses the file and generates a page class.
13. The page class is compiled into a .NET assembly and cached on the disk. 14. An instance of the requested page’s class is created. 15. The response is generated from the requested page class is sent back to the original caller.
145. What is the difference between 32-bit hardware and 64-bit hardware and software?
The terms 32-bit and 64-bit refer to the way a computer's processor (also called a CPU), handles information. The 64-bit version of Windows handles just double amounts of data from a 32-bit system.
146. What is a SharePoint Farm? A SharePoint farm is a set of one or more server computers working together to provide SharePoint functionality to clients in terms of executing SharePoint project or solution.
147. How to install or deploy SharePoint 2010? SharePoint installation/deployment scenarios can be classified as:
1. Standalone Installation: Most of the small companies prefer standalone installation scenario. This scenario enables user to install, SharePoint and SQL database on one physical server.
2. Server Farm Installation: Most of the mid or large size, companies prefer farm installation scenario. The server farm installation can be performed as:
Complete Installation: Add all the components with ability to add more as per need
Standalone : Install all the components on single server[web server/application server/database server]
148. Explain Small, Medium and large server farm? 1. A small server farm typically consists of at least two Web servers and a database server. One of
the Web servers hosts the Central Administration site and the other handles additional farm-related tasks, such as serving content to users. The small farm can be scaled out to three tiers using a dedicated application server in response to the number of users, the number of content items, and the number of services that are required.
2. A medium server farm typically consists of two or more Web servers, two application servers, and more than one database servers. It is recommended that user should start with the preceding configuration and then scale out to accommodate the workload placed on the servers.
3. A large server farm can be the logical result of scaling out a medium farm to meet capacity and performance requirements or by design before a SharePoint Server solution is implemented. A three-tier topology environment typically uses dedicated servers on all the tiers. Additionally, these servers are often grouped according to their role in the farm. For example, all client-related services can be grouped onto one or two servers and then scaled out by adding servers to this group as needed in response to user demand for these services.
149. What are the minimum Hardware requirements to install SharePoint 2010?
To install SharePoint below mentioned is the minimum recommended hardware configuration.
Component Minimum requirement
Processor 64-bit, four cores for small deployments 64-bit, eight cores for medium deployments
RAM 8 GB for small deployments
16 GB for medium deployments
Hard disk 80 GB for system drive
Hard disk space is dependent on the size of user SharePoint content.
150. What are the minimum Software requirements to install SharePoint 2010?
The requirements in the following tables apply to single server with built-in database installations and server farm installations that include a single server and multiple servers in the farm. Database requirements
Environment Minimum Requirement
Database server in a farm
One of the following:
The 64-bit edition of Microsoft SQL Server 2008 R2.
The 64-bit edition of Microsoft SQL Server 2008 with Service Pack 1 (SP1) and Cumulative Update 2.
The 64-bit edition of Microsoft SQL Server 2005 with Service Pack 3 (SP3).
Single server with built-in database
The 64-bit edition of Windows Server 2008 Standard, Enterprise, Data Center, or Web Server with SP2, or the 64-bit edition of Windows Server 2008 R2 Standard, Enterprise, Data Center, or Web Server.
Front-end requirements
Environment Minimum Requirement
Front-end Web servers and application servers in a farm
The 64-bit edition of Windows Server 2008 Standard, Enterprise, Data Center, or Web Server with SP2, or the 64-bit edition of Windows Server 2008 R2 Standard, Enterprise, Data Center, or Web Server.
Client computer A supported browser
151. What does the preparation tool installs before installing SharePoint 2010? The preparation tool installs the following prerequisites:
Web Server (IIS) role
Application Server role
Microsoft .NET Framework version 3.5 SP1
SQL Server 2008 Express with SP1
Microsoft Sync Framework Runtime v1.0 (x64)
Microsoft Filter Pack 2.0
Microsoft Chart Controls for the Microsoft .NET Framework 3.5
Windows PowerShell 2.0
SQL Server 2008 Native Client
Microsoft SQL Server 2008 Analysis Services ADOMD.NET
ADO.NET Data Services Update for .NET Framework 3.5 SP1
A hotfix for the .NET Framework 3.5 SP1
Windows Identity Foundation (WIF)
152. What is the directory structure created during SharePoint installation? The directory created while installing SharePoint 2010 is C:\Program Files\Common Files\Microsoft Shared\web server extension\14 1. ADMISAPI 2. BIN 3. CONFIG 4. HCCab 5. Help 6. ISAPI 7. LOGS
8. Policy 9. Resources 10. TEMPLATE – Sub Directories (1033, Admin, FEATURES, LAYOUTS, IMAGES, PAGES, Themes, SQL,
XML, ControlTemplates, Document templates, IDENTITYMODEL, Site Template, GLOBAL). 11. UserCode 12. WebClients 13. WebServices
153. What has Changed in SharePoint 2010 Object model?
Microsoft has replaced the “12 hive” structure that we had in SharePoint 2007 with “14 Hive” structure in 2010. It has apparently added four new folders to its hive. The Folders are:
1. Policy 2. UserCode 3. WebClients 4. WebServices
154. List all the databases created at the time of installing SharePoint?
1. Secure Store database - The Secure Store service application database stores and maps credentials, such as account names and passwords. Prefixed with "Secure_Store_Service_DB_".
2. State database - The State service application database stores temporary state information for InfoPath Forms Services, the chart Web Part, and Visio Services. Prefixed with "StateService".
3. Web Analytics Staging database - The Staging database temporarily stores un-aggregated fact data, asset metadata, and queued batch data for the Web Analytics service application. Prefixed with "WebAnalyticsServiceApplication_StagingDB_"
4. Web Analytics Reporting database - The Reporting database stores aggregated standard report tables, fact data aggregated by groups of sites, date and asset metadata, and diagnostics information for the Web Analytics service application. Prefixed with "WebAnalyticsServiceApplication_ReportingDB_"
5. Search service application Administration database - The Administration database hosts the Search service application configuration and access control list (ACL), and best bets for the crawl component. This database is accessed for every user and administrative action. Prefixed with "Search_Service_Application_DB_".
6. Search service application Crawl database - The Crawl database stores the state of the crawled data and the crawl history. Prefixed with "Search_Service_Application_CrawlStoreDB_'.
7. Search service application Property database - The Property database stores information that is associated with the crawled data, including properties, history, and crawl queues. Prefixed with "Search_Service_Application_PropertyStoreDB_"
8. User Profile service application Profile database - The Profile database stores and manages users and associated information. It also stores information about a user's social network in addition to memberships in distribution lists and sites. Prefixed with "User Profile Service Application_ProfileDB_".
9. User Profile service application Synchronization database -The Synchronization database stores configuration and staging data for use when profile data is being synchronized with directory services such as Active Directory Prefixed with "User Profile Service Application_SyncDB_".
10. User Profile service application Social Tagging database - The Social Tagging database stores social tags and notes created by users, along with their respective URLs. Prefixed with "User Profile Service Application_SocialDB_".
11. Managed Metadata database - The Managed Metadata service application database stores managed metadata and syndicated content types. Prefixed with " Managed Metadata Service_".
Enterprise edition installation adds two more databases: 1. Performance Point service application database - The Performance Point service application
database stores temporary objects, persisted filter values, and user comments. Name Prefix "PerformancePointServiceApplication_.”
2. Word Automation Services database - The Word Automation Services database stores information about pending and completed document conversions.Name Prefix "WordAutomationServices_..."
155. What are the various functions performed by Central Administration?
Central administration is a graphical interface utility to perform various functions related to SharePoint. These functions are classified as: 1. Application Management: Application Management enables user to create site collection,
manage web application, service application and content database. 2. System Setting: System setting enables user to manage server, services and farm features. It also
enables to configure alternate access mapping. 3. Monitoring: Monitoring enables user to review problems and solutions, web analytics report and
check Job status. 4. Backup and restore: Backup and Restore enables user to perform backup, Restore from a backup
and a site collection backup. 5. Security: Security enables user to manage the farm administrators group and Configure service
accounts. 6. Upgrade and Migration: Upgrade and Migration enables user to convert farm license type, Check
product and patch installation status And Check upgrade status 7. General Application Settings: General Application Settings enables users to Configure send to
connections, Configure content deployment paths and jobs Manage form templates 8. Configuration Wizard: Configuration provides various wizards to perform configuration tasks.
156. What are the various kinds of lists available in SharePoint 2010?
1. Predefined lists: SharePoint provides a set of built-in list templates that can be used directly and customize them as needed. For example:
Announcement list
Calendar
Tasks list
Events list
Links list
Contacts list
Discussion board
Survey
Issue tracking
Project Tasks
Status List 2. Custom lists: In addition to list templates, user can create a customized list to suit specific needs.
This is done through by custom list. The custom list is actually just another list template like those just mentioned above, but its formatting is less complex.
157. What are the security improvements in SharePoint 2010? In SharePoint 2010 a variety of security methods have been introduced. 1. Claims-Based Authentication - Claims based authentication is based on identity and trust. 2. Code Access Security - in which user can specify their own code access
security (CAS) policy for the web parts. 3. Sandbox Solutions - Sandbox Solutions which when deployed to the server, SharePoint runs in a
special process that has limited permissions. 4. Cross-Site Scripting - Introduced to prevent Cross - Site Scripting (XSS) attacks
158. What is Web solution package (WSP)?
Web solution package is a cabinet file that contains, site and features definition, web part file, templates, assemblies, and code access security policies. It contains a web manifest that defines the list of features, site definitions, resource files, web part files, and assemblies to process when the solution is deployed. The directory structure within the cabinet file dictates the resulting structure on the web front-end computer. WSP creates a file with extension “.WSP”.
159. What Changes are made in SharePoint 2010 to enforce Referential Integrity?
In SharePoint 2010, Referential Integrity is enforced by using two options available with Look-up columns. While creating a Look-up column, user has two options: 1. Restrict Delete 2. Cascade Delete these options define a relationship between the Look-up list and the list containing the look-up Column.
160. List all the web parts available is SharePoint Server 2010 and Foundation 2010?
Category List of web part
Lists & Libraries List view web part
Authoring Content Editor - Foundation · Image Viewer – Foundation · Media Web Part · Page Viewer - Foundation · Silverlight Web Part - Foundation
Business data Business Data Actions ,· Business Data Catalog Filter ,· Business Data Item ,· Business Data Item Builder · Business Data List ,· Business Data Related List ,· Key Performance Indicators ·,KPI Details ·,Visio Graph Service
Content roll up Chart Viewer , Content Query , HTML Form Web Part - Foundation , iView , Picture Library Slideshow Web Part - Foundation , RSS Viewer, What’s Popular – pick from content, search queries, or search results; XML Viewer – Foundation
document Document ID Lookup , Document Set Contents , Document Set Properties , Relevant Documents - Foundation
filters Choice Filter ,· Current User Filter ,· Date Filter · Filter Actions · Page Field Filter · Query String (URL) Filter · SharePoint List Filter · SQL Server Analysis Services Filter · Text Filter
My information · My Calendar · My Contacts · My Inbox · My Mail Folder · My Tasks
Office Client Excel Web Access ,· InfoPath Form Web Part.WSRP Viewer
Navigation Categories · Site Aggregator · Sites in Category · Summary Links · Table of Contents · Tag Cloud
People Contact Details · Profile Browser · Site Users - Foundation · User Tasks - Foundation
Performance Point Performance Point Filter · Performance Point Report · Performance Point Scorecard · Performance Point Stack Selector
Search Advanced Search Box · Dual Chinese Search · Featured Content · Federated Results · People Refinement Panel · People Search Box · People Search Core Results · Refinement Panel · Related Queries · Search Action Links · Search Best Bets · Search Box · Search Core Results · Search Paging· Search Statistics· Search Summary · Top Federated Results
Miscellaneous Chart Web part
161. List the various ways to create a workflow? There are three ways by which a workflow can be created: 1- Visual Studio.
2- Microsoft Visio. 3- SharePoint Designer.
162. What are the various types of workflow in SharePoint?
These are of two types namely: 1. Declarative Workflow: is a workflow that is built from conditions and actions that are assembled
into rules and steps, and that sets the parameters for the workflow without writing any code. 2. Compiled Workflow: is a workflow that can be built from conditions and actions, in addition it
allows custom code to be written inside them unlike Declarative workflows.
163. What is different with SharePoint 2010 workflows? Some of the additions in workflow model are: 1. SharePoint 2010 workflows are build upon the workflow engine provide .Net Framework 3.5. 2. In addition to the SharePoint lists, workflows can also be created for SharePoint sites. 3. SharePoint Designer 2010 also has a new graphical workflow designer for designing workflows
and deploying them directly to SharePoint. 4. Another Improvement in SharePoint Designer 2010 is that it now allows editing the out-of-the-
box workflows that comes with SharePoint.
164. What are Reusable List Workflows and Site workflows? 1. Reusable List Workflows - User can create a reusable list workflow (reusable workflow) in the
top-level site in the site collection, and that workflow can be made globally reusable — meaning that the workflow can be associated to any list, library, or content type in the site collection. User can also create a reusable workflow in any subsite in the site collection; this workflow is available for reuse in that particular subsite.
2. Site workflows - A site workflow is associated to a site — not to a list, library, or content type. Therefore, unlike most workflows, a site workflow is not running on a specific list item. Because of this, many of the actions that is available for items not available for site workflows.
165. How can a workflow be debugged? 1. visual studio debugging add w3wp.exe process 2. Visio workflow cannot be debugged. 3. SharePoint Designer offers no custom debugging functionality; user can write information at
various stages to history and view the content to debug.
166. What are the various types of in-built workflows in SharePoint 2010? Microsoft SharePoint Server 2010 includes the following predefined workflow templates that address common business scenarios: 1. Collect Feedback: This Workflow routes a document or item to a group of people for feedback.
Reviewers can provide feedback, which is then compiled and sent to the person who initiated the workflow. By default, the Collect Feedback workflow is associated with the Document content type, and therefore it is automatically available in document libraries.
2. Approval: This Workflow routes a document or item to a group of people for approval. By default, the Approval workflow is associated with the Document content type, and therefore it is automatically available in document libraries. A version of the Approval workflow is also associated by default with the Pages library on a publishing site, and can be used to manage the approval process for the publication of Web pages. The Approval workflow is a staged approval model (that is, the first set of approvers can undergo the review and approval process, then the next set of approvers, and so on). Each stage or approval set can also have its own behavior. For example, members of the first group of approvers can do their review in serial approval order (one after the other), members of the second group can do their review in parallel, and so on.
3. Disposition Approval: This Workflow manages document expiration and retention by letting participants to decide whether to keep or delete expired documents. The Disposition Approval workflow supports record management processes and is intended for use primarily in a Records Center site.
4. Collect Signatures: This Workflow routes a document that was created in a Microsoft application to a group of people to collect their digital signatures. By default, the Collect Signatures workflow
is associated with the Document content type, and therefore is automatically available in document libraries. However, the Collect Signatures workflow appears for a document in the document library only if that document contains one or more Microsoft Office Signature Lines.
5. Three-state: This Workflow is designed to track the status of a list item through three states (phases). It can be used to manage business processes that require organizations to track a high volume of issues or items, such as customer support issues, sales leads, or project tasks. The Three-state workflow is so named because it tracks the status of an issue or item through three different states, and through two transitions between the states. For example, when a workflow is initiated on an issue in an Issues list, SharePoint Server 2010 creates a task for the assigned user. When the user completes the task, the workflow changes from its initial state (Active) to its middle state (Resolved) and creates a task for the assigned user. When the user completes the task, the workflow changes from its middle state (Resolved) to its final state (Closed), and creates another task for the user to whom the workflow is assigned at that time. This workflow is only supported on lists, not libraries.
6. Translation Management: This Workflow manages manual document translation by creating copies of the document to be translated and by assigning translation tasks to translators. This workflow is available only for Translation Management libraries.
7. Issue Tracking: This Workflow routes an issue to team members for resolution. It presents a Web page to the user who makes possible the entry of new issues. For example, customer complaints. As an issue progresses though different workflow states, the Web page of the user changes to reflect appropriate events. For example, a Web page that was closed when an issue is resolved.
167. What are the Types of forms associated with the workflow? With SharePoint Designer 2010, user can create three types of workflow forms: 1. Initiation form – An initiation form gathers information from the workflow participant when
they start the workflow. It is automatically generated when user create the workflow in SharePoint Designer 2010. Initiation forms are displayed to users when they manually start a workflow on a given SharePoint item. With an initiation form, users can specify additional parameters or information about the workflow as it applies to the given SharePoint item.
2. Task form – A custom task form allows workflow participants to interact with tasks in the Tasks list specified for the workflow. With the Custom Task Wizard, user can easily create custom form fields and add them to a custom task form. When user finish designing the workflow, SharePoint Designer 2010 automatically generates the InfoPath or ASP.NET forms for custom tasks.
3. Reusable workflow – association form – A reusable workflow, by default, only provides the fields common to all items, such as Created and Modified by. This is because a reusable workflow is not by default associated with a list, library, or content type. An association form enables user to associate fields with a reusable workflow so that the fields will be available when user design and run the workflow.
168. What is the difference between method activity and event activity in Workflow?
A method activity is one that performs an action, such as creating or updating a task. An event activity is one that runs in response to an action occurring.
169. What is Governance model? Governance is the set of policies, roles, responsibilities, and processes that guides, directs, and controls how an organization's business division and IT team works together to achieve business goals. A comprehensive governance plan can benefit the organization by:
Streamlining the deployment of products and technologies, such as SharePoint Server 2010.
Protecting the enterprise from security threats or noncompliance liability.
Ensuring the best return on the investment in technologies.
170. What is Active Directory? Active Directory is a database that keeps track of all the user accounts and passwords in organization. It allows user to store user accounts and passwords in one protected location, improving organization's security. Active Directory is subdivided into one or more domains. A domain is a security boundary. A server computer called a domain controller (DC) hosts each domain. A domain controller manages all of the user accounts and passwords for a domain.
171. What are the key areas in which Governance model should be applied? The key areas in which governance model should be applied are: 1. IT governance - regulation over hardware, software, security, infrastructure, backup and
recovery, Multitenancy, Windows PowerShell as well as the services provided; 2. Information Architecture - design and administration of information life cycles, content types,
metadata, taxonomy, workflow, navigation and site structure, Document library, lists, web pages and data.
3. Customization Policy - administration and control of custom solutions built on top of or integrated within the SharePoint environment. Customization introduces risks to the stability, maintenance, and security of the SharePoint Server 2010 environment.
4. Branding - A formal set of branding policies helps ensure that sites consistently use enterprise imagery, fonts, themes, and other design elements.
172. What are the various permission levels in SharePoint?
Eight major Permission level in SharePoint are 1- Full Control 2- Design 3- Contribute 4- Read 5- Limited Access 6- Restricted Read 7- Approve 8- Manage Hierarchy
173. What permissions developer must have to install a webpart or any custom solution in SharePoint
2010 using PowerShell? In order to use Windows PowerShell for SharePoint 2010 Products, a user must be a member of the SharePoint_Shell_Access role on the configuration and content database. In addition to this, the user must also be a member of the WSS_ADMIN_WPG local group on the computer where SharePoint 2010 Products is installed.
174. What is Service application framework?
Service application framework provides a platform that allows developers to build scalable middle-tier applications.
175. What is SOA? SOA can be termed as “A service-oriented architecture is essentially a collection of services. These services communicate with each other. The communication can involve either simple data passing or it could involve two or more services coordinating some activity. Some means of connecting services to each other is needed. It can also be stated as rather than developing software as a monolithic, inseparable, intertwined, chunk of code, System design is comprised of autonomous “services” each providing some discrete function and/or access to data. These services are usually implemented in the form of Web Services, which come in many flavors including SOAP, REST, XML over HTTP, etc.
176. What are the benefits of SOA? SOA benefits include: 1. Reuse – once the service is written it can be plugged in wherever needed versus writing the same
application repeatedly every time/place user need it. 2. Consistency – the service executes the same way every time so, for example, calculations such as
APR (a tricky calculation for mortgages and one that has to be correct per compliance guidelines) and underwriting decisions are consistent across applications that consume the service.
3. Scalability & Reliability - Because the services run in a web server environment, they can take advantage of load balancing and fault tolerance technologies to provide scalability and reliability.
4. Rapid development – several services can be combined very rapidly to create robust applications without having to write anything but the code necessary to glue them together
5. Integration – access to line of business systems’ data and functionality becomes trivial if these systems are fronted by services.
177. What are the various services provided by SharePoint?
Services Description
Access Database Services New service that allows for viewing, editing and interacting with MS Access through a browser.
Application Registry Service Enables users to search and collaborate around business data. Provides backward compatibility to BDC service.
Business Data Connectivity Access to line of business systems. Service now supports writing to data services.
Central Administration Central Admin Site
Document Conversions Launcher Service
Schedules and initiates document conversions.
Document Conversions Load Balancer Service
Balances document conversions across the SharePoint farm.
Excel Calculation Services Ability to interact with Excel files in a browser. New extended functionality.
Lotus Notes Connector Index service connector to index Lotus Notes Domino Servers.
InfoPath Service Supports hosting InfoPath forms in SharePoint.
Managed Metadata Service New service that manages taxonomy structures and definitions.
Microsoft SharePoint Foundation Incoming E-mail
Email service. This will run on the machine where the web application is running.
Microsoft SharePoint Foundation Subscription Settings Services
New service used to track subscription IDs and settings for services that deployed in partition mode.
Microsoft SharePoint Foundation User Code Service
New service runs code deployed as part of a sandbox solution and runs in restricted mode. Must be started on any machine in the farm that needs to run Sandbox code.
Microsoft SharePoint Foundation Web Application
The service that runs the web application.
Microsoft SharePoint Foundation Workflow Timer Service
Responsible for running timer jobs.
PerformancePoint BI Dashboard services.
PowerPoint New services that allows viewing, editing and broadcasting PowerPoint in a browser.
Search Query and Site Settings Service
Service that performs a query across built indexes.
Secure Store Service Service provide SSO authentication.
SharePoint Foundation Search
Service that provides search capabilities for SharePoint Foundation Search only. For SharePoint Server 2010 Standard and Enterprise this service will perform online Help search.
SharePoint Server Search Crawls content, creates indexes and performs queries. Automatically configured.
State Service New services that provides temporary storage of user session data for SharePoint components.
Usage and Health Data Collection
Reporting services that provide farm wide usage and health.
User Profile New and expanded social networking services and features.
User Profile Synchronization Service
Synchronizes user and group profile information that is stored in the SharePoint Server 2010 profile store with profile information that is stored in directory services across the enterprise. Works with AD, BDC, Novel LDAP and Sun LDAP .
Visio Graphics Service Ability to view published Visio diagrams in a browser.
Web Analytics Data Processing Service
Captures data for analytics.
Web Analytics Web Service Web service interfaces for analytics.
Word Automation Services Service that performs automated bulk document conversions.
178. What is Business intelligence?
Business intelligence provides business intelligence feature that allows tracking key performance indicators and BI dashboards into the team site.
179. What is Business data catalog? Business data catalog (BDC) integrates external data into the SharePoint server. It is a one-way communication.
180. What is Business Connectivity Services (BCS)? In SharePoint 2010, Business Connectivity Services is all about connecting to external data. BCS enhances the SharePoint platform’s capabilities with out-of-box features, services, and tools that streamline development of solutions with deep integration of external data and services. It is a two-way communication.
181. What is Web Service? Web services are small units of code designed to handle a limited set of tasks. Web service provides methods that user can use to work remotely with a deployment of windows SharePoint services.
182. What are Event Receivers?
An event receiver is essentially a piece of code, which can be attached to a specific SharePoint object. They will be executed whenever a specified event occurs within that object. We can attach event receivers with Site, List, and List Item.
183. What are the various types of Events in SharePoint? SharePoint is having two types of events: Synchronous: happens 'before' the actual event, User has the Http Context and can show an error message in the browser and cancel the event. Asynchronous: happens 'after' the actual event, there is no Http Context and user cannot directly show an error message or cancel the event in spite of user can handle what happens after the event is fired.
184. What is a Timer job and how it can be deployed? Timer jobs are Microsoft.SharePoint.Administration.SPJobDefinition objects. To create a timer job, one should create a new class that inherits from SPJobDefinition. Timer jobs can be deployed by using Features, custom applications, Power Shell, or custom STSADM commands.
185. How to debug timer services and event receiver? Debugging Timer Service: User needs to attach debugger with OWSTIMER.exe process. This is the “Windows SharePoint Services Timer” service. Debugging Event Receiver: User can attach Visual Studio to the w3wp.exe process and simply put a breakpoint in the event handler code. Alternatively, use System.Diagnostics.Trace to write out information to a log.
186. What is Business Continuity Management?
Business continuity management consists of the business decisions, processes, and tools put in place in advance to handle crises. A crisis might affect the business only, or be part of a local, regional, or national event.
187. What is Windows PowerShell? Windows PowerShell is the new command line interface and scripting language designed for system administrators to perform tasks like backup, restore etc.
188. What is the path of PowerShell? The path of the PowerShell is: %WINDIR%\SysNative\WindowsPowerShell\v1.0\powershell.exe.
189. What is Stsadm?
Stsadm is command line utility located at the following path on the drive where SharePoint Products and Technologies is installed: %PROGRAM%FILES\COMMON%FILES\Microsoft%shared\web%server% extensions\14\bin. Stsadm provides a method for performing the administration tasks like backup, restore etc.
190. What is the advantage of using Windows PowerShell over Stsadm in SharePoint 2010? Unlike Stsadm, which accept and return text, Windows PowerShell is built on the Microsoft .NET Framework and accepts and returns .NET Framework objects. Windows PowerShell also gives user access to the file system on the computer and enables to access other data stores, such as the registry and the digital signature certificate stores etc.
191. What is the Stsadm command for installing, activating and deactivating a feature? For installation stsadm.exe -o installfeature -name "sample" –force For Activation stsadm.exe -o activatefeature -name "sample" -URL http://portal.espire.com For Deactivation Stsadm -o deactivatefeature -filename -name <feature folder> [-URL] <URL name> [-force]
192. How to move SharePoint application from one server to another?
1. Use the WSP Packages feature to export and to import a Windows SharePoint Services Web site
2. Back up the Windows SharePoint Services Web site then Restore on Windows SharePoint Services Web site.
3. Move SharePoint foundation or SharePoint Server 2010 content databases or configuration database from one SQL server to another.
193. What are the Methods of Backup and Recovery in SharePoint 2010?
Microsoft SharePoint Server 2010 provides a broad range of levels for performing backups, including the entire farm, farm configuration information, site collections, subsites, or lists. SharePoint Server 2010 uses two different tools to configure backup and recovery.
1. Central Administration: Central Administration provides a user interface where SharePoint
Administrators will be prompted via menu structures to select the information that needs to be backed up.
2. Windows PowerShell: Windows PowerShell is a command line tool that provides SharePoint
administrators a way to perform backup and recovery with additional options such as file compression or working with SQL snapshots.
194. What is the Stsadm command for backup?
To export sites Stsadm command. Stsadm –o export –URL <URL> -filename <FILENAME> .cmp To back up a site collection, user must use the following Stsadm command. Stsadm –o backup –URL <URL of the site collection> -filename <Name of the backup file> To back up an individual database, Web application, or the entire farm, user can use the following Stsadm command Stsadm –o backup –directory <UNC path or local drive> -backupmethod <full or differential>
195. What is the Stsadm command for restore? To import sites to the SharePoint Products and Technologies deployment, user uses the following Stsadm command. Stsadm –o import –URL <URL> -filename <FILENAME>.cmp To restore a site collection, user must use the following Stsadm command. Stsadm –o restore –URL <URL of the site collection> -filename <Name of the backup file> To restore an entire farm user can use the following Stsadm command. Stsadm –o restore –directory <UNC path or local drive> -restoremethod <overwrite or new>
196. How to list all the commands in PowerShell? Get-Command * command lists all the PowerShell commands in the PowerShell prompt.
197. Can admin create PowerShell scripts for deploying components in SharePoint? If developer is creating a webpart with VS 2010 then webpart can be deployed by using ctrl + f5. However, to activate the webpart feature admin can write a PowerShell script (.ps1) and execute it after deployment.
198. Can multiple SharePoint applications points to the same DB? Multiple SharePoint installs can use the same database server not the same database on that server.
199. How to write ULS logs in SharePoint 2010? In SharePoint, ULS exposes configurable settings in two ways, through the – Object model and Windows PowerShell cmdlets. For writing to SharePoint ULS logs, developers can use Diagnostics Service, which will make the customized categories viewable in the administrative UI for our errors. On the other hand, they can use the number of cmdlets available for accessing ULS logs using PowerShell. Some of the cmdlets are Get-SPDiagnosticConfig ,Get-SPLogEvent etc.
200. What does Development Environment for SharePoint 2010 means?
Development Environment is a set of plans for development of any software. This is a plan to set up machines, installation of software, tools and developers for development. The choice will be determined by factors specific to organization and environment (such as budget, the size of the development team, and the operating systems that organization already uses).
201. What are the various testing that needs to be done on SharePoint 2010 Application? 1. Performance Testing:
In SharePoint performance testing is in general testing performed to determine how a system or web application performs in terms of responsiveness and stability under a particular workload. It can also serve to investigate measure, validate or verify other quality attribute of the system, such as scalability, reliability and resource usage.
2. Stress Testing: Stress Testing is normally used to understand the upper limits of capacity within the system. This kind of test is done to determine the system's robustness in terms of extreme load and helps application administrators to determine if the system will perform sufficiently if the current load goes well above the expected maximum.
3. Load Testing: Load Testing is the simplest form of performance testing. A load test is usually conducted to understand the behavior of the system under a specific expected load. This load can be the expected concurrent number of users on the application performing a specific number of clicks or transactions within the set duration. This test gives out the response times of all the important business critical transactions, if the database, application server are also monitored, then this simple test can itself point towards any bottleneck in the application software.
4. Functional Testing: Functional testing refers to any procedure that tests the functionality of an application from the perspective of a user. Functional tests can include manual tests, Web tests, and integration tests. Integration tests are included in functional testing because systems often expose APIs for extensibility or for programmatic use.
“Limitations in SharePoint 2010”
Web application limits Maximum value
1. Content database 300 per Web application
2. Zone 5 per Web application
3. Managed path 20 per Web application
4. Solution cache size 300 MB per Web application
Web server and application server Limit
Maximum value
5. Application pools 10 per Web server
Content database Limit
6. Content database size 200 GB per content database
7. Site collections per
content database 2,000 recommended
8. Remote BLOB Storage
(RBS) storage subsystem on Network Attached Storage (NAS)
5,000 maximum Time to first byte of any response from the NAS cannot exceed 20 milliseconds
Site collection Limit Maximum value
9. Web site 250,000 per site collection
10. Site collection size 100 GB per site collection
List and library Limit Maximum value
11. List row size 8,000 bytes per row
12. File size 2 GB
13. Documents 30,000,000 per library
14. Major versions 400000
15. Items 30,000,000 per list
16. Rows size limit 6 table rows internal to the database used for a list or library item
17. Bulk operations 100 items per bulk operation
18. List view lookup
threshold 8 join operations per query
19. List view threshold 5000
20. List view threshold for
auditors and administrators
20000
21. Subsite 2,000 per site view
22. Coauthoring in
Microsoft Word and Microsoft PowerPoint for .docx, .pptx and .ppsx files
10 concurrent editors per document
23. Security scope 1,000 per list
Column Limit Maximum value
24. Single line of text 276
25. Multiple Lines of Text 192
26. Choice 276
27. Number 72
28. Currency 72
29. Date and Time 48
30. Lookup 96
31. Yes / No 96
32. Person or group 96
33. Hyperlink or picture 138
34. Calculated 48
35. GUID 6
36. Int 96
37. Managed metadata 94
Page Limit Maximum value
38. Web parts 25 per wiki or Web part page
Security Limit Maximum value
39. Number of SharePoint
groups a user can belong to
5,000
40. Users in a site
collection 2 million per site collection
41. Active Directory
Principles/Users in a SharePoint group
5,000 per SharePoint group
42. SharePoint groups 10,000 per site collection
43. Security principal: size
of the Security Scope 5,000 per Access Control List (ACL)
Search Limit Maximum value
44. SharePoint search
service applications 20 per farm
45. Crawl databases and
database Items 10 crawl databases per search service application 25 million items per crawl database
46. Crawl components 16 per search service application
47. Index partitions 20 per search service application; 128 total
48. Indexed items 100 million per search service application; 10 million per index partition
49. Crawl log entries 100 million per search application
50. Property databases 10 per search service application;128 total
51. Query components 128 per search application; 64/(total crawl components) per server
52. Scope rules 100 scope rules per scope; 600 total per search service application
53. Scopes 200 site scopes and 200 shared scopes per search service application
54. Display groups 25 per site
55. Alerts 1,000,000 per search application
56. Content sources 50 per search service application
57. Start addresses 100 per content source
58. Concurrent crawls 20 per search application
59. Crawled properties 500,000 per search application
60. Crawl impact rule 100
61. Crawl rules 100 per search service application
62. Managed properties 100,000 per search service application
63. Mappings 100 per managed property
64. URL removals 100 removals per operation
65. Authoritative pages 1 top level and minimal second and third level pages per search service application
66. Keywords 200 per site collection
67. Metadata properties 10,000 per item crawled
recognized
User Profile Service Limit
Maximum value
68. User profiles 2,000,000 per service application
69. Social tags, notes and
ratings 500,000,000 per social database
Content Limit
70. Content deployment
jobs running on different paths
20
Blog Limit Maximum value
71. Blog posts 5000 per site
72. Comments 1000 per post
Business Connectivity Services Limit
Maximum value
73. ECT (in-memory) 5000 per Web Server (per tenant)
74. External system
connections 500 per Web server
75. Database items
returned per request 2,000 per database connector
Workflow Limit Maximum value
76. Workflow postpone
threshold 15
77. Workflow timer batch
size 100
Managed Metadata term store (database) Limit
Maximum value
78. Maximum number of
levels of nested terms in a term store
7
79. Maximum number of
term sets in a term store 1000
80. Maximum number of
terms in a term set 30,000
81. Total number of
items in a term store 10,00,000
Visio Services Limit Maximum value
82. File size of Visio Web
drawings 50 MB
83. Visio Web drawing
recalculation time-out 120 seconds
84. Visio Services
minimum cache age (data connected diagrams)
Minimum cache age: 0 to 24hrs
PerformancePoint Services Limit
Maximum value
85. Cells 1,000,000 per query on Excel Services data source
86. Columns and rows 15 columns by 60,000 rows
87. Query on a SharePoint
list 15 columns by 5000 rows
88. Query on a SQL Server
data source 15 columns by 20000 rows
Word Automation Services Limit
89. Input file Size 512 MB
90. Frequency with which
to start conversions (minutes)
1 minute (recommended)
91. Number of conversions
to start per conversion process
For PDF/XPS output formats: 30 x MFor all other output formats: 72 x M Where M is the value of Frequency with which to start conversions (minutes)
92. Conversion job size 100,000 conversion items
93. Total active conversion
processes N-1, where N is the number of cores on each application server
94. Word Automation
Services database size 2 million conversion items
SharePoint Workspace Limit
Maximum value
95. SharePoint Workspace
synchronization 30,000 items per list
96. SharePoint Workspace
synchronization 1800 documents limit in SharePoint Workspace
OneNote Limit Maximum value
97. Number of Sections
and Section Groups in a OneNote Notebook (on SharePoint)
See limit for "Documents" in List and library limits
98. Maximum size of a
section See limit for "File size" in List and library limits
99. Maximum size of an
image, embedded file, and XPS OneNote printout in a OneNote section.
See limit for "File size" in List and library limits
100. Maximum size of all
images, embedded files, and XPS printouts in a single OneNote page.
Default limit is double the "File size" limit.
101. Merge operations One per CPU core per Web server
Office Web Application Service Limit
Maximum value
102. Cache size 100 GB
103. Renders One per document per second per CPU core per application server (maximum eight cores)
Project Server Limit Maximum value
104. End of project time Date: 12/31/2049
104. Deliverables per
project plan 1500 deliverables
105. Number of fields in a
view 256
106. Number of clauses in
a filter for a view 40
“SharePoint 2010 JumpStart”
The series “SharePoint 2010 JumpStart by Vishal Gupta” comprise 21 eBooks. These eBooks are written in simple language covering all the aspects of SharePoint 2010 and are based on practical scenarios with real life day-to-day examples. Being an architect for mission critical large-scale projects, I am exploring SharePoint for past eight years, and Microsoft technologies for near about 15 yrs. My focus is to relate the technology with real life problems in simplistic manner. The eBooks appraises more towards practical approach and issues faced while doing customizations, development and deployment of the SharePoint. These eBooks can be read and purchased individually by experts as per need, while novice users can purchase them sequentially to become SharePoint 2010 expert.
1 - “SharePoint 2010 Introduction – Vishal Gupta [[email protected]]” This eBook in series contains the details about what is SharePoint 2010.
o 1.1What is SharePoint? o 1.2 History of SharePoint o 1.3 CMS, DMS & RMS
o 1.4 SharePoint Basic Elements o 1.5 Features of SharePoint o 1.6.1 WSS 3.0 vs. MOSS 2007 o 1.6.2 WSS 3.0 vs. Microsoft SharePoint Foundation 2010 o 1.6.3 SharePoint Server 2007 vs. SharePoint Server 2010 o 1.6.4 SharePoint Foundation 2010 vs. SharePoint Server 2010 o 1.6.5 NET vs. SharePoint
2 - “SharePoint 2010 Architecture – Vishal Gupta [[email protected]]” This eBook in series contains the details about the architecture of SharePoint 2010.
o 2.1 Architecture Concepts o 2.1.1 Software Application Architecture o 2.1.2 Topology o 2.1.3 Server and Web service o 2.1.4 Web server [IIS] o 2.1.4.1 Elements of IIS o 2.1.4.2 Modules of IIS o 2.1.4.3 Authentication modes of IIS o 2.1.4.4 IIS site creation and deployment o 2.2 SharePoint Architecture o 2.3 SharePoint Interaction o 2.3.1 SharePoint IIS Interaction o 2.3.2 Difference in User Request Processing in .Net vs SharePoint o 2.3.3 Physical folder structure o 2.3.4 SharePoint Logical Directory Structure o 2.3.5 SharePoint SQL Interaction
3 - “SharePoint 2010 Installation & Configuration – Vishal Gupta [[email protected]]”
This eBook in series contains the details about step-by-step installation and configuration of SharePoint 2010.
o 3.1 Hardware and Software recommendations o 3.1.1 Hardware Requirements o 3.1.2 Software Requirements o 3.2. Browser Support o 3.3. IP Support o 3.4 SharePoint Standalone Installation o 3.5 SharePoint Server Farm installation o 3.5.1 Server Roles o 3.5.2 Server Topology o 3.5.3 Server Farm Complete Installation o 3.6 SharePoint Foundation Installation o 3.7 Difference in various installation Scenarios o 3.8 SharePoint server installation scenarios
o 3.9 SharePoint server installation Error 4 - “SharePoint 2010 Site Creation – Vishal Gupta [[email protected]]”
This eBook in series contains the details about the Creation and Site Management in SharePoint 2010.
o 4.1 SharePoint Look & Feel o 4.2 SharePoint Central Administration o 4.3 SharePoint Web Application o 4.3.1 Create a new Web application o 4.3.2 Extend an existing Web application o 4.4 Site Collection o 4.5 Site Actions
o 4.5.1 Edit Page o 4.5.2 New Page o 4.5.3 Document Library o 4.5.4 New Site o 4.5.5 More Options o 4.5.6 View All Site Content o 4.5.7 Edit SharePoint Designer o 4.5.8 Site Permissions o 4.6 Site Settings: o 4.6.1 Users and Permissions o 4.6.2 Look and Feel o 4.6.3 Galleries o 4.6.4 Site Actions o 4.6.5 Site Administration o 4.6.6 Site Collection Administration o 4.7 Existing User name o 4.7.1 My Site o 4.7.2 My Profile
5 - “SharePoint 2010 Common Operations – Vishal Gupta [[email protected]]”
This eBook in series contains the details about the common operations being performed on basic elements of SharePoint 2010.
o 5.1 Check out/Check in o 5.1.1 Check out o 5.1.2 Check in o 5.1.3 Discard Check out o 5.2 Versioning o 5.3 Column creation o 5.3.1 Scope of column o 5.3.2 Creating a column o 5.4 Content creation o 5.4.1 Creating a Content type o 5.5 Validation settings o 5.5.1 Column level validation o 5.5.2 List level validation o 5.6 Rating settings o 5.7 Audience targeting settings o 5.8 Views o 5.8.1 Advantages of Views o 5.8.2 Types of views o 5.8.3 Create a view o 5.8.4 Work with mobile views o 5.9 Scenario
6 - “SharePoint 2010 Out of the Box Elements-I –Vishal Gupta [[email protected]]”
This eBook in series contains the details about the out of the box elements - I provided by SharePoint 2010.
o 6.1 List o 6.1.1 Types of List o 6.1.2 Creating a List o 6.1.3 Creating a custom list o 6.1.4 Add item in a list o 6.1.5 Delete item from list o 6.1.6 Edit item in a list o 6.1.6 Add column in a list o 6.1.7 Limitations of Lists
o 6.2 Document library o 6.2.1 Creating a Document library o 6.2.2 Upload single document to Document library o 6.2.3 Upload multiple files to document library o 6.2.4 Typical uses of document libraries o 6.2.5 Moving/Copying SharePoint document library between sites o 6.2.6 Document ID feature of Document Library o 6.2.7 Limitations of Document Library o 6.3 Picture Library o 6.3.1 Creating a picture library o 6.3.2 Add images to a picture library o 6.4 Blogs o 6.4.1 Creating a Blog o 6.4.2 Create a post o 6.4.3 Set up categories o 6.4.3.1 Edit existing categories o 6.4.3.2 Add new categories o 6.4.3.3 Delete a category o 6.4.4 Manage posts o 6.5 Wiki o 6.5.1 Creating a WIKI o 6.5.2 Adding Content to Wiki o 6.5.2 Difference in Blogs/Wiki o 6.6 Poll/Survey o 6.6.1 Create a survey o 6.7 Ways to manage lists and libraries with many items o 6.7.1.1 Creating SharePoint indexed columns o 6.7.1.2 Creating filtered views based on column indexes o 6.7.1.3 Organizing items into folders o 6.7.1.4 Controlling the display of data on the page
7 - “SharePoint 2010 Out of the Box Elements-II – Vishal Gupta [[email protected]]” This eBook in series contains details about the out of the box elements - II provided by SharePoint
2010. o 7.1 Content Editor Web part o 7.1.1 Ways to add content to the content editor web part o 7.1.2 Creation of Content editor web part o 7.2 Image viewer web part o 7.2.1 Ways to display an image in image web part o 7.2.2 Creation of image web part o 7.3 Announcement o 7.3.1 Creation of announcement web part o 7.3.2 Add announcements to a web part o 7.4 Issue tracking o 7.4.1 Creation of issue tracking o 7.4.2 Add Items o 7.5 Chart web part (CWP) o 7.5.1 Creation of chart web part o 7.6 Excel web access web part o 7.6.1 Add an excel web access web part to a page o 7.7 RSS viewer o 7.7.1 Add RSS viewer web part to a page o 7.8 Web analytics o 7.8.1 Add web analytics web part to a page. o 7.9 XML viewer o 7.9.1 Add XML viewer to a page
o 7.10 Picture library slide show web part o 7.10.1 Add picture library slide show web part to a page o 7.11 Calendar web part o 7.11.1 Add calendar web part to a page o 7.12 Search statistics o 7.12.1 Add search statistics web part to a page o 7.13 Wiki Page Library o 7.14 Visio Process Repository o 7.15 Slide Library o 7.16 Report Library o 7.17 Record Center o 7.18 Project Web Database o 7.19 Multipage Meeting Workspace o 7.20 Issue Web Database o 7.21 Import Spreadsheet o 7.22 Assets Web Database o 7.23 Charitable Contributions Web o 7.24 Contacts Web Database o 7.25 Custom List in Datasheet view o 7.26 Data Connection Library o 7.27 Document Center o 7.28 Document Workspace o 7.29 Group Worksite
8 - “SharePoint 2010 Branding – Vishal Gupta [[email protected]]”
This eBook in series contains the details about how to provide similar look and feel to portal created using SharePoint 2010.
o 8.1 Branding in SharePoint o 8.2 Pages in SharePoint o 8.2.1 Site Pages o 8.2.1.1 Use of Site Pages o 8.2.1.2 Creation of Site pages o 8.2.1.3 Scenarios for using Site pages o 8.2.1.4 Drawbacks of using Site pages o 8.2.2 Application Pages o 8.2.2.1 Use of Application pages o 8.2.2.2 Creating Application pages o 8.2.2.3 Scenarios for using Application pages o 8.2.2.4 Drawbacks of Application pages o 8.2.2.5 Difference in Application pages vs. Site Pages o 8.2.3 Master Pages o 8.2.3.1 Benefits of using Master Pages o 8.2.3.2 Master Pages Available in SharePoint 2010 o 8.2.3.3 Customize a master page to brand your site o 8.2.3.4 FAQ’s related to Master Pages o 8.3 CSS in SharePoint o 8.3.1 How to use CSS o 8.3.2 Benefits of using CSS o 8.3.3 FAQ’s related to CSS o 8.4 Site Definition in SharePoint o 8.4.1 Files in Site Definition o 8.4.2 Create Site Definition o 8.4.3 Use of Site Definition o 8.4.4 When to use Site Definition o 8.5 Template in SharePoint o 8.5.1 Various Site Templates Available in SharePoint 2010
o 8.5.2 Create Site Template o 8.5.3 How to Use Custom Site Template o 8.5.4 Use of Site Templates o 8.5.5 When to Use Site Templates o 8.5.6 Difference between Site Definition and Site Templates o 8.6 Theme in SharePoint o 8.6.1 Customize Theme Feature o 8.6.2 Create Themes o 8.6.3 Benefits of using Themes o 8.7 Navigation in SharePoint o 8.8 Document Templates and Form Templates o 8.8.1 Customize Document Template o 8.8.2 Customize Form Template o 8.9 Customize the Ribbon o 8.10 Scenario to perform Branding
More to Come …
9 - “SharePoint 2010 Workflows and Deployment - Vishal Gupta [[email protected]]”
10 - “SharePoint 2010 Governance Model - Vishal Gupta [[email protected]]”
11 - “SharePoint 2010 Information Architecture - Vishal Gupta [[email protected]]”
12 - “SharePoint 2010 Capacity Planning & Limitations - Vishal Gupta [[email protected]]” 13 - “SharePoint 2010 Customization using SharePoint 2010 Designer - Vishal Gupta [[email protected]]”
14 - “SharePoint 2010 Customization using InfoPath 2010 - Vishal Gupta [[email protected]]”
15 - “SharePoint 2010 Customization using Visual Studio - Vishal Gupta [[email protected]]”
16 - “SharePoint 2010 Service Oriented Architecture - Vishal Gupta [[email protected]]”
17 - “SharePoint 2010 Administration - Vishal Gupta [[email protected]]”
18 - “SharePoint 2010 Document & Record Management - Vishal Gupta [[email protected]]”
19 - “SharePoint 2010 Migration - Vishal Gupta [[email protected]]”
20 - “SharePoint 2010 Performance Management - Vishal Gupta [[email protected]]”
21 - “SharePoint 2010 Case Studies - Vishal Gupta [[email protected]]”
------Thanks All----