1. SharePoint:
1)
Microsoft SharePoint is an enterprise collaboration and content management
platform,. SharePoint is a
business collaboration platform.
2) SharePoint 2010 is a platform where user can share Data, Collaborate and
people can also take this
platform and customized patform as per their requirements.
3) SPFarm
-> SPServer -> SPServices - >SPWebServices
->SPWebApplication ->SPSite Collection
-> SPWeb ->SPList ->SPField
->SPItem ->SPFile ->SPFolder
4) SharePoint having one
of the best feature is SharePoint
Designer, InfoPath, search services.
5). SharePoint is
web Application platform developed by Microsoft.
2. SharePoint 2010 Features:
1) Sites: A
site is a contextual work environment. Once SharePoint is configured, these
sites can be created without any requirement for specialized knowledge. A
context for a site may be organization-wide, or it may be specific to an
individual team or group.
2) Communities: A community is a place where communication
and understanding happens. Communities can occur around any context, and will
typically develop around either shared knowledge, or shared activities (such as
collaboration).
3)Content: SharePoint provides management of
documents and work items that need to be stored, found, collaborated on,
updated, managed, documented, archived, traced or restored - in accordance with
relevant compliance or governance policies.
4) Search: Look for relevant communities, content,
people, or sites: search is based on keywords, refinement, and content
analysis.
5) Insights: Information from any part of the
organization can be surfaced inside useful contexts, providing information that
can improve effectiveness.
6) Composites: SharePoint enables no-code integration of
data, documents and processes to provide composite
applications ("mash-ups" based on internal data).
3. Different between SharePoint 2010 vs SharePoint 2013
3. Different between SharePoint 2010 vs SharePoint 2013
SharePoint 2013 is
new version of famous collaboration portal.
SharePoint 2013 the
new versions adds few existing features such as Social Feed, SharePoint apps
and Cross site publishing.
sharepoint 2010 was
released in 2010.
Application:
However the
sandbox solution could be deprecated and replaced the application model.
introduce App
Catalog&Marketplace
Collaboration:
Improving the Team-sites
, Work-management in 2013
Social:
introduce the
Newsfeed,Skydrive Pro, Community Sites Follow Content , Follow
site, Follow User .
Search:
introduce Out-of-Box FastSearch , Continuos Crawl.
Content Mnagement:
Content Mnagement:
introduce
Cross-site-Publishing,eDiscovery
BI:
Same as well as SharePoint 2010 and 2013
Same as well as SharePoint 2010 and 2013
Busniess Solutions:
introduce
SharePoint2013-Workflow ,Access
Branding:
introduce Updated
SharePoint Designer,Design manager,channels
Mobile:
introduce Native
support for iOS/Android
4. SharePoint History:
2001
SharePoint Team Services (free) - SharePoint Portal Server2001
(lic)
2003 wss2.0
(free)
- SharePoint Portal Server2003 (lic)
2007 wss3.0
(free)
- Microsoft office SharePoint server (lic)
2010 SharePoint
Foundation
- SharePoint Server2010
2013 SharePoint
Foundation
+
- SharePoint Server2013
5. SharePoint Product History:
2001---CMS(failure due
to heavy cost) everyting is paid version only
2003---CMS*(better in
2003 beacuse reduces cost and give some features free)
2007---CMS+WCM*( utimate
version and most pupular and MS office give freeeeee)
2010---CMS+WCM+ECMS*(
rich applications + new and advanced features)
2013-----CMS+WCM+ECMS*+
new advaced feature+apps
6. Content management system (cms):
1.CMS is a computer program that allows publishing, editing and
modifying content as well as maintenance from a central
interface Such systems of content provide procedures to manage workflow in a collaborative
environment.
2. CMS is a more complex and powerful functions
3.CMSs are often used to run websites containing blogs, news, and shopping. Many corporate and marketing websites use CMSs.
3 types of CMS
1. Web content management system
2. Component content management system
3. Enterprise content management systems
Enterprise content
management types:
7. Web content management:
Web content management
capabilities to create, publish, manage, and control a large, dynamic collection of content. Web content management, as part of Enterprise
Content Management (ECM) in Office SharePoint Server 2007, can help streamline
your process for creating and publishing Web sites.
8. Document content mgmt system:
Document management capabilities on the storage and organization of documents to support active work in
progress, including content creation and
sharing within an organization
Microsoft Office
SharePoint Server 2007 supports your organization's document management needs
by providing a broad set of document management capabilities that enable you to
do the following.
->Store, organize, and locate documents.
->Ensure the consistency
of documents.
->Manage metadata for
documents.
->Help protect
documents from unauthorized access or use.
->Ensure consistent
business processes (workflows) for how documents are handled.
9. STS/SPS
It STS is running on 2001, SPS is running
on2001 and 2003 paid versions.
. SharePoint Portal Services (SPS) has MUCH better document
management. It has check-in, check-out, versioning, approval, publishing,
subscriptions, categories, etc.
. STS does not have these features, or they are very scaled back.
.SharePoint Portal Services (SPS) has a better search
engine, and can crawl multiple content sources.
.STS cannot.
. STS is easier to manage and much better for a team environment
where there is not much Document Management going on. SPS is better for an
organization, or where Document Management is crucial.
10. Windows Sharepoint Services (WSS)
Windows Sharepoint Services (WSS)
is a portal-based platform for creating, managing and sharing documents and
customized Web services. WSS is available as a free download included with
every Windows Server license and is considered to be part of the Office 2003
productivity suite.
11. Whats new in Shared Service
Provider (SSP ) in Sharepoint 2010 ?
(Alt Q: What is "Service Application" ? )
“Service Application” or “Service App” is a concept in Sharepoint 2010,
where SSP Services are split out into separate services.
What is replaced?
(Alt Q: What is "Service Application" ? )
“Service Application” or “Service App” is a concept in Sharepoint 2010,
where SSP Services are split out into separate services.
What is replaced?
1. Profiles, Audiences = People Service App
2. Search = Search Service App
3. Excel = Excel Service App
Whats new :-
1. Project Server = Project Server App
2. Visio Services = Visio Service App
Advantages :-
1. Web applications can be configured to only use a subset
of the
deployed services.
2. You can deploy multiple instances of the same service in
a farm by
giving the new service instances unique names.
3. You can share services across multiple web applications
in a farm.
SSP: The major services that are handled by the SSP are:
Profiles and Audiences
My Sites
Search
All of Excel Services
All of the BDC (Business Data Catalog)
12. SPSite and SPWeb:
The SPSite object
represents a collection of sites (site collection [a top level sites 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.
13. Dispose: According to the
best Practices you should always dispose them if you have created them in your
code.
You can
dispose them in finally block or you can use the "Using" clause, so
that they gets disposed when not required. If you are using SPContext then you
need not dispose the spsite or spweb objects.
14. Using Clause:
14. Using Clause:
15. Explain
the WebPart life cycle.
WebPart life cycle also same as asp.net life
cycle. Here you can find some additional events like CreateChildControls,
RenderContents etc.
· OnInit
· OnLoad
· CreateChildControls
· OnPreRender
· Render
(RenderContents, etc)
- See
more at:
http://sharepointknowledgebase.blogspot.in/2012/12/sharepoint-developer-interview-questions.html#sthash.UgUlZkFD.dpuf
16. SharePoint Web Application:
->Before you can
create a site collection, you must first create a Web application.
->Each Web
application is represented by a different IIS Web site with a unique or shared
application pool. You can assign each Web application a unique domain name,
which helps to prevent cross-site scripting attacks.
You use Web applications
to isolate content. When you create a new Web application, you also create a
new content database and define the authentication method used to connect to
the database. In addition, you define an authentication method to be used by
the IIS Web site in SharePoint Foundation 2010.
17. PowerShell:
Windows PowerShell is an Extendable command shell and scripting
language.
Pre-PowerShell we used to do all sorts of tasks with all sorts of tools:
Central
Administration website
the SharePoint
Products Configuration Wizard
STSADM
Psconfig
Use with Stsadm->
Activate / deactivate
the feature
Delete / add the feature
Backup/restore
Administrator full
access to applicable application programming interfaces (APIs). Administrators
can use Windows PowerShell to interact directly with SharePoint-based web
applications, site collections, sites, lists, and more.
18. SharePoint 2010's Search Center
SharePoint 2010
provides a site template that's built for delivering search results. You can
use this template to create a branded search experience or to customize how
results appear. You can choose among three search center site templates:
Basic Search Center delivers a stripped down search
experience in one page. This site template uses Web Part pages and is
essentially a team site specialized for search.
Enterprise Search
Center provides
multiple pages for displaying search results. This site template uses
publishing pages, which make it easier to brand and customize than Basic Search
Center.
FAST Search Center is used with the add-on search product
FAST Search for SharePoint 2010 to provide enhanced search results. Very large
enterprises use the FAST search product. Any search solutions you create with
SharePoint 2010’s default search options continue to work even if your company
chooses to deploy FAST.
SharePoint 2010's
Search Center Feature
You can
create a new site collection using one of the search center templates and then
configure multiple site collections to use that same search center.
19.What is Web part?
Web part is a fundamentally building blocks and for SharePoint (UI) .
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.
Web part is a fundamentally building blocks and for SharePoint (UI) .
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.
Visual web part:
The new important
feature introduced in SharePoint on webparts is Visual webpart. It’s a
combination of user control (.ascx) and assembly (.dll)
Since a Visual Web
Part loads a User Control (.ascx) from the SharePoint Root it needs access to
run the ASP.NET method LoadControl and file system access to the
ControlTemplates folder in the SharePoint Root – and this is not allowed by a
Sandboxed Solution.
Visual webpart cannot
be deploying using sandbox solutions.
SharePoint 2010
difference between webpart and visual web part?
SharePoint designer:
1. It
is a part of Microsoft SharePoint family of products.
2.
SharePoint Designer focuses on designing and personalizing Microsoft
SharePoint websites
3.
It is a specialized HTML editor and web freeware for creating or modifying Microsoft SharePoint sites, workflows and web pages,
lists, libraries.
4.we
can customize lists,librariers, designer workflows….
.List:
A list contains items that are collections of
fields/properties/columns.
Optionally each item can have one or more attachments.
. List is a collection
of data, collection of records. This is similar to one of the database. It’s
storing at Content database.
. List having rows and
each rows with appear items, list having fields.
. A list will always
have a default view
. A list in SharePoint
is used to store data across columns in separate rows.
. There are different
data types that can be used for each column.
Library:
A library is a list, but have one and exactly one file associated with each item. A library item also has fields/properties/columns.
A library is a list, but have one and exactly one file associated with each item. A library item also has fields/properties/columns.
A document library is a SharePoint page from
where you can share documents and collaborate on your work. Documents are
shared, protected, and developed amongst your team. Contributors can view
documents in a library, as well as upload, delete, and make changes to
documents.
List vs Library:
Lists:
Can have attachments
Have major versions only
Do not have
Check-in/Check-out features
Libraries:
Cannot have attachments
(files are directly in the library)
Have both minor (draft)
and major (published) versioning
Have Check-in/Check-Out
Publishing Libraries can
use Page Layouts
Have Unique Document Ids
out of the box.
Document library: Document libraries Consist of your core
documents. An example would be a word document, excel, PowerPoint, vision, pdf
Form
Library:
A form library is much
like a document library, but it is supposed to host only Microsoft InfoPath
forms. Microsoft InfoPath is electronic form-creation software that integrates
with SharePoint. Forms created with InfoPath can be published to SharePoint
form libraries, and users can then fill out these forms.
XML
editors or XML-based form design programs that are compatible with Windows
SharePoint Services,
Web.Allowunsafeupdates: If your
code modifies(WSS) 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.
->For
developer, when updates needs to be done in the content database without
requiring a security validation then AllowUnsafeUpdates property needs to be
set to true. After operation is performed then this property again needs to set
to false again.
Moss:
Sahrepoint
server 2010:
MOSS (sp2007)
Features
SharePoint Server 2010 Features
Portal
Sites
Search
Communities
Enterprise Content
Management
Content
Business Process and
Forms
Search
Business Intelligence
Insights
Collaboration
Composites
Moss features:
1) Portal: Provides Single Infrastructure for
Intranet, Extranet, Internet, a common navigation across multiple sites and
include some customized site templates
2) Collaboration: MOSS allows users to share information and
work together and provides a hub
3) Enterprise Content
Management: Content management
was previously called Microsoft’s Content Management Server 2002. Now release
with MOSS 2007.
4) Enterprise Search: New to MOSS 2007 ability to find relevant
content in many different locations and formats. Search results that respect
security permissions.
5) Business
Intelligence: Provides a Report
Centre template, Server calculations, web, rendering and Key Performance
Indicator (KPI) lists and Web parts.
6) Business Process
Provides built-in workflow: and
allow you to create, maintain, and analyze custom workflows, helps you to
streamline your collaborative processes.
SharePoint2010 Main
Features:
Document Collaboration
Document Collaboration
Enterprise Search
FAST Search
New Enhance Web
Part
Silver Light web part
Business Connectivity
Services
Social Media Investments
Large lists
Enhanced collaboration
features
Visio Services
Usage reporting and
loggin
Better Network
Differencing & SharePoint Offline in SharePoint Workspace
High Availability/
Disaster Recovery Innovatio.
Admin Insights through
the Logging & Usage database, and dev dashboard
Service
Applications
SharePoint
Designer Enhancements like portable
workflows, and granular delegation
workflows, and granular delegation
Sandbox Solutions
WSS vsMOSS2007:
.WSS in not a
portal, it's only a collaborative platform (there are no publishing features in
WSS)
.MOSS allows you to use
user profiles, not WSS.
.Search functionalities
are cheap in WSS compare to MOSS (but you can extend them using
Search
Server Express)
.Many others: InfoPath,
BDC, Additional Web Parts, Additional site and list templates.
Site collection:
A site collection is a grouping of websites under a common top-level site that have the same owner and share administration settings,
A site collection is a grouping of websites under a common top-level site that have the same owner and share administration settings,
for example,
permissions. When you create a site collection, a top-level site is
automatically created in the site collection.
You can then
create one or more subsites below the top-level site.
A site collection is
made up of one top-level site and all sites
it is the top level of
organization in a SharePoint 2013 web application.
The number of site
collections you can have in a single web application depends on the capacity of
your server infrastructure.
Sub sites:
è Top-level Web sites can have
multiple sub sites, and sub sites can also have multiple sub sites. You can use top-level Web site and sub sites to
divide site content into distinct, separately manageable sites.
List Defination:
è we can create a List
Definition using:
è 1)
SharePoint user interface
è 2)
Visual Studio 2010
è
Site definition:
1. Site definition is
installed on file system of web front ends.
2. Located
at..\14\Templates\Site Templates.
3. Site definition
consists of .aspx pages and .xml files with Collaborative Application Markup
Language (CAML).
4. Major Benifit is that
the page and List definition is read locally from the File System, not from
Content Database.
Site definition vs Site
template:
Files are on disk, better performance.
|
Files are in database, less efficient.
|
Highly customizable and extensible (XML and .NET code is
much more flexible than UI)
|
Not easily extensible (You are limited by what UI offers)
|
Can provision multiple webs *
|
Can only provision one web
|
Complex to create
|
Easier to create
|
Requires admin access to server for deploying.
|
Installable from a Web UI by site owners.
|
Modifying the site definition after provisioning at least one
site from it is not supported and might break existing sites.
|
Custom templates can be modified without affecting existing sites
that have been created from the templates (**).
|
Site Definitions are
stored on the hard drive of the SharePoint front end servers. They are used by
the SharePoint application to generate the sites users can create. Site
Templates are created by users as a copy of a site they have configured and
modified so that they do not have to recreate lists, libraries, views and
columns every time they need a new instance of a site.
Event
Receivers: If you want to catch some action in SharePoint
and want to do something on each action, then you can use event receivers’.
Event receivers are nothing but classes.
Sometimes they are called before events and after events.
Types also includes :
1) Item-Level Event Receivers
2) List-Level Event Receivers,
3)Web-Level Event Receivers,
4)Workflow Event Receivers
1) Item-Level Event Receivers
2) List-Level Event Receivers,
3)Web-Level Event Receivers,
4)Workflow Event Receivers
Event Handler: It is a similar of the
Event receivers. Event Receivers or Event
handlers are created to handle the basic actions or events against an item,
list\library, a web or a site. 4 types of
• List Items –
SPItemEventReceiver
• List Columns – SPListEventReceiver
• Site – SPWebEventReceiver
• Email – SPEmailEventReceiver
• List Columns – SPListEventReceiver
• Site – SPWebEventReceiver
• Email – SPEmailEventReceiver
Event Receivers vs. Event
Handler:
Event Receivers or Event
handlers are created to handle the basic actions or events against an item,
list\library, a web or a site.
There are two kinds of events in SharePoint. They are:
1) Synchronous Events: Like Item adding (not added yet), Uploading (document not uploaded yet) etc.
2) Asynchronous Events: Item Added (after item is added), Uploaded(after a document is uploaded)
Events receivers can be written to override an event.
For e.g. Item Added event to change the name of an Item once it is added.
There are two kinds of events in SharePoint. They are:
1) Synchronous Events: Like Item adding (not added yet), Uploading (document not uploaded yet) etc.
2) Asynchronous Events: Item Added (after item is added), Uploaded(after a document is uploaded)
Events receivers can be written to override an event.
For e.g. Item Added event to change the name of an Item once it is added.
SharePoint Farm:
ð A SharePoint Farm
is a collection of one or more sharepoint server which
having a single configuration database.
having a single configuration database.
ð A SharePoint farm is a
collection of SharePoint servers or SQL servers that
work in concert to provide a set of basic SharePoint services
that support a single site.
ð Farm solutions are installed to the
solution store of a farm by a farm administrator. The components in the
solution can, and usually do, run in full trust, and no resource usage
restrictions are placed on them.
Content type:
A Content Type is a
reusable, shareable metadata. The base type of a content type could be an
existing content type like: item, Document, Folder, Event, Task,
Meesage, Cooment, Post…..
-> We can create
content types in SharePoint by the following 3 ways:
a. From UI
b. Using CAML (Collaborative Application Markup Language)
c. Using SharePoint Object Model (i.e. Programmatically)
a. From UI
b. Using CAML (Collaborative Application Markup Language)
c. Using SharePoint Object Model (i.e. Programmatically)
-> We can associate
one content types to multiple lists and libraries
Organizations
can define each of these different sets of documents as a content type. A
content type is a group of reusable settings that describe the shared
attributes and behaviors for a specific kind of content. Content types can be
defined for any item type, including documents, list items, media files, and
folders.
Site Content Type:
List Content Type:
Metadata:
1. Managed Metadata is a hierarchical collection of terms that can be associated with items in SharePoint 2010.
2. We can use Central Administration website to manage these terms.
1. Managed Metadata is a hierarchical collection of terms that can be associated with items in SharePoint 2010.
2. We can use Central Administration website to manage these terms.
This is a new feature
in SharePoint 2010.
Example: You have a document library to upload
articles. For each item you can specify a column metadata of category
like C#, ASP.NET etc.
Term: A term is keyword
that can be associated with a SharePoint item.
Term Set:
A term set is a group of terms. You can restrict that a particular item
should contain a term from a particular term set. For example: setting
the category of an article item from term set [C#, ASP.NET].
Local Term Sets: Site collection scoped term set. Only site user can see
it.
Global Term Sets: Global Term Set created outside the site collection.
They are visible to all users.
http://www.codeproject.com/Tips/401716/SharePoint-2010-Managed-Metadata-Configuration-and
Farm Solutions: The scope of farm level solution is farm level so it has Full trusted access to all resources and functionality of
SharePoint.
Sandbox solution vs Form solution
In SharePoint 2010 we can have two types of
solutions one is Sandboxed Solution and Farm Solution while developing a
solution in Visual Studio 2010.
One major difference in the deployment is Farm solutions are installed and deployed. Sandboxed solutions are uploaded and activated.
One major difference in the deployment is Farm solutions are installed and deployed. Sandboxed solutions are uploaded and activated.
Farm Solutions:
- Farm solutions are hosted in the IIS worker process (W3WP.exe).
- If you run any code in farm solution the whole farm will got affected.
- If you deploy any feature or retract any feature the whole application pool got recycled.
- Since they are scoped as farm level, they have full trust access to all the resources.
- When the Sandboxed Solution property is set to False, selecting Build\Deploy will deploy the solution to the Farm Solution Gallery.
- Farm solutions are hosted in the IIS worker process (W3WP.exe).
- If you run any code in farm solution the whole farm will got affected.
- If you deploy any feature or retract any feature the whole application pool got recycled.
- Since they are scoped as farm level, they have full trust access to all the resources.
- When the Sandboxed Solution property is set to False, selecting Build\Deploy will deploy the solution to the Farm Solution Gallery.
Sandboxed Solution:
- Sandboxed solutions are hosted in the SharePoint user code solution worker process (SPUCWorkerProcess.exe).
- The process runs under a CAS policy that restricts programmatic access to any resource outside the sandbox.
- Never restart the IIS application pool.
- If you run any code it will affect only the site collection of the solution.
- Helpful if you have shared hosting.
- When the Sandboxed Solution property is set to True, selecting Build\Deploy Solution deploys the solution to the site collection Solution Gallery.
we create use with
sandbox:
list definition
list instances
webparts
event receivers
Feature receivers
Designer workflows
infopath busines logics
1.we can't create
Aplication pages in Sandbox solutions.
2.Beacuse Application pages are stored in the 14\TEMPLATES\_LAYOUTS and when we deploy as sandbox we dont have permissions to the physical folder.
3.We cant use code to connect to the external web services or to database in the sandbox soltion
4.runwithelevatedprivileges doesn't work
5.Site collection adminstrator can deploy a Sandboxed solutions,
2.Beacuse Application pages are stored in the 14\TEMPLATES\_LAYOUTS and when we deploy as sandbox we dont have permissions to the physical folder.
3.We cant use code to connect to the external web services or to database in the sandbox soltion
4.runwithelevatedprivileges doesn't work
5.Site collection adminstrator can deploy a Sandboxed solutions,
Templates: Site template, Web template, Library
template, List template
Custom Templates:
These
templates can be located at C:\Program Files\Common Files\Microsoft Shared\web
server extensions\15\TEMPLATE\1033.
->Advantages of
having custom templates.
->You can
control the Look and feel of the web site page.
->You can have your
predefined custom web parts.
->Not required to drag
and drop web parts.
->Same look and feel
across the web site page.
Httphandler: Every
request into an ASP.NET application is handled by a specialized component known
as an HTTP handler. The HTTP handler is the most important ingredient while
handling ASP.NET requests
In use
with sharepoint you need to deploy your code to in the GAC.
ASP.NET default
handlers:
Page Handler (.aspx) -
Handles Web pages
User Control Handler
(.ascx) - Handles Web user control pages
Web Service Handler
(.asmx) - Handles Web service pages
Trace Handler
(trace.axd) - Handles trace functionality
Using
SharePoint 2010, the HTTP handler was deployed to the LAYOUTS folder. The trick
here is that SharePoint needs to load all its referenced assemblies from the
GAC and in this case the assembly was in the GAC but we were not referencing
the FQDN of the assembly.
Webpartzones:
Web Parts located in a
Web Part zone When
a Web Part is located inside a Web Part zone, the Web Part properties are
stored in the content database in Windows SharePoint Services 3.0, not in the
ASPX page. By inserting a Web Part inside a zone, you make it possible for
users to interact with or modify that Web Part through the browser.
Web Parts not located in
a Web Part zone When
a Web Part is not located inside a Web Part zone, the Web Part properties are
stored in the ASPX page and not in the content database in Windows SharePoint
Services 3.0. By inserting a Web Part without enclosing it in a zone,
Application page and Site Pages:
Application page: Application
pages are shared across all sites on the server, whereas a site page is
specific to one site.
To create an application
page, add an Application Page item to a SharePoint project. When you
create an application page, Visual Studio adds the following folders to your
project:
-> Application page is an ASP.NET content page present LAYOUTs
directory
“C:\Program Files\Common
Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS “
a. . An application
page can have code behind as well as inline code
b. . An application
page doesn’t support web parts or web part zones
c. .
Application page is available to all the sites,
d. . Application
page must deployed only in farm solution,
Site Pages:
1. Site Pages are stored in the virtual file
system in the Content databases
2. Site page can’t have code behind or inline
code.
3. Site
Pages supports web parts
4. Site page can be deployed only specific sites
5. Site Page can be deployed using a sandbox
solution
6. Site pages can be deployed by site collection
administrators/end-users.
Master page:
-> Page layouts contains is a field controls and Web Parts
-> Page layouts contains is a field controls and Web Parts
Master pages and page layouts dictate the overall look and feel of your
SharePoint site
->you can quickly change the appearance of an entire site.
->This article shows you how to create and modify a copy of the existing primary master page and then apply the new or modified master page to all of the pages in your site that are attached to the primary master.
->you can quickly change the appearance of an entire site.
->This article shows you how to create and modify a copy of the existing primary master page and then apply the new or modified master page to all of the pages in your site that are attached to the primary master.
Master pages contain controls that are shared across
multiple page layouts, such as navigation, search, or language-preference for
multilingual sites.
->Master pages and content pages work together using a set of replaceable regions, or content placeholder controls
-> inside content placeholders in your SharePoint 2010 page layout. Although you can place text and HTML markup inside placeholders, most often you put fields, controls, containers, and Web Parts in your page layout.
Here are multiple control types that you can put in a page layout to contain content:
Web Parts/Web Part zones:
HTML controls:
ASP.NET controls:
sharepoint controls
dataview controls
Content controls:
content fields
Page-layouts:
->Master pages and content pages work together using a set of replaceable regions, or content placeholder controls
-> inside content placeholders in your SharePoint 2010 page layout. Although you can place text and HTML markup inside placeholders, most often you put fields, controls, containers, and Web Parts in your page layout.
Here are multiple control types that you can put in a page layout to contain content:
Web Parts/Web Part zones:
HTML controls:
ASP.NET controls:
sharepoint controls
dataview controls
Content controls:
content fields
Page-layouts:
Master pages and page layouts dictate the overall look and feel of your SharePoint site.
Master pages contain
controls that are shared across multiple page layouts, such
as navigation, search, or language-preference for multilingual sites. Page
layouts contain field controls and Web Parts
By using master pages,
you can provide a consistent look and feel for your site. You can use master
pages to position items that must be shared by all pages, such as navigational
controls, company logos, and copyright notices. Within master pages, you can
use user controls (.ascx controls), Web server controls, and Web Parts.
v4.masterpage:
V4Materpage in a one of
the primary page in masterpage.
->Team Site home
page, list and library pages, and site settings page.
->Used for
content and administration pages. Provides the interface and layout for
SharePoint 2010.
Minimal
master page:
The
home and search results pages on a Search Center, pages that host Word
or Excel web applications.
Contains
minimal SharePoint content, used for full-screen functionality or embedded
applications.
What is
solution:
Ans. Solutions are the container packages for Features. Solution basically, is a cabinet (.cab) file with extension .wsp which contains various components needed to be deployed (features, web parts, custom forms etc) along with files that describe some important metadata about those Components. Once a Solution is installed on a server in the farm, you can deploy it to any web application from your Solution Management
Ans. Solutions are the container packages for Features. Solution basically, is a cabinet (.cab) file with extension .wsp which contains various components needed to be deployed (features, web parts, custom forms etc) along with files that describe some important metadata about those Components. Once a Solution is installed on a server in the farm, you can deploy it to any web application from your Solution Management
Security levels in
SharePoint:
Full Control: Enables
users to have full control of the website.
Design:
Enables users to view, add, update, delete, approve, and customize items
or pages in the website.
Contribute: Enables users to
manage personal views, edit items and user information, delete versions in
existing lists and
document
libraries, and add, remove, and update personal Web Parts.
Edit:
Enables users to manage lists.
Read:
Enables users to view pages and list items, and to download
documents.
View only: Enables users to view application pages. The
View Only permission level is used for the Excel Services
Viewers
group.
Limited Access: Enables users to
access shared resources and a specific list, document library, folder, list
item, or document.
If you use a site template other than the team site template, you will see a different list of default SharePoint permission levels. For example,
1. Approve 2. Manage Hierarchy 3. Restricted Read
If you use a site template other than the team site template, you will see a different list of default SharePoint permission levels. For example,
1. Approve 2. Manage Hierarchy 3. Restricted Read
Limited Access
cannot be edited or deleted.
Special Permissions
Site level Controls access to the site
and any objects that inherit their permissions from the site.
List or library level Controls access to the list
and all folder and items in the list that inherit their permissions from the
list.
Folder level Controls access to the
folder itself and any items in that folder that inherit their permissions from
the folder.
Item level or document
level Controls
access to a specific list item or a document.
Where are Master Pages and Layout Pages located in
a SharePoint site?
They are location in master Page(Master Page
Gallery) under _catalogs folder of root site.
- See
more at:
http://sharepointknowledgebase.blogspot.in/2012/12/sharepoint-developer-interview-questions.html#sthash.UgUlZkFD.dpuf
2010
vs 2013
Developement changes
Socail and collaboration
Fetures
Search
Enterprise Content
Mangement
Server
object model , Client object model , silverlight and javascript..
interview Questions
for Developers - A four-part series.
Managed
Object Model
|
Microsoft.SharePoint
.Client.dll
Microsoft.SharePoint
.ClientRuntime.dll
|
ISAPI
folder
|
Silverlight
client object model
|
Microsoft.SharePoint
.Client.Silverlight.dll
Microsoft.SharePoint
.Client.Silverlight.Runtime.dll
|
LAYOUTS\ClientBin
folder
|
JavaScript
client object model
|
SP.js
|
LAYOUTS
folder
|
Different types of
Objects:
Server object model
|
Managed Model
|
Silverlight Model
|
Javascript Model
|
SPContext
|
ClientContext
|
ClientContext
|
ClientContext
|
SPSite
|
Site
|
Site
|
Site
|
SPWeb
|
Web
|
Web
|
Web
|
SPList
|
List
|
List
|
List
|
SPListItem
|
ListItem
|
ListItem
|
ListItem
|
SPField
|
Field
|
Field
|
Field
|
SandBox Solutions support the following SharePoint item
types:
- List definitions
- List instances
- Content Types/Fields
- Navigation
- Web Parts derived
from WebPart
- Event receivers
- Custom Workflow
Actions
- Workflow
- Doesn’t Supported
- programmatic workflow
- Event receivers
o SPLimitedWebPartManager
- timer jobs
- visual WebParts
- SharePoint mapped folders (e.g.
"_layouts", and "images")
SharePoint
2010's Content Query Web Part(cqwp):
1. Content Query Web Part(cqwp) contains we can get items list items , library documents , content types from different sites
and sub-sites Or Entire site-collection
2. we can configure to filtering , audience targeting
3.If u want create cqwp
First you need to activate Fetures is "SharePoint server publishing infrastructure"
4. After then u can get the cqwp in webpart gallary
2. we can configure to filtering , audience targeting
3.If u want create cqwp
First you need to activate Fetures is "SharePoint server publishing infrastructure"
4. After then u can get the cqwp in webpart gallary
SharePoint
2010's Content Editor Web Part(cewp):
->Content Editor Web Part to add
formatted text, tables, hyperlinks, and images to a Web page.
Ways
you can use the Content Editor Web Part
-You
can use the Content Editor Web Part to add:
->An
introductory, formatted paragraph to a page.
->
A table of instructions to explain a chart on your page, the data that is used
in the chart, and how the chart was created.
->A
set of hyperlinks to more information
Difference
between List Definition, List Template and List Instance in SharePoint
2010:
List
Definition:
A
list definition defines
a schema for a SharePoint list. It contains information on what views are
being used, which columns and content types are being used, and other metadata
information.
List
Template:
A
list template can
either be created by end users through the SharePoint user interface
using an existing list as a pattern or using an existing list instance. If
based on a user-created list it is called a custom list template. A custom list
template includes everything that defines the list, including list columns and
site columns used by the list, content types used by the list, views defined
for the list, and so on
What is an InfoPath?
InfoPath is an XML
based electronic forms development product.
InfoPath is an application to create XML based Data entry Forms and targeted for end users and developers.
- How to deploy Infopath form in Sharepoint site?
->If you customize a SharePoint list form with InfoPath, just click the Publish button. If you create a Browser form, you can publish it to a Forms Library, either as a content type or an actual library item.
->InfoPath List Forms do not support any kind of code. InfoPath browser forms do support code.
->Ability to convert Word and Excel documents into InfoPath form templates.
->we can create infopth form for new sharepoint list
we can create customize an existing sharepoint list
->in that infopath designer in there having field pane.
InfoPath is an application to create XML based Data entry Forms and targeted for end users and developers.
- How to deploy Infopath form in Sharepoint site?
->If you customize a SharePoint list form with InfoPath, just click the Publish button. If you create a Browser form, you can publish it to a Forms Library, either as a content type or an actual library item.
->InfoPath List Forms do not support any kind of code. InfoPath browser forms do support code.
->Ability to convert Word and Excel documents into InfoPath form templates.
->we can create infopth form for new sharepoint list
we can create customize an existing sharepoint list
->in that infopath designer in there having field pane.
Linq
What is LINQ and why it’s
useful in LINQ?
LINQ is Language
integrated Query Language. It’s part of .Net framework, you can easily
integrate this with SharePoint 2010. It’s used to Query on Data sources such as
Object, Datasets, SQL, XML and other entities. LINQ provide access to
sharepoint in TYPED Manner, you can easily access List columns name as
property. As syntax is same as it is for .net development.
var items = from s in DataContext.Students
select s;
Microsoft SharePoint 2010 brings support for Language-Integrated Query (LINQ) to the
platform, which can improve the productivity and efficiency of
developers reading and writing to SharePoint lists.
1. LINQ to SharePointprovider and the SPMetal.exe utility.
2. SharePoint developers can write LINQ queries. At compile time, the LINQ queries will be translated to CAML queries.
LINQ to SharePoint is a new feature of SharePoint 2010. LINQ stands for Language Integrated Query which is a part of .NET. The aim of LINQ is to support different data sources using the same Typed Query Syntax. Presently it supports Objects, Datasets, SQL, Entities, XML, etc.
CAML:.
CAML - Collaborative Application Markup Language
Ø XML- Extensible Markup Language based query
language
Ø Used to perform a query operation against
SharePoint Lists
CAML stands for Collaborative Application Markup Language. CAML
is XML based language which provides data constructs that build up the
SharePoint fields, view, and is used for table definition during site
provisioning
1. CAML is always better
than LINQ because if you write LINQ query then finally it converts in CAML
internally so it down the performance.
2. Of course there is other advantages of LINQ like: Sorting/filtering/can return objects /
3. Most imp part, it is object oriented etc.
2. Of course there is other advantages of LINQ like: Sorting/filtering/can return objects /
3. Most imp part, it is object oriented etc.
Disadvantages of using Linq:
1. During the run time the LINQ query itself gets converted into a
CAML query, which is an extra step ahead that takes more time . This can be avoided
if we write a CAML query itself straight away.
2. Also, we generate a DataContext class
using the SPMetal.exe. This class is the one which we use in our project to
generate LINQ queries. This class is not generated dynamically. So, if
we do any changes in any of the lists or libraries in our site it is not
reflected in the DataContext class. We have to generate a new class whenever we
make any changes in the site.
3. Unlike CAML queries, LINQ to
SharePoint has no use if we are going to access SharePoint data in Silverlight using
Client Object Model.
4. Fields like Created, CreatedBy,
Modified and ModifiedBy of a SharePoint list are not created by SPMetal to be
used in the LINQ queries.
5. LINQ to SharePoint cannot be
implemented for an External list.
Client Object Model
Microsoft SharePoint 2010 Software Development
Kit (SDK) introduces three new client APIs that allow you to interact with
SharePoint sites from script that executes in the browser
1. from code (no earlier than Microsoft .NET Framework 3.5) that executes in a
.NET managed application, or
2. from code that executes in a Microsoft Silverlight 2.0
application.
3.; The new ECMAScript (JavaScript, JScript),
The following table shows the equivalent
objects that the new APIs provide
for common SharePoint Foundation 2010 server objects.
Client Object Model vs
Server Object Model in SharePoint 2010 ?
Using Client Object
Model we can access the data from the system where SharePoint server is not
installed on the machine via Web Services, API(application porgramming
interface) , JavaScript etc.
Whereas In Server Object
Model is like a Production Server Environment to access the data where share
point server installed on the machine
workflow
1). The workflow feature in Microsoft
SharePoint Server 2010 enables solution architects, designers, and
administrators to improve business processes.
2). SharePoint Foundation 2010 workflows are made available to end-users at the list or document-library level. Workflows can be added to documents or list items. Workflowcan also be added to content types.
3). Multiple workflows can run simultaneously on the same item, but only one instance of a specific workflow can run on a specific item
2). SharePoint Foundation 2010 workflows are made available to end-users at the list or document-library level. Workflows can be added to documents or list items. Workflowcan also be added to content types.
3). Multiple workflows can run simultaneously on the same item, but only one instance of a specific workflow can run on a specific item
Fundamentally, a workflow consists of two things:
1. The forms that a workflow uses to interact with its users and the logic that defines the workflow’s behavior.
2. Understanding how workflows are created requires
knowledge about both.
Workflow's
are associated with List , Library, Site
content type , Site
Benefits
of using workflows
The primary benefits
of using workflows are to facilitate business processes and improve
collaboration.
Workflow life cycle:
SharePoint workflow cycle is very
much unique to SharePoint environment. SharePoint workflows are always
connected in context with SharePoint content like list or a document.
There are four stages in the SharePoint workflow cycle. They are
There are four stages in the SharePoint workflow cycle. They are
Associate: Association forms address how the workflow applies to a specific
list, library, or content type. In this stage, workflow is associated with a content type like
list or a document.
Association forms are displayed to
administrators when they first decide to add—or associate—a workflow with a
particular list, document library, or content type.
Initiate: Initiation forms address how the workflow applies to a specific
SharePoint item. In this stage, the workflow created
is to be initiated. Workflow are noting but classes. So a workflow instance
needs to be created to start the workflow in action.
Initiation forms are displayed to users
when they start a workflow on a specific SharePoint item.
Modify: In
third stage, the instance of the workflow is modified as per the workflow
stages.
Complete: Finally the workflow object is terminated.
Site
definitoin
A site definition is the basic blueprint for a site.
-> site definition consists of .aspx pages and .xml files with Collaborative Application Mark-up Language (CAML).
-> major benefit is that the Page and List definition is read locally from the file system, not from Content Database.
A site definition in Sharepoint consists of two parts
ONET.xml: Contains the bulk of the actual site definition
WEBTEMP.xml: it contains This is a collection of templates which are defined by ONET.xml files.
-> site definition consists of .aspx pages and .xml files with Collaborative Application Mark-up Language (CAML).
-> major benefit is that the Page and List definition is read locally from the file system, not from Content Database.
A site definition in Sharepoint consists of two parts
ONET.xml: Contains the bulk of the actual site definition
WEBTEMP.xml: it contains This is a collection of templates which are defined by ONET.xml files.
Feature
A SharePoint Feature is a Functional component that can
be used for activated and deactivated at various scopes throughout
a SharePoint instances, scope of which are defined as
Feature Scopes
FARM - Activate
Feature for an entire server farm.
WEB APPLICATION -
Activate Feature for all websites in a web application.
SITE -
Activate Feature for all websites in a site collection.
WEB -
Activate Feature for a Specific website.
Features have their own receiver architecture, which allow you to trap
events such as when a feature is Installing, Uninstalling, Activated, or
Deactivated.
Feature Components:
We can create menu commands, 1)Custom Actions
2)page templates 3)page instances, 4)list definitions, 5)list instances,6)event
handlers,7)web parts 8)workflows as feature.
Timer job
1. A Timer Job is a periodically executed task inside SharePoint
Server.
2. It provides us a task execution environment.
3. These tasks will having execution periods like:
Minute, hour, day, week, monthly, yearly
There are many timer jobs inside SharePoint which do internal tasks like:
: Send emails
: Validate sites
: Delete unused sites
: Health analysis
: Product versioning
: Diagnostics
Timer Jobs can be
scheduled for automating jobs inside SharePoint 2010
SPJobDefinition is the base class for Timer Job
Create Event Receiver
Feature to create or delete the timer job
SPFeatureReceiver is the base class for the event receiver
The feature gets
deployed in the 14hive folder
OWSTIMER.EXE is
the process executing Timer Jobs
SPSecurity.RunWithElevatedPrivileges
Method
RunWithElevatedPrivileges
Method:
Executes the specified method with Full Control rights even if the user does not otherwise have Full Control.
A delegate method that is to run with elevated rights. This method runs under the Application Pool identity, which has site collection administrator privileges on all site collections hosted by that application pool.
Executes the specified method with Full Control rights even if the user does not otherwise have Full Control.
A delegate method that is to run with elevated rights. This method runs under the Application Pool identity, which has site collection administrator privileges on all site collections hosted by that application pool.
SPSecurity.RunWithElevatedPrivileges(delegate()
{
using (SPSite site = new
SPSite(web.Site.ID))
{
// implementation details omitted
}
});
BCS
Microsoft Business
Connectivity Services (BCS) (formerly
named the Business Data Catalog) provides read/write access to external data
from line-of-business (LOB) systems, Web services, databases, and other
external systems
within Microsoft
SharePoint 2010 and Microsoft Office 2010 applications.Both SharePoint 2010 and Office 2010 applications have product features
that can use external data directly, both online and offline.
Developers can gain access to a rich set of features and rapidly build
solutions using familiar tools such as Microsoft Visual Studio 2010 and Microsoft SharePoint Designer 2010.
Business Connectivity
Services enhances Office application and SharePoint application capabilities
and their user interface (UI) through features, services, and tools. These
enhanced capabilities and UI streamline development of solutions with deep
integration of external data and services. Experienced users, developers, and
business unit IT professionals can integrate assets from external systems and
enable interaction with the external data through many types of Office client
and server applications.The Business Connectivity Services feature set
enables rapid development and deployment of scalable and security-rich
solutions. The following diagram shows a high-level view of Business
Connectivity Services.
Explain the Share Point
Architecture:
Having 3 layers, like 3 tire architecture
1. WFE (Front End Web Server>) 2. Application Layer 3. Data base Layer
1. WFE (Front End Web Server>) 2. Application Layer 3. Data base Layer
1.Front End WEB Server
-
Here we have share point
Installed.
We have 12-hive
structure & virtual drives.
Here IIS web sites are
hosted.
Here servers are
clustered on & are in synch.
2. Application
Layer: -
SharePoint provides
different services.
This layer provides
those services, like my site hosting, user profile & searching etc.
One server can be
dedicated to particular service depend upon the scalability.
3. Data Base Layer:
-
Here we have SQL server
installed.
Here content DB is
hosted.
For moss 2007, it is SQL
server 2005. For Share Point 2010, it is SQL server 2008.
Here servers are
clustered on & are in synch.
Web Service
|
Description
|
WebSvcOrganizationProfileService
|
Provides an
interface for remote clients to read and create organization profiles.
|
Provides a published
links interface for remote clients to read and create published links.
|
|
Provides methods
that can be used to remotely query SharePoint Server search.
|
|
Provides an
interface for remote clients to read, create, and manipulate social data.
|
|
Provides a user
profile interface for remote clients to read and create user profiles.
|
|
Provides a user
profile interface for remote clients to read and create user profiles.
|
Difference between
Stored Procedure and Function?
Function are compiled
and executed at run time.
Stored Procedure are
stored in parsed and compiled format in the database.
Function cannot affect
the state of the database which means we cannot perform CRUD operation on the
database.
Stored Procedure can affect
the state of the database by using CRUD operations.
Store Procedure can
return zero or n values whereas Function can return only one value.
Store Procedure can
have input, output parameters for it whereas functions can have only input
parameters.
Function can be called
from Stored Procedure whereas Stored Procedure cannot be called from Function.
What is LINQ to
Sharepoint ?
|
|
Ans.
|
· LINQ is a feature of the programming
languages C# 3.0 and Visual Basic .NET
· LINQ adds, to each of the languages, a
SQL-like syntax and vocabulary for querying data sources.
· LINQ to Sharepoint allows developers to use
SQL-like syntax to query Lists and Libraries in Sharepoint.
· LINQ to Sharepoint internally converts the
LINQ query to a CAML query to fetch records
· Advantage : Strongly typed access to the
entities of the list.
· Disadvantage : If the new columns are added
or its datatype changed, the datacontext class used by LINQ is no longer
valid and may break the code
|
1 - What is the difference between CustomMasterUrl & MasterUrl?
Ans. MasterUrl is used
to change the layout of all use end pages but CustomMasterUrl is for changing
the layout of admin side pages.
2- What are the zones in SharePoint?
- Zones provides
the separate logical paths of authentication for the same web application
- We can create 5
zones for each web application as follows :
a.Default
b.Intranet
c.Extranet
d.Internet
e. Custom
What is Shredded Storage?
With Shredded Storage feature enabled, every document and the Changes made to the document, is stored in SQL as multiple “Shredded BLOBS“. Whenever a new Version of a document is Created, only the BLOBs of the document that Corresponds to the Change are saved as opposed to the entire document as a new version.This feature helps to lower down the amount of storage required for saving files.
With Shredded Storage feature enabled, every document and the Changes made to the document, is stored in SQL as multiple “Shredded BLOBS“. Whenever a new Version of a document is Created, only the BLOBs of the document that Corresponds to the Change are saved as opposed to the entire document as a new version.This feature helps to lower down the amount of storage required for saving files.
3-What is a DWP?
The file extension of a web part.
share point Installed.
12-hive structure & virtual drives.
IIS web sites are hosted.
servers are clustered on & are in synch.
2. Application Layer
Share Point provides different services.
This layer provides those services, like my site hosting, user profile & searching etc.
One server can be dedicated to particular service depend upon the scalability.
3. Data Base Layer
Here we have SQL server installed.
Here content DB is hosted.
For moss 2007, it is SQL server 2005. For Share Point 2010, it is SQL server 2008.
Here servers are clustered on & are in synch.
* Every layer has load balancer for control the traffic.
What is Diff between BDC and BCS
BDC- Business data Catalog
BCS-Business Connectivity Service
Business data Catalog:
BCS-Business Connectivity Service
Business data Catalog:
- Connect to External Database and view in share point
- we can only read in database
- Its new in SharePoint 2010
- Itw we have Read and write in database
Sharepoint Architecture
We have 3 layer architecture
WFE <Front End Web Server>
2. Application Layer
3. Data base Layer
1. WFE
2. Application Layer
3. Data base Layer
1. WFE
share point Installed.
12-hive structure & virtual drives.
IIS web sites are hosted.
servers are clustered on & are in synch.
2. Application Layer
Share Point provides different services.
This layer provides those services, like my site hosting, user profile & searching etc.
One server can be dedicated to particular service depend upon the scalability.
3. Data Base Layer
Here we have SQL server installed.
Here content DB is hosted.
For moss 2007, it is SQL server 2005. For Share Point 2010, it is SQL server 2008.
Here servers are clustered on & are in synch.
* Every layer has load balancer for control the traffic.
Custom Feature
Create xml file named feature.xml and its manifest file. save file to 12- hive \template\feature.
How to install feature file?
Go to command prompt, navigate 12- hive bin folder & run the command.
Stsadm -0 installfeature –filename <filelocation+name>
How to Activate feature?
Go to command prompt, navigate 12- hive bin folder & run the command.
Stsadm -0 activefeature –name <name> -url <url>
How to Deactivate feature?
Go to command prompt, navigate 12- hive bin folder & run the command.
Stsadm -0 deactivefeature –name <name> -url <url>
How to uninstall feature?
Go to command prompt, navigate 12- hive bin folder & run the command.
Stsadm -0 uninstallfeature –filename <filelocation+name>
How to install feature file?
Go to command prompt, navigate 12- hive bin folder & run the command.
Stsadm -0 installfeature –filename <filelocation+name>
How to Activate feature?
Go to command prompt, navigate 12- hive bin folder & run the command.
Stsadm -0 activefeature –name <name> -url <url>
How to Deactivate feature?
Go to command prompt, navigate 12- hive bin folder & run the command.
Stsadm -0 deactivefeature –name <name> -url <url>
How to uninstall feature?
Go to command prompt, navigate 12- hive bin folder & run the command.
Stsadm -0 uninstallfeature –filename <filelocation+name>
How to Deploy WSP file?
In command promt Navigate to 12 hive Folder after write Commant line
STSadm -o addsoultion -filename filelocation
Then go to "central administration -> operations" under "global configuration" there is "solution management" click on that.
Then click on "wsp file name", and then click on "deploy solution" for deploy it, for retrieve click on "retrieve solution", for remove it click on "remove solution" after retrieve it.
STSadm -o addsoultion -filename filelocation
Then go to "central administration -> operations" under "global configuration" there is "solution management" click on that.
Then click on "wsp file name", and then click on "deploy solution" for deploy it, for retrieve click on "retrieve solution", for remove it click on "remove solution" after retrieve it.
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|||||||||||||||
|
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
PowerShell
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
Workflow
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
Event Receiver
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
||||||||||||||
|
CUSTOMIZATION QUESTIONS
3. 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....
5. 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.
6. 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.
7. 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).
8. 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.
10. 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 LoadQuery() collections go out of scope at the end of IEnumerable<List> list.
11. 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.
12. 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.
13. What data type does REST return?
REST does not return an object of type SharePoint Site\List. Instead, it returns an XML output.
14. 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.
15. 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.
18. How is a Content type deployed?
Content Type can be deployed and associated with list using feature.
19. 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.
20. 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.
21. 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.
22. 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
24. 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.
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.
25. 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.
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.
26. 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.
2- By SharePoint Designer.
3- By editing minimal.master using editor.
27. 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.
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.
28. 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
29. 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.
30. 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.
2- Themes can also be created with the help of Visual Studio.
31. 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.
32. 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.
33. 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.
34. 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"/>
35. 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.
36. 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.
37. 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
38. 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
39. 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.
40. 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.
42. 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.…
web application level,
site collection level,
web level, etc.…
43. 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
44. 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.
45. 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.
46. 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.
47. 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.
49. 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.
1- WSP builder via Visual Studio and activate solution from central admin.
2- Using STS Command, firstly install and then activate.
50. Where the feature receiver file needs to be deployed?
The feature receiver file needs to be deployed in Global Assembly cache (GAC).
51. 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.
52. 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.
53-. 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.
54-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.
55. 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:2. Application of tags in SharePoint 2010: The document libraries are configured to use metadata as a primary navigation pivot and improves search.
1. Use of tags: It is easy for a site to use enterprise wide tags and taxonomies, and easy for users to apply them.
A. http://blogs.msdn.com/b/besidethepoint/archive/2011/11/13/sharepoint-timer-job-locks-and-scope.aspx
Timer Job base Class: SPJobDefinition
Timer Job worker process: OWSTimer.exe
SPJobLockType: 3 Types
1. None
2. ContentDatabase
3. Job
Member name
|
Description
|
None
|
Provides no locks. The timer job runs on every machine in the farm on which the parent service is provisioned, unless the job I associated with a specified server in which case it runs on only that server (and only if the parent service is provisioned on the server).
|
ContentDatabase
|
Locks the content database. A timer job runs one time for each content database associated with the Web application.
|
Job
|
Locks the timer job so that it runs only on one machine in the farm.
|
RealTime Sharepoint Interview Questions 5
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?
.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.
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.
When running with SPSecurity.RunWithElevatedPrivileges (web context) what credentials are being used?
In a web context, this is the application pool identity. In a timer job and workflow, this will be the 'Windows SharePoint Timer Services' identity.
When should you dispose SPWeb and SPSite objects? And even more important, when not?
You should always dispose them if you created them yourself, but not otherwise. You should never dispose SPContext.Current.Web/Site and you should normally not dispose SPWeb if IsRootWeb is true. More tricky constructs are things along the line of SPList.ParentWeb.
Also dispose each web when iterating over SPWeb.Webs
Also dispose SPLimitedWebPartManager's SPWeb property (.web)
What base classes do event receivers inherit from?
SPListEventReceiver, SPItemEventReciever, and SPWebEventReceiver inherit from the abstract base class SPEventReceiverBase.
SPWorkflowLibraryEventReceiver inherits from SPItemEventReceiver.
SPEmailEventReceiver inherits directly from System.Object.
What are the built in ways to backup a SharePoint install?
A: Through the central administration and the stsadm command
(more advanced) You've created and deployed a Web Part, when you deploy to the server you get a page saying your Web Part couldn't be loaded, click here to go to the Web Part maintenance page, etc. to disable the web part. What step(s) should you take to get a stack dump from your web part instead of that error page?
Go to the web.config file for your website and find the CallStack Attribute in the SafeControls element and set the value to true
How would you programmatically retrieve a list item?
SPQuery and SPSiteDataQuery. Bonus points for knowledge of CrossListQueryCache, PortalSiteMapProvider. Negative points for use of foreach.
What are the data types which are supported as Lookup column in SharePoint.
Only Single Line of Text and Calculated columns are supported as lookup columns.
how can debugging share point application and timer jobs ? with steps?
- build application place .dll into gac and reset iis
- On the Debug menu, select Attach to Process
- select the Show processes from all users check box.
- select W3W.exe and OSWTIMER.exe can attach
- refresh sharepoint site point break point
what is web part?
Web Parts are the fundamental building blocks for Share Point user interface, and with them we can build and integrate many different types of applications.In share point also be create custom web part using .oscx control
steps create custom web part
- create web part project copied .oscx control and build application.place .dll file in GAC .reset IIS.
- go 12 hive _layout folder create folder past your .oscx control
- go inetpub ->wwwroot->wss->open Your site ->web con fig->create safe control write assembly information of web part application
- open sharepoint site ->site action-site editing->Galleries ->web part->new Add your web part.
- Content Editor Web Part
- Data View Web Part
- List View Web Part
- Image Web Part
- Members Web Part .
- Page Viewer Web Part
What are the advantages of SharePoint Portal Services (SPS) over SharePoint Team Services (STS)?
harePoint Portal Services (SPS) has MUCH better document management. It has check-in, check-out, versioning, approval, publishing, subscriptions, categories, etc. STS does not have these features, or they are very scaled back. SharePoint Portal Services (SPS) has a better search engine, and can crawl multiple content sources. STS cannot. STS is easier to manage and much better for a team environment where there is not much Document Management going on. SPS is better for an organization, or where
No comments:
Post a Comment