1.
ASP.Net webpart vs.
SharePoint webparts
Table 1. Decision matrix
for creating Web Parts
Create a custom ASP.NET 2.0 Web Part
|
Create a SharePoint-based Web Part
|
·
For most business
needs.
·
To distribute your
Web Part to sites that run ASP.NET 2.0 or SharePoint sites.
·
When you want to
reuse one or more Web Parts created for ASP.NET 2.0 sites on SharePoint
sites.
·
To use data or
functionality provided by Windows SharePoint Services 3.0. For example, you
are creating a a Web Part that works with site or list data.
|
·
When you want to
migrate a set of Web Parts using the SharePoint-based Web Part infrastructure
to Windows SharePoint Services 3.0.
·
To create cross page
connections.
·
To create
connections between Web Parts that are outside of a Web Part zone.
·
To work with
client-side connections (Web Part Page Services Component).
·
To use a
data-caching infrastructure that allows caching to the content database.
|
2.
New Features in SharePoint 2010
Sites:
- Ribbon User Interface
- SharePoint WorkSpace (Sync Framework)
- SharePoint Mobile
- Standard Support
Communities:
- Rating
- Inline editing support for Wiki Pages/Blogs
- RSS Activity Feeds (Similar to Alerts but feed based)
Composites:
- Business
Data Connectivity Services
- External
List
- Silverlight
and AJAX Support
- Workflow
(Site Level and Workflow draft)
- SharePoint
Designer Changes
- Visual
Studio 2010 Support
- Event
receivers enhanced (Site deletion/Web App Provision/Deletion etc.,)
- User
Interfaces
- API
Enhancement - LINQ to SharePoint/ COM & REST/ATOM
Search:
- Social Relevance and Ranking
- Phonetic Search (examples B2B etc.,)
- Better Search Navigation
- FAST Integration
- Extensible framework - Search Connector Framework
Insight:
- Performance
Point Services
- Excel
Services
- Visio
Services (Web Browser Support)
- 2D/3D
Chart Web parts
- SQL
Server BI Technologies Integration
- Power
Pivot
Content:
- Audio/Video content types for streaming
- Digital Media Assets for DRM (Digital Rights
Management)
- Document Set
- Tagging/Tag clouds & Taxonomies
- Social Bookmarking
- Org Browser
- Profiles- Other directories integration
Developer Features in SharePoint 2010:
- Large List Throttling
- Referential Integrity & Join support to List
Columns
- Event Receivers support to Custom Error Pages
- Ranking Support
- Validation Support to List and Columns
- Event Receiver Post Synchronous Execution Support
- VS 2010 Projects, Item Templates for Lists/Schema
Definitions
- BDC services support for column definitions
- Visio Based workflow design support
- Reusable workflow support
- Site Workflow support - Capture Site Events
- VS 2010 Project Item Templates for Workflow
Customization of UX
- Developer Dashboard for Debugging/ Tracing
- Silverlight Web part Support
- PowerPoint based Theme Design
- Theme Preview Support
- API Enhancements
- Client Object Model
- LINQ to SharePoint
- ADO.NET Data Services/ Web Services/ REST
- Silverlight Client Object Model
- ECMA Script library support
- Application services Architecture (SSP - Not extensible
for custom services. Everything or none)
- Scalable - Shared across farms
- Extensible
- On demand basis usage
- Access Services
- Business Data Connection Services
- Excel Calculation Services
- Metadata Management Services
- Claims based Authentication Support
- Unified Logging Services & Correlation ID Support
- Resource Governance/ Throttling
- Record Management Features (at Site Collection Level)
- Multi lingual Support in the same site instead of
Variations
- Audio/Video Content Types – Streaming
- Document Set
- Remote Blob Storage Support (for large files)
- Visio/Excel/Word/Access Webpage
- Profile Import - Sources Enhanced (AD, LDAP,BDC,
Custom)
- Sandboxed solution deployment support
- Health Monitoring Support
- End to End PowerShell Support. More than 500 cmdlets
- SCOM Management Pack Support
3. ECMA
SCRIPT SHAREPOINT 2010 or Client Object Model
Managed Client
DLL's needed : Microsoft.SharePoint.Client.dll, Microsoft.SharePoint.Client.Runtime.dll. Find these files in the 14/ISAPI folder. Usually, the location would be at "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI".
Silverlight
Microsoft.SharePoint.Client.Silverlight.dll and Microsoft.SharePoint.Client.Silverlight.Runtime.dll. They find at "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\ClientBin".
ECMAScript
SP.js file - The file fund at "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS".
SharePoint object model syntax:-
Server side syntax Client side syntax
DLL's needed : Microsoft.SharePoint.Client.dll, Microsoft.SharePoint.Client.Runtime.dll. Find these files in the 14/ISAPI folder. Usually, the location would be at "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI".
Silverlight
Microsoft.SharePoint.Client.Silverlight.dll and Microsoft.SharePoint.Client.Silverlight.Runtime.dll. They find at "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\ClientBin".
ECMAScript
SP.js file - The file fund at "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS".
SharePoint object model syntax:-
Server side syntax Client side syntax
SPContext
ClientContext
SPSite Site
SPWeb Web
SPList List
SPSite Site
SPWeb Web
SPList List
<script type=”text/ecmascript” src=”/_layouts/SP.Core.js”
/>
<script type=”text/ecmascript” src=”/_layouts/SP.Debug.js” />
<script type=”text/ecmascript” src=”/_layouts/SP.Runtime.Debug.js” />
<script type=”text/ecmascript” src=”/_layouts/SP.Debug.js” />
<script type=”text/ecmascript” src=”/_layouts/SP.Runtime.Debug.js” />
Or
<SharePoint:ScriptLink ID=”ScriptLink1″ Name=”sp.debug.js”
LoadAfterUI=”true” Localizable=”false” runat=”server” />
4. Content types
A
content type is a reusable collection of settings that you want to apply to a
certain category of content. Content types enable you to manage the metadata
and behavior of a document, item, or folder in a centralized, reusable way
5. Site coloumn
A site column entity that allows you to reuse
columns across multiple lists. Site columns are created at the top-level of your team site and can be reused
in any list or library within your entire team site, including subsites.
6. Event
Receivers
Asynchronous means After events, so all
Asynchronous events occur after the event. All Asynchronous events end with
‘ed’ letters like SiteDeleted, FieldAdded, ItemAdded etc
Synchronous events, all Synchronous events occur before the event, which stop the code
to execute. All Synchronous events end with ‘ing’ letters like SiteDeleting,
FieldAdding, ItemAdding etc
Site Events
Site Events
|
Receiver Base Class
|
Event Host Type
|
Web Events
Web Events
|
Receiver Base Class
|
Event Host Type
|
List Events
List Events
|
Receiver Base Class
|
Event Host Type
|
List Field Events
List Field Events
|
Receiver Base Class
|
Event Host Type
|
Item Events
Item Events
|
Receiver Base Class
|
Event Host Type
|
Table 2.
Event receiver base classes and supported events
Event
receiver base class
|
Available
event host types
|
Supported
events
|
· SPSite
· SPWeb
|
· SiteDeleting
· SiteDeleted
· WebAdding
· WebProvisioned
· WebDeleting
· WebDeleted
· WebMoving
· WebMoved
|
|
· SPSite
· SPWeb
|
· ListAdding
· ListAdded
· ListDeleting
· ListDeleted
|
|
SPListEventReceiver (fields)
|
· SPSite
· SPWeb
· SPList
· SPContentType
|
· FieldAdding
· FieldAdded
· FieldDeleting
· FieldDeleted
· FieldUpdating
· FieldUpdated
|
· SPSite
· SPWeb
· SPList
· SPContentType
|
· ItemAdding
· ItemAdded
· ItemDeleting
· ItemDeleted
· ItemUpdating
· ItemUpdated
· ItemFileConverted
· ItemFileMoving
· ItemFileMoved
· ItemCheckingIn
· ItemCheckedIn
· ItemCheckingOut
· ItemCheckedOut
· ItemAttachmentAdding
· ItemAttachmentAdded
· ItemAttachmentDeleting
· ItemAttachmentDeleted
|
|
· SPSite
· SPWeb
· SPList
|
· EmailReceived
|
|
· SPSite
· SPWeb
· SPList
· SPContentType
|
· WorkflowStarting
· WorkflowStarted
· WorkflowCompleted
· WorkflowPostponed
|
7. Timer
Job
These are reflected in the three values of the
SPJobLockType enum: Job, None, and ContentDatabase. Job means the job runs only
once per farm per iteration; None means the job runs once per server; and
ContentDatabase means the job runs once for each content database
Get-SPTimerJob | ? {$_.LockType -eq
"Job"}
Get-SPTimerJob | ? {$_.LockType -eq
"None"}
Get-SPTimerJob | ? {$_.LockType -eq
"ContentDatabase"} | Select-Object -Unique | Sort-Object Name |
Format-Table Name
->Timer Job Base Class is “SPJobDefinition”
Q. SharePoint - Object Hierarchy:-
http://sptechbytes.blogspot.in/2013/01/sharepoint-2010-object-hierarchy.html
Q. Hardware and
software requirements for SharePoint 2013
----------------------------------
Q. Backup and Restore using PowerShell;-
Back up farms:-
Backup-SPFarm -Directory <BackupFolder> -BackupMethod {Full
| Differential} [-Verbose]
Restore farms:-
Restore-SPFarm -Directory <BackupFolder> -RestoreMethod
Overwrite [-BackupId <GUID>]<Type the appropriate cmdlet, including
parameters and values, and enclose the values for the parameters in
"placeholder" tags >
Back up farm configurations:-
Backup-SPConfigurationDatabase
-Directory <BackupFolder> -DatabaseServer <DatabaseServerName> -DatabaseName <DatabaseName> -DatabaseCredentials <WindowsPowerShellCredentialObject> [-Verbose]
Restore farm:-
Restore-SPFarm -Directory <RestoreShare> -RestoreMethod
Overwrite -ConfigurationOnly
Back up web applications:-
Backup-SPFarm -Directory <BackupFolder> -BackupMethod {Full
| Differential} -Item <WebApplicationName> [-Verbose]
Restore web applications:-
Restore-SPFarm
-Directory <BackupFolderName> -RestoreMethod Overwrite -Item
<WebApplicationName> [-BackupId <GUID>] [-Verbose]
Back up service applications:-
Backup-SPFarm -Directory <BackupFolder> -BackupMethod {Full
| Differential} -Item <ServiceApplicationName> [-Verbose]
Restore service applications:-
Restore-SPFarm –Directory <BackupFolder> -Item " <ServiceApplicationName> "
-RestoreMethod Overwrite [-BackupId <GUID>] [-Verbose]
To restore all the service applications, at the Windows PowerShell
command prompt, type the following command:
Restore-SPFarm -Directory <BackupFolder> -Item "Farm\Shared Service
Applications"
-RestoreMethod Overwrite [-BackupId <GUID>] [-Verbose]
Back up User Profile service applications:-
Backup-SPFarm -Directory <BackupFolder> -BackupMethod Full
-Item Farm\Shared Services\Shared Service
Applications\<ServiceApplicationName> [-Verbose]
Restore a User Profile Service service application:-
Restore-SPFarm -Directory <BackupFolder> -Item Shared
Services\Shared Services Applications\<ServiceApplicationName>
-RecoveryMethod Overwrite [-BackupId <GUID>] [-Verbose]
Back up Search service applications:-
Backup-SPFarm
-Directory <BackupFolder> -BackupMethod {Full | Differential}
-Item “<SearchServiceApplicationName>” [-Verbose]
Restore Search service applications:-
Restore-SPFarm -Directory <BackupFolder> -Item
"<ServiceApplicationName>" -RecoveryMethod Overwrite [-BackupId
<GUID>] [-Verbose]
When you restore a Search service application, it is automatically
paused. To resume the Search service application when the restore has
completed, type the following command:
$ssa = Get-SPEnterpriseSearchServiceApplication
<SearchServiceApplicationName>
$ssa.ForceResume($ssa.IsPaused())
Back up the Secure Store Service:-
Backup-SPFarm -Directory
<BackupFolder> -BackupMethod Full -Item <SecureStoreService
> [-Verbose]
Restore Secure Store Service:-
Restore-SPFarm -Directory
<BackupFolder> -Item <SecureStoreServicename> -RecoveryMethod
Overwrite [-BackupId <GUID>] [-Verbose]
After the restore operation has successfully completed, you must
refresh the passphrase. At the Windows PowerShell command prompt, type the
following command:
Update-SPSecureStoreApplicationServerKey -Passphrase
<Passphrase>
Back up content databases:-
Backup-SPFarm -Directory
<BackupFolder> -BackupMethod
{Full | Differential} -Item <ContentDatabaseName> [-Verbose]
Restore content databases:-
Restore-SPFarm
-Directory <BackupFolder> -RestoreMethod
Overwrite -Item <ContentDatabase> [-BackupId <GUID>] [-Verbose]
Attach and restore a read-only content database:-
Attaching a content database by using the Mount-SPContentDatabase cmdlet differs from attaching
a database in SQL Server by using SQL Server tools. Mount-SPContentDatabase associates the content
database with a Web application so that the contents can be read.
Mount-SPContentDatabase
-Name <DatabaseName> -WebApplication <WebApplicationID> [-Verbose]
Restore content from unattached content databases:-
You can restore or copy content, such as sites, site collections,
lists, or document libraries, from a content database without having to attach
the content database to the farm.
Get-SPContentDatabase -ConnectAsUnattachedDatabase -DatabaseName <DatabaseName>
-DatabaseServer <DatabaseServer>
Back up databases to snapshots :-
CREATE DATABASE <snapshot name>
ON
(
NAME=<logical name of the database file>,
FILENAME = 'c:\WSS_Backup1.ss')
AS SNAPSHOT OF <database name>;
Back up solution packages:-
Backup-SPFarm -backupmethod full -directory <UNC location>
-item "farm\solutions"
Here: 1. <UNC location> is the UNC location of the directory
that you want to back up to.
2. To back up a
single solution, add the name of the solution to the item path
"farm\solutions"
Back up site collections:-
Backup-SPSite -Identity <SiteCollectionGUIDorURL> -Path
<BackupFile> [-Force] [-NoSiteLock] [-UseSqlSnapshot] [-Verbose]
Get-SPSite | format-list -property id,url
Restore customizations:-
Restore-SPFarm -Directory <BackupFolder> -RestoreMethod
Overwrite -BackupId <GUID> -Item <SolutionPath>
Restore site collections:-
Restore-SPSite -Identity <SiteCollectionURL>
-Path <Backup file>
[-DatabaseServer <DatabaseServerName>]
[-DatabaseName <ContentDatabaseName>] [-HostHeader <Host
header>] [-Force] [-GradualDelete] [-Verbose]
Back up apps:-
The app for SharePoint content and packages are in the SharePoint
2013 content databases in individual site collections. All app for SharePoint
license and security data is stored in the App Management Service and the
Secure Store Service application databases. Additional app for SharePoint data
is stored in the SharePoint 2013 configuration database, in the form of
Internet Information Services (IIS) web sites or web applications, and Web Part
packages. You must back up the following SharePoint 2013 databases at the same
time:
·
Content
·
Configuration
·
Secure Store Service application
·
App Management service application
If you have to eventually restore the databases, you have to
restore the same version of each database that you backed up. In other words,
don't restore a content database that's six months older than the configuration
database.
Restore apps:-
The apps for SharePoint can reference the following SharePoint
2013 databases which you may have to restore. You should also restore the site
collection where the app for SharePoint is located if you are restoring the
apps for SharePoint to the same environment.
·
Content
·
Configuration
·
Secure Store Service application
·
App Management service application
Restore-SPSite -Identity <SiteCollectionURL>
-Path <Backup file>
[-DatabaseServer <DatabaseServerName>]
[-DatabaseName <ContentDatabaseName>] [-HostHeader <Host
header>] [-Force] [-GradualDelete] [-Verbose]
Export sites, lists, or document libraries:-
Export-SPWeb
-Identity <SiteURL> -Path <Path and File
Name> [-ItemUrl <URL of Site, List, or
Library>] [-IncludeUserSecurity] [-IncludeVersions] [-NoFileCompression] [-GradualDelete] [-Verbose]
Import a list or document library:-
Import-SPWeb -Identity
<SiteURL> -Path
<ExportFileName> [-Force]
[-NoFileCompression] [-Verbose]
http://sptechbytes.blogspot.in/2013/01/sharepoint-2010-object-hierarchy.html
Q. Sandbox
Solutions in SharePoint 2010
A. Sandboxed
Solutions worker process: SPUCWorkerProcess.exe
Q.
Timer Job
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.
|
Q.
Which zone we are using for FBA (form based authentication)
A. Extranet
Q.
Explain Zone in SharePoint
A. Zones represent
different logical paths (URLs) of gaining access to the same Web application.
You can use zones to enforce different access and policy conditions for group
of users.
Zones provide a method to partition users by:
·
Authentication type (ex:
claims-based authentication, windows authentication)
·
Network zone (ex:
extranet, Internet)
·
Policy permissions (ex:
allow or deny read or write access)
Each Web application can have a maximum of 5 zones. The 5 possible
zones are:
·
Default
·
Intranet
·
Internet
·
Custom
·
Extranet
When you create a Web application, the Default zone is created.
You can then extend the Web application to create other zones.
Each zone can only be selected once per Web application. For
example, you can only have one Default zone in a Web application.
Each zone is represented by a different Web site in IIS.
Q. Explain
Authentication type in SharePoint
SharePoint
2013 Supported authentication types and methods
SharePoint
2013 supports a variety of authentication methods and authentication providers
for the following authentication types:
·
Windows
authentication
·
Forms-based
authentication
·
SAML
token-based authentication
Windows
authentication
The
Windows authentication type takes advantage of your existing Windows
authentication provider (AD DS) and the authentication protocols that a Windows
domain environment uses to validate the credentials of connecting clients.
Windows authentication methods, which are used by both claims-based
authentication and classic mode, include the following:
·
NTLM
·
Kerberos
·
Digest
·
Basic
Forms-based
authentication
Forms-based
authentication is a claims-based identity management system that is based on
ASP.NET membership and role provider authentication. Forms-based authentication
can be used against credentials that are stored in an authentication provider,
such as the following:
·
AD
DS
·
A
database such as a SQL Server database
·
An
Lightweight Directory Access Protocol (LDAP) data store such as Novell
eDirectory, Novell Directory Services (NDS), or Sun ONE
Forms-based
authentication validates users based on credentials that users type in a logon
form (typically a web page). Unauthenticated requests are redirected to a logon
page, where a user must provide valid credentials and submit the form. The
system issues a cookie for authenticated requests that contains a key for
reestablishing the identity for subsequent requests.
Q. Difference
between allowunsafeupdate and runwithelevatedprivileges
A. AllowUnsafeUpdates: 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.
RunWithElevatedPrivileges : 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.
Q.
Explain about ‘Web Analytics’ in SharePoint
“Web
Analytics” will provide insights into the behavior of users of your SharePoint
sites. There are three categories of
reports that you will find:
1. Traffic reports: These reports provide metrics such as:
1. Traffic reports: These reports provide metrics such as:
§ How much traffic
your site gets (Number of Page Views);
§ Who visits your
sites (Top Visitors);
§ How visitors arrive
at your site (Top Referrers);
§ Daily Unique
Visitors, Top Destinations, Top Browsers, etc;
2. Search
reports: These reports give you insight into what users are searching for, for
example:
·
How
many times users searched (Number of Queries);
·
What
were the most used search terms (Top Queries);
·
What
queries have high failure rates (Failed Queries);
·
Best
Bet Usage, Search keywords, etc;
3. Inventory
reports: These reports display key metrics regarding the inventory of your
sites:
·
What
is the total disk drive space user (Storage Usage);
·
How
many sites exist (Number of Sites);
·
Top
Site Product Versions, Top Site Languages, etc;
We
aggregate these reports aggregated at the following levels:
1.
Per
web application in the farm
2.
Per
site collection
3.
Per
site
4.
Per
search service application
Q. Deployment
Commands using PowerShell:-
A. 1.
Add-SPSolution "allwsps\firstwsp.wsp"
2. Install-SPSolution
-WebApplication "[Site Collection URL]" -GACDeployment -FullTrustBinDeployment -Identity
firstwsp.wsp -CompatibilityLevel All
à On each SharePoint machine that is
a front-end web server, in the PowerShell command line tool, execute the following
command
3. Install-SPApplicationContent
4. Enable-SPFeature
-Url "[Site Collection URL]" -Identity onwWspFeature
Q. Hardware and
software requirements for SharePoint 2013
RAM:
8 GB
Processor:
64-bit, 4 cores
Hard
disk space: 80 GB for system drive
Operating System: The 64-bit edition of Windows Server 2008 R2
Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition
of Windows Server 2012 Standard or Datacenter
Database: Microsoft SQL
Server 2008 R2 SP1 - Express Edition
·
.NET
Framework 4.5
·
Windows
Management Framework 3.0
·
Window
Server App fabric
·
WCF
Data Services 5.0
Q. SharePoint
2013: Service Applications list
A.
·
Access
Services
·
Access
Services 2010
·
App
Management Service
·
Business
Data Connectivity Service
·
Excel
Services Application
·
Machine
Translation Service (new in SharePoint
2013)
·
PerformancePoint
Service Application
·
PowerPoint
Automation Services
·
Managed
Metadata Service Application
·
Search
Service Application
·
Secure
Store Service
·
State
Service
·
User
and Health Data Collection Service
·
User
Profile Service Application
·
Visio
Graphics Service
·
Word
Automation Services
·
Work
Management Service Application
·
Microsoft
SharePoint Foundation Subscription Settings Service
Q. SharePoint
2013 - The 15 Hive and other important directories
Q. SharePoint
Page Types:-
Application
and site pages both inherit their layout from the same master page
Site
Page:-
Site
pages are pages that are created, edited, and customized by end users.
They
are primarily used for the content in a site. Site pages come in two types—a
standard page and a Web Parts page.
A
standard page contains text, images, Web Parts, and other elements. A Web Parts
page contains Web Parts in Web Part zones.
They
have a predefined layout that uses Web Part zones.
Both
types of site pages are edited using a Web browser or Microsoft SharePoint
Designer.
Application
Pages:-
Application
pages are used to support application implementations in SharePoint Foundation.
Application
pages are stored on the file system of the front-end Web server in the
%ProgramFiles%\Common
Files\Microsoft Shared\web server extensions\15\TEMPLATE\LAYOUTS directory
Q.
Workflow Types in SharePoint
A
workflow executes from one step to another in two ways. There are two types of
workflows in SharePoint 2010.
1.
Sequential:
The steps within the workflow execute sequentially, one after another.
2.
State
Machine: Its executes in no particular order. A sequential workflow always
progresses forward and never goes back to a previous step. On the other hand, A
state machine workflow moves from one state to another, until the logic
concludes that the workflow has completed.
Sequential Workflow:
A sequential workflow execute sequentially
one after another and always progresses forward and never goes back to a
previous step.
It represents a workflow as a procession
of steps that execute in order until the last activity completed.
The control of the workflow is decided by
the the workflow itself.
State Machine Workflow:
A state machine workflow moves from one
state to another until the logic concludes the workflow has completed and there
is no particular order in execution of each state.
The control of the workflow is decided by
the user.
Q. can
we deploy timerjob as sandbox solution
A.
No, because it is timerjob scope is WebApplication level. For sandbox solution
scope we can’t set WebApplication
Q.
How to Create Custom Tiles in SharePoint 2013
A. http://www.howtosp.com/blog/2012/10/14/sharepoint-2013-create-a-metro-live-tile-programmatically/
Q. BCS
(business connectivity services) external list limitations:-
1.
Workflows
cannot be configured on External Lists
2.
Cannot
create Information Management Policies
3.
No
versioning or version history
4.
No
Inline Editing or Datasheet View
5.
No
ratings
6.
No
ability to Export to Excel, Create Visio Diagram, Open with Access or Open with
Project
7.
No
REST access through ListData.svc to External Lists
8.
No
RSS Feeds
9.
No
Item Level Permissions
10.
No
item or field level validation
11.
No
Lookups
12.
No
attachments
1. WebParts -
Event life cycle of webpart, create child control, deploy webpart, event
controls in webparts, 200 webparts deploy at a time.
Ans.
Defferent life cycle events in webparts
1. OnInit
2.OnLoad
3.CreateChieldControls
4.EnsureChildControls
5.OnPreRender
6.PagePreRenderComplete
7.Render
8.RenderContent
2. wsp -
window sharepoint package, create wsp package, deployment wsp package(makecab
tool)
3. create
feature - how many file containing in feature, feature.xml,
elementmanifest.xml, different scope webpart/feature deployment.
4. audience
targeting.
5. sharepoint
object level hierarchy
Ans. SPFarm,
SPServer, SPService, SPWebService, SPServerInstance, SPDatabaseserverInstance,
SPWebApplication, SPContentDatabase, SPSiteCollection.
6.
sitecollection, differentiate between spsite, spweb
7. splist,
spdocument (difference between them)
8. evaluatedpreviliges(run
with evaluated privileges)
9.
AllowUnSafeUpdate explain.
Ans. Get or
Set a boolean value that specifies whether to allow updates to the database as
result of GET request public bool AllowUnSafeUpdate { get; set; }
10.different
level of trustlevel
11.wss, moss
-> team iste, by browsing how can you find out which one is wss and which
one is moss site.
12. life
cycle of asp.net page
13. view
state -> when will event occur in life cycle
14. save view
state
15. rendering
events
16. server
side code, event side code
17.
validatation controls types
18. code
behind(no), page load, page uploads write same in page load event in line code?
19. server
variables (how many types)->1. session, application(server) 2. cookie,query
string, hidden field, view state(client side)
20.view state
handle or manage
21. ssrs,
ssir, server, transform && response & redirect?
22. reporting
life cycle, controlling process behavior, control cursor behavior,(farvwrd,
static)
23. lock
types explain.
ASP 2.0 Page
Directives:-
---------------------------
1. @Page
2. @Master
3. @Control
4. @Register
5. @Reference
6.
@PreviousPageType
7.
@OutputCache
8. @Import
9. @Implement
10. @Assembly
12.
@MasterType
SQL DML &
DDL :-
---------------------
Data
Definition Language:- The Query and update commands from the DML part of SQL
1. SELECT
2. UPDATE
3. DELET
4. INSERT INTO
Data
Manipulation Language:-
------------------------------
1.CREATE
DATABASE
2. ALTE
DATABASE
3.CREATE TABLE
4.ALTER TABLE
5. DROP TABLE
6.CREATE INDEX
7. DROP INDEX
SQL
Constraints:-
-------------------
1. NOT NULL
2. UNIQUE
3. PRIMARY KEY
4. FOREIGN KEY
5. CHECK
6.DEFAULT
MOSS
Interview Questions:-
-----------------------------
1. stsadm.exe
- required permission to use this tool (wss admin member)
2. security
authentication methods - out of the box
1. NTLM
2.
Kerberos
3.
Window Authentication
3. Deploying
WebPart
4. Security
level of user (viewer, contributor, member...)
5. wss, moss
difference
6.Intaled or
configure of sharepoint ( difference normal and advance installation )
7.
backup/restore - using stsadm.exe tool. how to extension of backup of web
application.
8. working
area's of sharepoint
9. workflow
object model and workflow sharepoint apart from this out-of-the-box.
10.
Limitation of out-of-the-box/sharepoint designer workflows
11.
masterpage-> customization why, how many master pages by default and explain
placeholders
12.
permission- groups of permission (what is default group)
13. dataview
webpart - how to create)
14. content
query webpart - what is publishing feature need or not && what is
content editor webpart and difference between content query & content
editor web part.
15.
publishing site, publishing portal
16. content
type definition.
17. document
mtetadata
18. list /
library difference
19. document
metadata
20. partial
trust in webpart, explain.
21 Security
authentication methods;-
-------------------------------------
Windows:-1.
NTLM 2. Kerberos
Forms:-
1. Sql Membership Provider
2. Active Kirectory Forms Provider
3. Light weight directory acess protocal (LDAP)
4. Custom Provider
Web-Single
Sign On:- 1. Active Directory Federation Service (ADFS)
Q.
SP2010 Search vs FAST
SharePoint
Server 2010
· OOB relevance
· Federated results
· Query Suggestions
· Did You Mean
· Related Searches
· View in Browser
· People Search
FAST
Search Server
· Visual Best Bets
· Thumbnails & Previews
· Sorting on any property
· Similarity Search
· Better language support
· Richer query language
· Multiple relevance profiles
SharePoint
Interview Question:-
---------------------------------
1. how to
convert http to https site?
2. site &
site collection explain
3. how is sql
serer used in sharepoint
4. gosted and
ungosted explain terms.
5. web site
portal -> 10,000 document -> word document -> can i search text in
side document in sharepoint
6. query
optmization search sharepoint using index server
7. you worked
on certificates
8. two
advantages of site collection
9. portal
user active session
10.
difference between post & get
11. how
garbage collector work in dotnet collector ( heap-stack)
12. how we do
create custom web editor webpart.
13.
customization in webpart
14. sql serve
architecturein sharepoint ( database/ tables )
15. deploy /
active a feature
16. reusable
components explain
17. why we go
for custom workflow rather than SPDesigner cusstom workflow? (what is
disadvantage in spdesigner and what is advantage in object model custom
workflow) - Dell interview question.
Ans. 1.
Sequential workflow - sharepoint designer
2. State Machine workflow - visual studio workflow ( Initialize, Association,
Task Edition )
Shared
Service Providers ( SSP ):-
----------------------------------
1. Business
Data Catalog
2. Office
SharePoint Server Search
3. Excel
Services
4. User
Profile Application
5. Session
State
----------------------------------
how to create custom list
new,edit,display form in visual studio
what is schema, element file
in visual studio
how to show column in new,
edit, display form in vs
difference from designer and
vs workflows
expalin about application
server, frent-end server, back-end server and defferences and usages.
where is timerjob dll is deployed/saved
in sharepoint.
where is sandbox solution dll
is deployed/saved in sharepoint
Awesome article! You are providing us very valid information. This is worth reading. Keep sharing more such articles.
ReplyDeletehow Data Science Changing the World Today