hi,
Here are a few questions which can be usefull in a interview.
Compiled from various sources on net, I will try to keep it updated ...
• What is the relationship between Microsoft SharePoint Portal Server and Microsoft Windows Services?
Microsoft
SharePoint Products and Technologies (including SharePoint Portal
Server and Windows SharePoint Services) deliver highly scalable
collaboration solutions with flexible deployment and management tools.
Windows SharePoint Services provides sites for team collaboration, while
Share Point Portal Server connects these sites, people, and business
processes-facilitating knowledge sharing and smart organizations.
SharePoint Portal Server also extends the capabilities of Windows
SharePoint Services by providing organizational and management tools for
SharePoint sites, and by enabling teams to publish information to the
entire organization.
• What is a SharePoint Feature? What files are used to define a feature?A
SharePoint Feature is a functional component that can be activated and
deactivate at various scopes throughout a SharePoint instances, scope of
which are defined as
1. Farm level 2. Web Application level 3. Site level 4. Web level
Features have their own receiver architecture, which allow you to trap events such as when a feature is
Installing, Uninstalling, Activated, or Deactivated.
The element types that can be defined by a feature include
menu commands, link commands, page templates, page instances, list definitions, list instances,
event handlers, and workflows.
The
two files that are used to define a feature are the feature.xml and
manifest file(elements.xml). The feature XML file defines the actual
feature and will make SharePoint aware of the installed feature. The
manifest file contains details about the feature such as functionality.
• Workflow can be applied to what all elements of SharePoint ?Workflow
associations are often created directly on lists and libraries, a
workflow association can also be created on a content type that exists
within the Content Type Gallery for the current site or content types
defined within a list. In short, it can be applied ...
At the level of a list/library
At the level of a content type defined at site scope
At the level of a content type defined at list scope
• What are the types of input forms that can be created for a workflow ?You can create four different types of input forms including
1. An association form
2. An initiation form
3. A modification form
4. A task edit form.
Note that these forms are optional when you create a workflow template.
• What are ways to create input forms for workflow ?Two
1.
You can create your forms by using custom application pages, which are
standard .aspx pages deployed to run out of the _layouts directory. (
disadv: lot of code required when compared to Infopath approach)
2.
Using Microsoft Office InfoPath 2007 (disadv: picks up a dependenct on
MOSS, i.e. it cannot run in a standalone WSS environment)
• 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.
• What are content types?A
content type is a flexible and reusable WSS type definition (or we can a
template) that defines the columns and behavior for an item in a list
or a document in a document library. For example, you can create a
content type for a leave approval document with a unique set of columns,
an event handler, and its own document template and attach it with a
document library/libraries.
• Can a content type have receivers associated with it?Yes,
a content type can have an event receiver associated with it, either
inheriting from the SPListEventReciever base class for list level
events, or inheriting from the SPItemEventReciever base class. Whenever
the content type is instantiated, it will be subject to the event
receivers that are associated with it.
• What two files are typically (this is kept generally) included when developing a content type, and what is the purpose of each?There
is generally the main content type file that holds things like the
content type ID, name, group, description, and version. There is also
the ContentType.Fields file which contains the fields to include in the
content type that has the ID, Type, Name, DisplayName, StaticName,
Hidden, Required, and Sealed elements. They are related by the FieldRefs
element in the main content type file.
• 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.
• 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.
• When creating a list definition, how can you create an instance of the list?You can create a new instance of a list by creating an instance.XML file
• What is a Field Control?Field
controls are simple ASP.NET 2.0 server controls that provide the basic
field functionality of SharePoint. They provide basic general
functionality such as displaying or editing list data as it appears on
SharePoint list pages.
• What base class do custom Field Controls inherit from?This
varies. Generally, custom field controls inherit from the
Microsoft.SharePoint.WebControls.BaseFieldControl namespace, but you can
inherit from the default field controls.
• Can multiple SharePoint installs point to the same DB?Multiple
SharePoint installs can use the same database server. Not literally the
same database on that server. That server must be SQL Server 2000 or
SQL Server 2005. It cannot be Oracle or another vendor.
• How to create links to the mapped network drives?Creating links to mapped drives in WSS v3 or MOSS 2007 can be done via
the new content type for .lnk files.
• While creating a Web part, which is the ideal location to Initialize my new controls?
Override
the CreateChildControls method to include your new controls. You can
control the exact rendering of your controls by calling the .Render
method in the web parts Render method.
• What are the two base classes a WebPart you are going to use within SharePoint 2007 can inherit from?There are two base classes that a WebPart which is going to be consumed by SharePoint can inherit from, either the
SharePoint WebPart Base class
or the
ASP.NET 2.0 WebPart base class.
When
inheriting from the SharePoint WebPart Base class your derived WebPart
class will inherit from Microsoft.SharePoint.WebPartPages.WebPart. When
inheriting from the ASP.NET 2.0 WebPart base class your derived WebPart
class will inherit from System.Web.UI.WebControls.WebParts.WebPart. It
is considered good practice to use the ASP.NET WebPart base class since
the old base class is meant for backwards compatibility with previous
version of SharePoint, however there are four exception when it is
better to leverage functionality from the SharePoint WebPart base class:
Cross page connections
Connections between Web Parts that are outside of a Web Part zone
Client-side connections (Web Part Page Services Component)
Data caching infrastructure
• What are the differences between the two base classes and what are the inherit benefits of using one over another?The
difference is the Microsoft.SharePoint.WebPartPages.WebPart base class
is meant for backward compatibility with previous versions of
SharePoint. The benefit of using the SharePoint WebPart base class is it
supported:
Cross page connections
Connections between Web Parts that are outside of a Web Part zone
Client-side connections (Web Part Page Services Component)
Data caching infrastructure
ASP.NET
2.0 WebParts are generally considered better to use because SharePoint
is built upon the ASP.NET 2.0 web architecture. Inheriting from the
ASP.NET 2.0 base class offers you features that inherit to ASP.NET 2.0,
such as embedding resources as opposed to use ClassResources for
deployment of said types.
• What is the WebPartManager sealed class? What is its purpose?
The
WebPartManager sealed class is responsible for managing everything
occurring on a WebPart page, such as the WebParts (controls), events,
and misc. functionality that will occur in WebPartZones. For example,
the WebPartManager is responsible for the functionality that is provided
when you are working with moving a WebPart from WebPartZone to
WebPartZone. It is known as the “the central class of the Web Part
Control Set.”
• What does AllowUnsafeUpdates do ?If
your code modifies Windows SharePoint Services data in some way, you
may need to allow unsafe updates on the Web site, without requiring a
security validation. You can do by setting the AllowUnsafeUpdates
property.
• What does RunWithElevatedPrivileges do?There
are certain object model calls model that require site-administration
privileges. To bypass access-denied error, we use
RunWithElevatedPrivileges property when request is initiated by a
nonprivileged user. We can successfully make calls into the object model
by calling the RunWithElevatedPrivileges method provided by the
SPSecurity class.
• What does SPWeb.EnsureUser method do?Checks
whether the specified login name belongs to a valid user of the Web
site, and if the login name does not already exist, adds it to the Web
site.
e.g SPUser usr = myWeb.EnsureUser("hitenders");
• What is a SPSite and SPWeb object, and what is the difference between each of the objects?The
SPSite object represents a collection of sites (site collection [a top
level site and all its subsites]). The SPWeb object represents an
instance SharePoint Web, and SPWeb object contains things like the
actual content. A SPSite object contains the various subsites and the
information regarding them.
• What does a SPWebApplication object represent?The
SPWebApplication objects represents a SharePoint Web Application, which
essentially is an IIS virtual server. Using the class you can instigate
high level operations, such as getting all the features of an entire
Web Application instance, or doing high level creation operations like
creating new Web Applications through code.
• Would you use SPWebApplication to get information like the SMTP address of the SharePoint site?Yes,
since this is a Web Application level setting. You would iterate
through each SPWebApplication in the SPWebApplication collection, and
then use the appropriate property calls (OutboundMailServiceInstance) in
order to return settings regarding the mail service such as the SMTP
address.
• How do you return SharePoint List items using SharePoint web services?
In
order to retrieve list items from a SharePoint list through Web
Services, you should use the lists.asmx web service by establishing a
web reference in Visual Studio. The lists.asmx exposes the GetListItems
method, which will allow the return of the full content of the list in
an XML node. It will take parameters like the GUID of the name of the
list you are querying against, the GUID of the view you are going to
query, etc.
Side Question: I got asked how I built queries with the
lists.asmx web service. In order to build queries with this service, one
of the parameters that the GetListItems method exposes is the option to
build a CAML query. There are other ways to do this as well, but that
was how I answered it.
• When retrieving List items using
SharePoint Web Services, how do you specify explicit credentials to be
passed to access the list items?In order to specify
explicit credentials with a Web Service, you generally instantiate the
web service, and then using the credentials properties of the Web
Service object you use the System.Net.NetworkCredential class to specify
the username, password, and domain that you wish to pass when making
the web service call and operations.
• What is CAML, and why would you use it?CAML
stands for Collaborative Application Markup Language. CAML is an XML
based language which provides data constructs that build up the
SharePoint fields, view, and is used for table definition during site
provisioning. CAML is responsible for rending data and the resulting
HTML that is output to the user in SharePoint. CAML can be used for a
variety of circumstances, overall is used to query, build and customize
SharePoint based sites. A general use would be building a CAML query in a
SharePoint WebPart in order to retrieve values from a SharePoint list.
• What is impersonation, and when would you use impersonation?
Impersonation
can basically provide the functionality of executing something in the
context of a different identity, for example assigning an account to
users with anonymous access. You would use impersonation in order to
access resources on behalf of the user with a different account, that
normally, that wouldn’t be able to access or execute something.
• What are WebPart properties, and what are some of the attributes you see when declaring WebPart properties in code?
WebPart
properties are just like ASP.NET control properties, they are used to
interact with and specify attributes that should be applied to a WebPart
by a user. Some of the attributes you see with ASP.NET 2.0 properties
are WebDescription, WebDisplayName, Category, Personalizable, and
WebBrowsable. Although most of these properties come from the
System.Web.UI.WebControls.WebParts class, ones like Category come out of
System.ComponentModel namespace.
• Why are properties
important in WebPart development, and how have you exploited them in
past development projects? What must each custom property have?Properties
are important because WebParts allow levels of personalization for each
user. WebPart properties make it possible for a user to interact,
adjust, and increase overall experience value with the programmatic
assets that you develop without having the need to use an external
editor or right any code. A very simple example of exploiting a property
would be something like allowing the user to change the text on the
WebPart design interface so that they can display whatever string of
text they desire.
Each custom property that you have must have the appropriate get and set accessor methods.
• What are ClassResources? How do you reference and deploy resources with an ASP.NET 2.0 WebPart?ClassResources
are used when inheriting from the
SharePoint.WebPart.WebPartPages.WebPart base class, and are defined in
the SharePoint solution file as things that should be stored in the
wpresources directory on the server. It is a helpful directory to use in
order to deploy custom images. In ASP.NET 2.0, typically things such as
images are referenced by embedding them as resources within an
assembly. The good part about ClassResources is they can help to
eliminate recompiles to change small interface adjustments or
alterations to external JavaScript files.
• What is a SharePoint Solution File? How does it differ from WebPart .cab files in legacy development? What does it contain?A
SharePoint solution file is essentially a .cabinet file with all a
developers ustom componets suffixed with a .wsp extension that aids in
deployment. The big difference with SharePoint solution files is is that
a solution:
allows deployment to all WFE’s in a farm
is highly manageable from the interface allowing deployment, retraction, and versioning
Can package all types of assets like site definitions, feature definitions (and associated components), Webparts, etc.
Can provide Code Access Security provisioning to avoid GAC deployments
And much more..
• What is a .ddf file and what does it have to do with SharePoint Solution creation?A
.ddf file is a data directive file and is used when building the
SharePoint solution bundle specifying the source files and their
destination locations. The important thing for someone to understand is
that the .ddf file will be passed as a parameter to the MAKECAB utility
to orchestrate construction of the SharePoint solution file.
• What file does a SharePoint solution package use to orchestrate (describe) its packaged contents?The solution Manifest.XML file.
• What deployment mechanism can you use to instigate Code Access Security attributes for your WebParts?SharePoint
solution files can add in order to handle code access security
deployment issues. This is done in the element in the SharePoint
solution manifest.XML, which makes it easier to get assemblies the
appropriate permissions in order to operate in the bin directory of the
web application.
• What are event receivers?
Event
receivers are classes that inherit from the SpItemEventReciever or
SPListEventReciever base class (both of which derive out of the abstract
base class SPEventRecieverBase), and provide the option of responding
to events as they occur within SharePoint, such as adding an item or
deleting an item.
• When would you use an event receiver?Since
event receivers respond to events, you could use a receiver for
something as simple as canceling an action, such as deleting a document
library by using the Cancel property. This would essentially prevent
users from deleting any documents if you wanted to maintain retention of
stored data.
• What base class do event receivers inherit from?Event
receivers either inherit from the SPListEventReciever base class or the
SPItemEventReciever base class, both which derive from the abstract
base class SPEventReceiverBase.
• If I wanted to not allow people to delete documents from a document library, how would I go about it?You would on the ItemDeleting event set: properties.Cancel= true.
• What is the difference between an asynchronous and synchronous event receivers?An
asynchronous event occurs after an action has taken place, and a
synchronous event occurs before an action has take place. For example,
an asynchronous event is ItemAdded, and its sister synchronous event is
ItemAdding