This is part 2 of a series on SharePoint Server Interview questions. For reference, here are the links to the previous Part 1 of SharePoint Server Interview questions.
27. What base class do custom Field Controls inherit from?
29. What is a document library?
31. What is a template?
You can build Web Parts for Windows SharePoint Services 3.0 in two ways:
• Create custom ASP.NET 2.0 Web Parts.
• Create SharePoint-based Web Parts.
You should create ASP.NET 2.0 Web Parts whenever you can. However, there are a few exceptions where using SharePoint-based Web Parts might offer advantages
Create a custom ASP.NET 2.0 Web Part | Create a SharePoint-based Web Part |
· For most business needs. · To distribute your Web Part to sites that run ASP.NET 2.0 or SharePoint sites. · When you want to reuse one or more Web Parts created for ASP.NET 2.0 sites on SharePoint sites. · To use data or functionality provided by Windows SharePoint Services 3.0. For example, you are creating a Web Part that works with site or list data. | · When you want to migrate a set of Web Parts using the SharePoint-based Web Part infrastructure to Windows SharePoint Services 3.0. · To create cross page connections. · To create connections between Web Parts that are outside of a Web Part zone. · To work with client-side connections (Web Part Page Services Component). · To use a data-caching infrastructure that allows caching to the content database. |
37. What is Centralized configuration and Management Model? What are new and enhanced services in MOSS 2007?
38. What is UI Trimming?
39. What is MOM (Microsoft Operations Manager)?
40.What is Site Provisioning?
Lists store information about items such as events, contacts, or announcements. SharePoint lists are easy to create, requiring absolutely no code, special development skills or tools. In the past, such lists took time to create and required using an application and hiring a developer or user with technical skills.
42.What is SharePoint Library?
Libraries are much like lists with one major difference: their intended content. Libraries store documents.
43. What is Workflow?
Ans: A workflow automates a business process by breaking it into a set of steps that users must take to complete a specific business activity, such as approving content or routing a document from one location to another.
44. Sites, Workspaces, and Site Collections?
sites and workspaces, and site collections all refer to SharePoint sites.
· Sites: These share information in the form of list items and documents within a team or organization.
· Workspaces: These are more specific to an important document, such as an annual report, on which a team collaborates, or to a significant event, such as a gala or annual business meeting.
· Site collections: These are a group of sites and or workspaces that form a hierarchy with a single top-level website with a collection of subsites.
45. What is the difference between method activity and event activity in WF?
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.
46. Features Directory ?
i.e.Local_Drive:\ProgramFiles\CommonFiles\MicrosoftShared\webserver extensions \12\ TEMPLATE\ FEATURES\NewFeature
Attachment of a Feature to all new instances of sites that use a given site definition, without modifying the site definition or creating code routines to activate the Feature on each site. Also known as a feature site template association.
Feature stapling is implemented through a Feature that is specifically designed to staple other Features to one or more site definitions. Feature stapling allows a Feature to be stapled to any new sites created from any site definition or from specific site definitions based on the template name identified in the appropriate WEBTEMP.xml file.
Following is an example of feature stapling that associates the Feature with only the STS site definition templates.
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<FeatureSiteTemplateAssociation Id="00BFE171-1B17-4F72-28CB-1171C0140130" TemplateName="STS#0" />
<FeatureSiteTemplateAssociation Id="00BFE171-1B17-4F72-28CB-1171C0140130" TemplateName="STS#1" />
<FeatureSiteTemplateAssociation Id="00BFE171-1B17-4F72-28CB-1171C0140130" TemplateName="STS#2" />
Elements>
Following is an example of feature stapling that associates the Feature with all site definitions.
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<FeatureSiteTemplateAssociation Id="00BFE171-1B17-4F72-28CB-1171C0140130" TemplateName="GLOBAL" />
Elements>
48. How to make a webpart invisible to specific user?
Specify 'Target' Property to specific audience. Audience is a very powerful feature of Microsoft SharePoint Portal Server. You can create different audience in order to better manage the web parts security and visibility among portal users. Audience is more like a group created in portal server level, not at the windows server or Active Directory level. Every web part of Microsoft SharePoint Portal Server is having an option called 'Target'. By selecting the target we can make the web part visible to certain group of people.
Windows SharePoint Services offers a highly structured object model that makes it easy to access objects that represent the various aspects of a SharePoint Web site. For example accessing Feature Classes.
Feature Classes
- Microsoft.SharePoint.SPFeature (SPFeatureCollection) Returns an object that represents the state of a feature at its corresponding level. The presence of a feature in a collection at the farm (Microsoft.SharePoint.Administration.SPWebService), Web application (Microsoft.SharePoint.Administration.SPWebApplication), site collection (Microsoft.SharePoint.SPSite), or Web site (Microsoft.SharePoint.SPWeb) levels indicates that the feature is activated. Lack of a SPFeature object indicates that the object is not active in the given scope. Namespace: Microsoft.SharePoint
- Microsoft.SharePoint.SPFeatureProperty (SPFeaturePropertyCollection) Represents a single feature property. Namespace: Microsoft.SharePoint
- Microsoft.SharePoint.SPFeatureScope An enumeration of the possible scopes that can be specified for a feature, including Farm, WebApplication, Site, and Web. Namespace: Microsoft.SharePoint
- Microsoft.SharePoint.Administration.SPFeatureDefinition (SPFeatureDefinitionCollection) Contains the base definition of a feature, including the name, scope, ID, and version of the feature. Also, globally per feature, you can store properties about the feature. Namespace: Microsoft.SharePoint.Administration
- Microsoft.SharePoint.SPFeatureDependency (SPFeatureDependencyCollection) Represents a feature that is depended upon by another feature. Namespace: Microsoft.SharePoint
- Microsoft.SharePoint.Administration.SPElementDefinition (SPElementDefinitionCollection) Represents an element to be provisioned when the feature is activated or used. Namespace: Microsoft.SharePoint.Administration