Vous êtes sur la page 1sur 18

Interview Questions

Moss 2007
1- 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.
2- 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.
3- 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.

4- 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.

5- 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)

6- 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.
7- 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.
8- 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.

9- 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.

10What 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.

11-

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.

12When 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

13-

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.

14-

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.

15-

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.

16-

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.

17While 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.
18What 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

19What 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.

20-

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.

21-

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.

22-

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.

23-

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");

24What 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.

25-

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.

26Would 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.

27How 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.

28When 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.

29-

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.

30-

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 wouldnt be able to access or execute something.

31What 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.

32Why 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.

33What 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.

34What 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
custom components 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 WFEs 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..

35What 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.

36What file does a SharePoint solution package use to orchestrate


(describe) its packaged contents?
The solution Manifest.XML file.

37What 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.

38-

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.

39-

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.

40-

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.

41If 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.

42What 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

43-

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.
C#:
using(SPSite mySite = new SPSite("yourserver"))
{
using(SPWeb myWeb = mySite.OpenWeb())
{
myWeb.AllowUnsafeUpdates = true;
SPList interviewList = myWeb.Lists["listtoinsert"];
SPListItem newItem = interviewList.Items.Add();
newItem["interview"] = "interview";
newItem.Update();
}
}

44-

What does RunWithElevatedPrivileges do?

Assume that you have a Web Part in which you want to display information
obtained through the Windows SharePoint Services object model, such as

the name of the current site collection owner, usage statistics, or auditing
information. These are examples of calls into the object model that require
site-administration privileges. Your Web Part experiences an access-denied
error if it attempts to obtain this information when the current user is not a
site administrator. The request is initiated by a nonprivileged user. you can
still successfully make these calls into the object model by calling the
RunWithElevatedPrivileges method provided by the SPSecurity class.
C#:
SPSite siteColl = SPContext.Current.Site;
SPWeb site = SPContext.Current.Web;
SPSecurity.RunWithElevatedPrivileges(delegate() {
using (SPSite ElevatedsiteColl = new SPSite(siteColl.ID)) {
using (SPWeb ElevatedSite = ElevatedsiteColl.OpenWeb(site.ID)) {
string SiteCollectionOwner = ElevatedsiteColl.Owner.Name;
string Visits = ElevatedsiteColl.Usage.Visits.ToString();
string RootAuditEntries =
ElevatedSite.RootFolder.Audit.GetEntries().Count.ToString();
}
}
});

45What 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, such as at
the farm, site collection, web, etc. 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.

46What are content types ?


A content type is a flexible and reusable WSS type definition 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
customer presentation document with a unique set of columns, an event
handler, and its own document template. You can create a second content
type for a customer proposal document with a different set of columns, a
workflow, and a different document template.

47Workflow can be applied to what all elements of SharePoint ?


While workflow associations are often created directly on lists and
document 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 (or document library)
At the level of a content type defined at site scope
At the level of a content type defined at list scope

48What are the ways to initiate the workflow ?


1. Automatic
2. Manual (standard WSS UI interface)
3. Manual (Custom UI Interface)

49What are the types of input forms that can be created for a
workflow ?
You can create four different types of input forms including an association
form, an initiation form, a modification form, and a task edit form. Note
that these forms are optional when you create a workflow template.
8. What are ways to create input forms for workflow ?
Two different approaches can be used to develop custom input forms for a
WSS workflow template.
a. 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)
b. using Microsoft Office InfoPath 2007 (disadv: picks up a dependenct on
MOSS, i.e. it cannot run in a standalone WSS environment)

50What 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.

51What 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("mmangaldas");

52While creating a Webpart, which is the ideal location to Initialize my


new controls ?
Override the CreateChildControls method to include your new controls. To
make sure that the new controls are initialized.. call 'EnsureChildControls'
in the webparts Render method. You can control the exact Rendering of
your controls by calling the .Render method in the webparts Render
method.

53How to query from multiple lists ?


Use SPSiteDataQuery to fetch data from multiple lists. more details..

54How Does SharePoint work?


The browser sends a DAV packet to IIS asking to perform a document
check in. PKMDASL.DLL, an ISAPI DLL, parses the packet and sees that it
has the proprietary INVOKE command. Because of the existence of this
command, the packet is passed off to msdmserv.exe, who in turn
processes the packet and uses EXOLEDB to access the WSS, perform the
operation and send the results back to the user in the form of XML.

55What is the difference between Syncronous & Asyncronous events?


Syncronous calls ending with 'ing'
E.g. ItemDeleting
Event Handler code execute BEFORE action is committed
WSS waits for code to return
Option to cancel and return error code
Asyncronous calls ending with 'ed'
E.g. ItemDeleted
Event Handler code executes AFTER action is committed
WSS does not wait for code to return
Executed in its own Worker thread.

56What is ServerUpdate() ?
Any changes in the list, i.e. new addition or modification of an item.. the

operation is complete by calling the Update method.

But if a List is set to maintain versions .. and you are editing an item, but
don't want to save it as a new version, then use the SystemUpdate
method instead and pass in 'false' as the parameter.

57What is query.ViewAttributes OR How can you force SPQuery to


return results from all the folders of the list?
If you use SPQuery on any SPlist .. it will bring back results from the
current folder only.
If you want to get results from all the folders in the list.. then you need to
specify the scope of the query by the use of ViewAttributes..
e.g. query.ViewAttributes = "Scope=\"Recursive\"";

58How Branding can be achieved by Master Pages? What are the


advantages or disadvantages of Master Pages?

59Does sharepoint provide any way to grant read-only access to all


the users of the company on the portal?

60-

What are the steps to create a web-part?

61-

What does the webpart .cab file include?

62-

What are the benefits of using Infopath?

63-

What are the different namespaces per Sharepoint Object Model?

64-

What are the different Back-up and Restore methodologies?

65What are the steps in running a custom WebService under the


context of SharePoint?

66How can you display content from one site in another under the
same site collection ?

67-

How to Create a custom list form?

Some items to look at as a developer..


General info on WSS 3.0 development.
http://msdn2.microsoft.com/en-us/library/bb530302.aspx
Application page. Allows the use of inline custom code. Application pages
or "_layout" pages are stored on the SharePoint Web server and made
available via a Microsoft Internet Information Services (IIS) virtual
directory. Though application pages behave much like other ASPX pages
and allow the use of inline custom code, they differ from content pages in
that they cannot be used to host SharePoint features such as dynamic Web
Parts and Web Part zones. For more information, see Creating an
Application Page in Windows SharePoint Services 3.0.
WebParts.
http://blogs.tamtam.nl/mart/CreateASharePoint2007WebpartStepByStep.a
spx
Server Controls. User Controls on creation and how to install / deploy
them.
Content type. A reusable collection of settings to apply to a certain
category of content such as documents and folders. Content types are
designed to help users organize their SharePoint content in a more
meaningful way. For more information, see Introduction to Content Types.
Custom action. Represents a link, toolbar button, menu item, or any
control that can be added to a toolbar or menu that appears in the UI. You
define custom actions by using a custom action element within a feature
definition file. You can bind custom actions to a list type, content type, file
type, or programmatic identifier (ProgID). For more information, see
Custom Action Definitions.
Event receiver. Evaluator of an event and definer of the behavior of an
application. Windows SharePoint Services 3.0 allows you to define event
handlers within libraries, lists, and sites. Event receivers can be defined by
using a receiver element within a feature definition file. For more
information, see Event Registrations.
Feature. A package of Windows SharePoint Services elements that can be

activated for a specific scope and that helps users accomplish a particular
goal or task. Windows SharePoint Services 3.0 introduces this inherently
portable and modular functionality, which simplifies modification of sites
through site definitions. For more information, see Working with Features.
-- Inside Microsoft Windows Sharepoint Services 3.0
Master page. Pages that provide a consistent layout and appearance (look
and feel) for SharePoint sites. They allow you to factor out layout,
structure, and interface elements such as headers, footers, navigation
bars, and content placeholders. Master pages in ASP.NET 2.0 and master
pages in Windows SharePoint Services work in the same way. For more
information, see Building Simple Master Pages for Windows SharePoint
Services 3.0.
Module. A file or collection of file instances that define the location where
the files are installed during site creation. Modules are frequently used to
implement a Web Part Page in the site. You can define modules by using a
module element within a feature definition file. For more information, see
Modules.
Object Model. what is the architecture of sharepoint and how is it
represented programmatically. You have to create a webapplication as the
first step.. and specify a port number if the default port 80 is already
taken. This is not accessible as yet for browsing.. but you can see that a
new website is created in the IIS. Next step would be to create a
SiteCollection (multiple sitecollection can be created in a single website).
Creating a site collection creates a default root site. This root site is
accessible through the browser. you can go ahead to create multiple child
sites under the root site.
This was the administrative terms used. but for programming, to access
the SiteCollection we have to use SpSite and for the Sites we have to use
SpWeb.
SharePoint site: A Web site hosted in a virtual URL. A SharePoint site is a
place for collaboration, communication, or content storage. Depending on
your business needs, you can create sites such as team sites, blog sites,
wiki sites, and others. You can customize a site's appearance, users, user
permissions, galleries, and site administration by using the Site Settings
administration pages.
SharePoint site collection: A collection of SharePoint sites that share
common administration pages and site settings. Site collections allow you
to share content types, site columns, templates, and Web Parts within a
group of SharePoint sites.
SharePoint Web farm: A group of Office SharePoint 2007 servers that share
the same configuration database. All site content and all configuration

data is shared for all front-end Web servers in a server farm.


Custom List Definition.
http://ari.provoke.co.nz/archive/2007/04/18/creating-a-custom-sharepoint2007-list-definition.aspx
Site definition. A set of files that includes a master XML configuration file
that is stored on all front-end Web servers. A site definition provides the
basic blueprint for how sites look, what lists they include, their default
navigational structures, and so on. For more information, see Working with
Site Templates and Definitions.
Site template. A package containing a set of differences and changes from
a base site definition that is created through the UI or through
implementation of the object model. The site template package is stored
as a .cab-based file that can be downloaded or uploaded to site collections
by users with the appropriate rights. Site templates offer a measure of
portability to SharePoint applications. For more information, see Working
with Site Templates and Definitions.
Solution. A file that is a bundling of all the components for extending
Windows SharePoint Services in a particular way. A solution file has a .cabbased format with a .wsp extension. A solution is a deployable, reusable
package that can contain a set of Features, site definitions, and
assemblies that apply to sites, and that you can enable or disable
individually. You can use the solution file to deploy the contents of a Web
Part package, including assemblies, class resources, and other package
components. For more information see, Solution Overview.
Theme. A group of files (CSS, images) that allow you to define the
appearance (look and feel) of Web pages. Themes in ASP.NET 2.0 and
themes in SharePoint Products and Technologies work in the same way.
Themes are used to help organizations to brand their portals and team
sites. Office SharePoint Server 2007 includes a set of predefined themes.
However, as a developer, you can create custom themes for your
company. For more information, see How to: Customize Themes.
Code Access Security -- general info. (http://msdn.microsoft.com/enus/library/ms916855.aspx -- SPS 2003 but gives overall info)
HTTPHandlers in Sharepoint.
http://msdn.microsoft.com/en-us/library/bb457204.aspx
Programming Jobs in Sharepoint.
http://msdn.microsoft.com/en-us/library/cc427068.aspx
WWF

Custom Webservices. http://msdn2.microsoft.com/enus/library/ms464040.aspx .