21 .Types of Pages in SharePoint ?
1. Application Page
They are same as ASP.net Pages and stored on the
layouts folder of SharePoint front end web server. When user requests , application
pages are compiled and they are much faster than Site Pages. Admin Pages like
settings.aspx, accessdenied.aspx are an example of Application Pages. Thus we
can say that Application pages are common to all SharePoint Users
2. Master Page
Master
pages define the common layout and interface for SharePoint pages. Master page
defines the shared framing elements of your site. These elements may include
the header and footer, top navigation, breadcrumbs, search box, site logo, and
other branding elements.
3. Site Definition
Page
4. Layout Page
A page layout is a template for a specific type of
page in your site, such as an article page or a product details page. Just like
its name implies, you can think of a page layout as defining the layout or
structure for the body of a page. Page Layout is part of SharePoint publishing
features, which are the Web content management features of SharePoint.
5. Site Page
These Pages are stored in the Content Database and
they are parsed when requested by user. A typical web part page is an example
of Site Pages. They can be edited, modified by the Power Users and customized
according to their needs.
5.1.
Web Part Page
Pages inheriting from
Microsoft.SharePoint.WebPartPages.WebPartPage containing a number of
WebPartZones where the developer/end user can add web parts to control what the
page shows/can do. In previous versions of SharePoint very common and very
powerful.
5.2.
Wiki Pages
The new way of creating content pages. Very similar
to web part pages, but instead of having multiple web part zones it usually
only have one which is hidden. It then has a Wiki field which can easily be
edited and can contain markup which will make the web parts from the hidden
zone appear inline in the content (as divs)
It can be combined with multiple WebPartZones to
allow more control of placement of web parts.
5.3. Publishing
Pages
The standard type of pages in publishing sites. The structure of the
content is very much controlled by the page layouts, usually very limited use
of web parts. Very good for making the site look consistent.
22 .What Onet.xml file ?
1) Onet.xml file specifies all the components contained in a site. It is considered as the core of a site definition.
2) It is present at following location:
%SharePoint Root% \TEMPLATE\SiteTemplates\XML\Onet.xml
23 .What is difference between
Sandbox and Farm solution ?
LDifference
Base
|
FARM SOLUTION
|
SANDBOX SOLUTIONS
|
WORKER PROCESS
|
Farm solutions are hosted in the IIS worker
process (W3WP.exe)
|
Sandbox solutions are hosted in the SharePoint
user code solution worker process (SPUCWorkerProcess.exe)
|
BUILD \ DEPLOY LOCATION
|
It deploys the solution to the Farm Solutions
Gallery.
|
Windows SharePoint Services 2010 has a feature
that's known as the "site collection solution gallery."
Site Actions >> Site Settings>>Solutions
link under Galleries in the SharePoint
site. Solution galleries are repositories of solutions that enable site
collection administrators to manage solutions in their site collections.
|
ACTIVATION
|
Farm solutions are installed and deployed.
|
Sandboxed solutions are uploaded and activated.
|
VISUAL WEB PARTS
|
Yes, we can create Visual web parts in Farm
Solutions.
|
No, you can’t create Visual web parts in Sandbox
Solutions.
|
APPLICATION PAGES
|
We can create Application pages in Farm Solutions.
|
Sandbox solutions can’t create Application pages
as Application pages are stored in the hive. Sandbox solutions do not have
permissions to the physical folder.
|
AFFECT
|
Farm solutions can affect the whole farm as they
are hosted in the IIS worker process (W3WP.exe).
|
Sandboxed solutions, are hosted in the SharePoint
user code solution worker process (SPUCWorkerProcess.exe), run code that can
only affect the site collection of the solution.
|
IIS APPLICATION POOL RECYCLE
|
In Farm solution, the IIS application
pool recycles before SharePoint retracts or deploys the feature so as to
release any files locked by the IIS worker process. Only the IIS application
pool serving the SharePoint project’s site URL is recycled.
|
SPUCWorkerProcess
process that the SPUserCodeV4 service in SharePoint automatically triggers
and controls. It is not necessary for the SPUCWorkerProcess process to
recycle to load the latest version of the solution
|
DEBUGGER
|
Visual Studio attaches the debugger to the
W3WP process.
|
Visual Studio attaches the debugger only to
SPUCWorkerProcess processes running the current site.
|
FULL TRUST
|
Since they are scoped as farm level, they have
full trust access to all the resources on the farm,
|
Since they are scoped as site collection level,
they do not have full trust access to all the resources/ physical folder on
the farm.
|
24. What is difference between SP
Online and on Premise ?
Basic
Differences
SP On Premises
|
SP Online
|
- The
SharePoint server farm is within the corporate network.
- The
IT Support team maintains the SharePoint farm and regularly applies
Microsoft patches and updates.
- On
premise, Active directory is used for authentication.
- Full
access to use and customize any SharePoint feature as needed.
- Availability
of Enterprise level services such as BCS, Performance Point, etc.
|
- The
SharePoint sites reside in the Microsoft Data Centre (MDC).
- Microsoft
applies the patch regularly.
- Microsoft’s
SLA ensures 99.9% availability.
- Microsoft’s
global network of data centers provides reduced latency and high
network bandwidth.
- Support
for Client Side Object & App model.
|
Feature
Comparisons – All the basic functionality of SharePoint remains the
same, there are a number of significant feature differences between On
Premises and Online
Category
|
On Premises
|
Online
|
Product Features
|
Support for enterprise feature, Office web App (OWA)
needs to be installed
|
Missing or limited features, pre-configured features
|
Infrastructure deployment & maintenance
|
IT Support Team to deploy/manage farm, latest updates or
patches not always deployed.
|
Microsoft manages the environment and ensures all
updates and patches are deployed.
|
Business Continuity (BC)
|
Dependent on internal capabilities.
|
Microsoft built-in redundancy and failover for data
centers, but does not provide end user backups or data recovery.
|
Cost Involved
|
Purchase/Maintain Hardware, Software licenses etc.
|
Annual subscriptions for Office 365 Plans billed on a
per user basis.
|
Customization Options
|
Full support for server side code and client side code,
App usage from OAC and SAS
|
Full Support- Client Side, Limited Support-Server side,
can use Apps from OAC or SAS
|
Compliance Standard
|
Dependent on internal capabilities.
|
Verified by third party authors
|
Information Security
|
Dependent on internal capabilities.
|
Information in MDS meets industry-specific security
standards
|
Storage needs
|
Expensive storage devices, Site Collection -More than
100GB, Scalable Storage Size
|
Cheap storage cost, Site Collection- up to 100Gb,
Maximum content in single tenant -O365 plan based
|
Development
|
Full trust solution can be deployed- Features in farm
solutions can have scope as wide as the site collection, web application,
or whole farm Public facing website with much of customization is possible
Custom “Managed Path” allowed More control can be delegated to power users
|
Full trust solution and Sandbox cannot be deployed-
Allowed More control cannot be delegated to power users and maxim privilege
level is Site Collection level.
|
Technical
Comparisons –
Services
|
Online
|
On Premises
|
Search
|
Limited access to query
|
Full text Query
|
InfoPath Form Services
|
Only in E3, E4 and K1 plans
|
Required License to use InfoPath Form Services
|
Claim Bases Authentication
|
N/A
|
Can use SQL , LDAP and AD authentication
|
Managed Accounts
|
N/A
|
Provides a Managed Account to user at access the SP
Admin Services
|
Usage reporting and Logging
|
N/A
|
Provides LOGS and Reporting to check the exceptions and
System Report.
|
Alternate Access Mapping
|
N/A
|
Provides a map requests where the URL of a Web request
received by Internet Information Services (IIS) differs from the URL that
was typed by a user
|
SharePoint Health Analyser
|
N/A
|
Site collection pre-upgrade health check examines a site
collection and then generates a report listing ay potential upgrade issues
and how to address the issues
|
SharePoint OnPrem
Prons and Cons
Pros
|
Cons
|
Control Performance
|
Cost of internal resources (staff, hardware, software,
etc)
|
Scale Up and Scale Out
|
Additional Geographic redundancy costs
|
Reduces Bandwidth requirements
|
Disaster Recovery dependent on internal capabilities
|
Fully Customizable
|
Scale Up/Out Cost( SW/HW)
|
Full Server and SQL Database
|
Patching Servers/farms
|
Migrate as Needed
|
Extra configurations for External Collaboration
|
Seamless Single Sign on with Corporate Active Directory
|
|
SharePoint
Online Prons and Cons
Pros
|
Cons
|
Uptime 99.99%
|
More ISP Bandwidth
|
Multiple Data centers
|
Limited Customizations
|
Geographically redundant
|
Possible Storage Costs
|
Shorted release cycle
|
Recovery SLAs
|
Managed Services (SaaS)
|
No Server access
|
Pay as you go (Low Cost)
|
|
Reduced impact on internal IT resources
|
|
Scalability
|
|
|
25. What are Apps in SharePoint 2013?
Apps in SharePoint 2013 is a self-contained pieces
of functionality that extend the capabilities of a SharePoint website. An app
may include SharePoint components such as lists, workflows, and site pages, but
it can also surface a remote web application and remote data in SharePoint.
Sandbox Solutions introduced in SharePoint 2010 are
deprecated in 2013 to encourage the usage of Apps,
Custom code in Apps will be executed in
Client-Browser or in some other scope
like IIS or Windows Azure, which is completely out of SharePoint scope
Apps never run in the context of SharePoint Server,
but they will run in the context of the browser or in the context of the hosted
platform.
Apps are isolated and by default, apps are deployed
to their own web site in an isolated domain, in new App Model of SharePoint,no
server-side code can be deployed to the SharePoint servers. Keeping custom code
off SharePoint servers provides re assurance to SharePoint administrators that
the App can’t harm their servers
In SharePoint 2013, you can develop 3 type of Apps
SharePoint Hosted Apps (SharePoint Apps also known
now SharePoint Add-ins)
Provider Hosted
Autohost Apps.
Thank you very much
Fahadullah Karimi
SharePoint Specialist
No comments:
Post a Comment