►
Description
Webcast around different SharePoint development or customization models. More details on covered topics from blog post at http://dev.office.com/blogs.
A
Welcome
everybody,
this
is
chiffon
patterns
and
practices
of
webcast
and
system
didn't
actually
want
to
have
a
concentration
on
generating
actual
code
or
doing
a
live
demo
or,
let's
say
making
something
fancy
to
happen
from
a
code
perspective,
rather
rather
this
kind
of
an
architectural
discussion
when
you
should
be
using
which
model
within
a
ship
one,
because
we
do
have
different
kind
of
techniques,
different
kind
of
models
which
you
can
use
when
you're
customizing
your
SharePoint
in
SharePoint,
Online
or
in
on
premises.
So
what
would
be
the
right
model
for
you?
A
B
A
Indeed,
indeed,
before
we
actually
move
into
the
actual
topic
and
covering
the
individual
models,
what
we
have
it
in
the
sharepoint
from
a
customization
perspective.
It's
a
quick
introduction
on
a
ship
on
edit
and
preferences,
so
shipment
production
practices
is
a
community
driven
initiative,
open
source
initiative
which
is
providing
code
samples,
kind
of
documentation,
smartly
community
goals,
case
studies
and
the
areas
are
in
the
sharepoint
framework,
ship
and
padding's
max
of
crafts
on
office.
Rated
5
AP
is
both
sharepoint
online
and
then
obviously
on
those
elements
which
are
suitable
in
the
sharepoint
on-premises.
A
The
PMP
is
owned
by
the
sharepoint
engineering,
but
we
work
together
with
community
as
an
open
source
initiative
to
share
all
of
this
assets
for
you
to
get
advantage
and
get
get
a
starting
point
for
your
customizations
and
for
your
project.
Now,
let's
actually
move
back
on
the
today's
topics
and
today's
topics
really
what's
around
the
different
models
on
a
sharepoint
customizations
and
one
thing.
A
What
we
want
to
have
super
super
clear
when
we
are
talking
about
this
individuals
models
is
that
all
of
these
models
are
absolutely
fine
and
we
should
not
say
which
of
the
model
is
the
best
practice,
because
the
best
is
always
depends
on
your
requirements.
So
what
are
you
planning
to
achieve?
What
is
the
right
model
for
you
in
a
short
term
and
in
the
long
term?
So
the
key
points
when
you're
looking
into
this
options
is
really
to
understand.
A
What
are
you
trying
to
achieve
from
our
requirements
perspective
from
a
business,
functional
and
technical
requirements
perspective
and
then
choose
the
right
model
for
you,
so
the
world
is
definitely
not
black
and
white.
From
that
perspective,
we
should
not
go
and
say:
hey.
This
model
is
the
best
practice.
Well,
that's
not
quite
the
case.
It
really
depends
what
are
you're
trying
to
achieve
so.
A
Absolutely
and
that's
actually
a
cute
factor
as
well,
because
one
of
the
factors
to
make
the
right
decision
is
that
if
we
do
have
a
let's
say,
a
development
team
which
do
not
have
experience
on
certain
model,
maybe
not
is
actually
kid
factors
take
into
account.
Do
you
want
to
use
that
model
or
that
that
approach
within
your
customization
and
that
really
comes
down
on
designing
the
right
architecture
for
your
customizations
as
well?
Not
just
making
the
hey
somebody
in
the
internet
said
this
is
the
best
and
coolest
thing
ever.
A
So
let's
actually
concentrate
on
the
individual
models,
and
what
would
want
us
to
do
is
that
we
wanted
to
kind
of
Akko
through
these
models,
one
by
one
and
we're
going
to
start
with
something
classic
and
maybe
classic
it's
actually
a
wrong,
even
a
Kron
term,
because
well,
no
kind
of
classic.
It
is
an
old
stuff.
Yes,
my
sharepoint
classic
solutions
and
with
classic
solutions,
women,
WSB
packages
as
inbound
solutions
or
sample
solutions.
A
It's
now,
however,
when
we're
recording
this
is
2017.
So
actually
the
model
is
ten
years
old,
and
so
it's
kind
of
it's
been
actually
surprisingly
well
taken,
because
people
are
still
using
the
SharePoint
classic
solution
model.
That's
the
primary
way
of
customers
and
SharePoint,
especially
in
on-premises,
and
one
of
the
obvious
advantages.
A
Is
that
there's
a
lot
of
existing
resources
and
guidance
available
in
the
internet,
random,
blog
post
and
also
in
the
Microsoft
MSDN
site
as
well,
and
and
there's
a
native
resource
to
do
tooling
available
for
that
one
as
well
since
2010,
which
actually
got
slightly
even
more
better
in
2013
and
also
there
are
books
out
and
also
the
other
books?
I,
don't
forget
that
absolutely
absolutely
there
are
specific
books
and
there's
electronic
books
on
this
one.
So
really
validated
data
on
that.
A
From
that
perspective,
and
one
of
the
I
would
say
the
key
advantages
of
using
the
SS
pay
packages,
and
especially
if
you're,
using
upon
solutions
when
you
have
access
on
the
server
side
as
well,
is
the
fact
that
the
customizations
are
hosted
natively
in
the
shipment
servers.
So
you
don't
actually
need
to
have
additional
infrastructure.
You
don't
have
to
that.
The
additional
hosting
doesn't
cost
you
additional
maintenance
and
operational
impact,
and
so
on.
Now
that
was
the
advantages.
So
let's
concentrate
on
the
disadvantages
and
why
we
are
we
at
the
Microsoft.
A
We
are
kind
of
a
crutch,
really
moving
away
from
the
SS
pay
packages
and
really
absolutely
supported
in
on-premises
fun
solutions,
simple
solutions
in
online
as
a
declarative,
sandbox
solutions,
but
really
the
reason
why
we're
moving
away
is
the
the
complexity
and
one
and
they
are
not
flexible
enough
and
they're,
not
aligning
on
the
future
direction
of
the
SharePoint
or
the
future
way
of
doing
customizations
in
the
web
in
general
and
the
sense
of
solution.
Code-Behind
is
no
longer
supported
in
SharePoint
Online.
A
That
support
was
discontinued
back
in
Altered
2016
in
on-premises
that
actually
still
works.
If
you
enable
the
code
base
error
code
behind
ancient
in
your
own
premises,
one
form
solutions,
absolutely
understandable,
they're
not
supported
in
SharePoint
Online,
so
that
option
is
completely
closed
as
a
as
a
model
to
customership
at
online
deployment
deployments.
A
Even
though
you
have
been
on
primitive,
the
fun
solution
actually
has
a
lot
of
kind
of
a
let's
say,
downsides
or
disadvantages.
They
directly
impact
on
your
farm
operations
and
maintenance
and,
for
example,
downtime
and
I've
spent
countless
of
weekends
updating,
business-critical
production
deployments
of
customers
started
on
Saturday
morning
and
then
something
went
wrong
with
the
with
the
new
version
of
the
phone
solution
and
then
trying
to
wrestle
fix
the
issue
before
the
Monday
morning
actually
starts
and
the
modern
customizations
don't
do
this.
A
Yes,
you
might
theoretically
prague
individual
basis
or
we
individual
sections,
but
you
don't
actually
take
the
form
down
like
the
phone
solution.
D,
so
they're
also
really
con,
but
you
needed
to
trust
what
the
farm
solution
contained
and
also
from
a
backup
and
restore
perspective.
You
needed
to
make
sure
that
your
content
databases
are
in
sync
with
the
with
the
backups
of
your
customization,
because
if
you
need
to
restore
your
data
or
databases,
you
need
to
make
sure
that
you
have
much
matching
form
solutions
deployed
as
well,
really
the
the
SharePoint
classic
solutions
they
do.
A
They
did
and
do
require
deep,
SharePoint,
specific
knowledge
and
to
truly
master.
If
you
use
the
visual
studio
tooling,
it
might
feel
simple
and
the
v-star
say
I'm
just
clicking
through
stuff
here,
but
that
might
actually
fall
for
you
in
many
times,
because
even
the
even
though
it's
microsoft
generated,
we
saw
it
in
visual
studio.
It
wasn't
really
super
optimal
for
my
future
maintenance
and
versioning
perspectives.
A
B
So
slightly
also
in
a
path
originally
I've
built
a
lot
of
internet
sites,
and
all
of
that
you
could
only
do
with
farm
of
your
feet
and
like
no
one
else,
I
know
what
works.
What
does
not
and
actually
with
regards
to
the
tools.
The
tools
are
there
and
over
time
they
got
better
and
better,
but
the
thing
was
that
you
could
always
do
so
much
more
and
none
of
that
or
not
all
of
that
was
exposed
in
the
tools.
So
tools
only
go
through
the
first
step
of
adding
new
artifacts
creating
them.
B
But
at
some
point
you
really
have
to
understand
how
it
all
works
in
order
to
be
able
to
fine
tune
them
to
your
exact
needs
as
operated
to,
as
you
said,
just
use
a
default
which
might
be
then
a
bad
choice.
You'll
not
run
so
you
really
have
to
understand.
You
basically
have
to
read
all
the
books
that
were
there
at
a
time
in
order
to
fully
understand
the
what
consequences
each
choice
you
make
might
have
in
in
in
a
long
run,.
B
B
A
Absolutely
not
no
string
good,
let's
set
the
WS
with
packages
on
side
for
a
while
and
let's
move
on
the
ond
another
model
which
we
can
use
in
a
SharePoint
of
the
customization
model
as
well,
which
is
to
SharePoint,
adding
more,
which
was
introduced
back
in
2013
or
as
part
of
the
2013
release,
and
now
counting
the
years.
It's
actually
almost
five
years
from
that
time
as
well,
which
is
actually
pretty
terrifying
time
flies
when
you
are
having
one.
It's
really
really
did
one
of
the
key
chat.
A
A
And
so
you
are
essentially
hosting
your
customizations
outside
of
the
SharePoint
in
the
provider
hosted
at
in
platform
or
si
in
the
processor,
when
you're
using
the
SharePoint
hosted
model
and
really
the
same
model
works
across
the
on-premises
and
SharePoint
Online
sure
there
are
some
small
differences
here
and
there's
for
my
authentication
perspective
unless
you're
using
the
load.
Trust
in
on
premises
as
well,
but,
basically
the
same
architecture,
designs
basic
approach
can
be
actually
used
in
both
sites.
Really
really
fundamental,
let's
say
benefit
out
of
that
in
model
as
well.
A
It's
the
security
isolation
and
the
model
actually
approaches
the
whole
thing
in
a
way
that
it,
the
customization,
is
requesting
the
native
permissions
and
you
give
them
them
permissions.
And
then
it's
a
combination
of
the
entry
user
permissions
plus
the
permissions
which,
having
a
crime
that
folder
adding.
So
there
is
an
OAuth
security
isolation
and
the
customizations
are
commonly
executed
in
the.
A
If
you're
thinking
about,
let's
say
the
web
part
experience
they're
executed
in
an
iframe
in
an
isolated
domain,
which
then
falls
on
the
Descent
Landis's
of
the
SharePoint
data
model,
because
with
SharePoint,
the
web
parts
are
pretty
pretty
pretty
important
thing
in
SharePoint.
You
want
to
have
those
things,
your
what
the
end
users
and
then
content
editors,
are
able
to
put
on
the
page
and
configure,
as
as
they
wish,
and
with
adding
model
that
imports
they've
been
pretty
limited
and
stuff
is
running
in
an
iframe
you
can,
it
doesn't
scale,
there's
no
responsiveness.
A
All
of
those
additional
challenges
which
have
been
bothering
us
for
a
while,
with
sharing
with
SharePoint
Alamo
you'd,
also
have
to
have
ownership
on
hosted
aliens,
have
a
limited
application,
lifecycle
management
capabilities,
and
that
really
refers
to
the
fact
that
if
you
have,
let's
say
a
hundred
thousand
sites
where
individual
adding
has
been
installed
or
maybe
not
installed
the.
If
it's
a
SharePoint
hosted
adding
only
ways
you
can
actually
upgrade
that
adding
is
to
go
to
that
site
and
manually
upgrade
that
one
by
one
and
technically
that
does
apply.
A
Storing
data
in
there
adding
width
is
problematic
and
really
a
big
thing
which
we
need
to
understand,
because
now,
if
you
have
a
SharePoint
hosted
on
an
all-pro,
Idaho
stir
that
in
and
they're
storing
data
in
adding
with
the
adding
web
itself
is
created
when
the
instance
of
adding
a
side.
Another
side
when
somebody
deletes
the
add
or
adding
our
app
from
the
side
that
adding
web
is
deleted,
which,
as
a
consequence,
means
that
all
of
the
data
is
gone
and
you
can't
well
right
now.
A
Luckily,
we
do
have
recycle
bin
capabilities
on
the
site
level
as
well,
but
there's
a
fear
that
you
might
actually
lose
all
of
the
data
and
it
can't
access
or
export
that
data
easily
when
it's
actually
stored
in
the
adding
width.
So
that's
not
definitely
not
the
most
recommended
option
to
storing
the
data
and
also
from
a
disadvantages
perspective,
probably
hosted
atoms
require
external
host
things.
A
I
need
to
think
about
where
to
where
do
a
house,
my
stuff,
if
you're
familiar
with
Usher
or
other
cloud
services,
you
might
not
be
a
big
thing
in
on-premises
that
usually
requires
additional
servers,
and
that
might
be
a
challenging
thing
on
privacy.
Setting
model
setup
requires
additional
effort
as
well,
so
this
really
relates
on
the
OAuth
and
the
trusting
model
with
the
add-ins
is
especially
if
you're,
using
a
high
trust
model
in
on-premises
that
might
get
complicated.
A
Actually,
it
isn't
super
complicated
if
you
know
this
stuff,
but
it
might
feel
really
really
complicated
when
you're
setting
up
the
atom
model
in
on-premises.
Now,
let's,
let's
kind
of
a
talk
about
this
one
in
general,
so
few
things
kind
of
a
few
high-level
recommendations
on
this
one.
First
of
all,
kind
of
a
touch
that
already
sharepoint
hosted
aliens
are
always
in
adding
web.
The
problem
with
that
in
width,
first
of
all,
is
that
you
can
lose
the
data,
storing
data
and
adding
web.
A
Not
a
good
idea,
and
the
second
layer
is
really
the
sharepoint
hosted
a
dense
themselves.
The
remote
API
is
exposed
for
JavaScript
are
highly
limited.
So
if
you're
not
super
familiar,
what
you
can
do
with
the
SharePoint
hospital
in
it
might
feel
like
all
some
approach-
I,
don't
it
actually
hosts
my
stuff
anywhere,
but
then
you
start
implementing
stuff,
and
then
you
realize
that
it's
a
JavaScript,
you
don't
actually
have
any
back-end
processes
capabilities.
A
B
B
You
could
get
a
token
and
be
sure
that
no
other
element
on
the
page
will
access
that,
because
you
are
inside
an
iframe
right,
so
you
would
be
able
to
do
it
more
easily
than
for
example,
if
you
had
a
script
that
runs
as
a
part
of
the
page,
because
at
that
point
every
other
element
on
the
page
would
be
able
to
access
the
token
right.
So
it's
not
bad,
but
it
has
some
pros
to
it,
but
also
cons
right.
So
these
are
definitely
things
that
you
have
to
take
into
a
town.
B
A
I
mean
I
think
that's
quite
a
few
times
already,
but
but
obviously,
and
and
one
thing
made
it
a
con
that
one
and
maybe
somebody's
like
no,
no,
no
wait,
wait,
I'm,
actually
implementing
ship
and
hostile
aliens
to
the
store,
and
that
isn't
maybe
an
exception
with
the
rule.
So
if
you
actually
are
implementing
Adan's
which
are
coming
from
the
store,
then
maybe
in
certain
scenarios
you
could
store
something
in
the
added
weight
because
that's
the
model
for
the
ifvs
and
that
is
in
the
store.
A
And
but
if
you
think
about
this
from
an
enterprise
development
perspective,
that's
highly
limited,
it
could
be
problematic
and
the
story
isn't
really
quite
out
there.
For
the
time
being
now
inside
of
the
ship
and
engineering,
we
are
actually
going
to
do
investments
on
the
atom
model.
So
we
are
looking
into
improving
the
adding
models,
let's
say
and
pain,
points
or
fixing
those
pain
points
or
some
of
the
pain
points
during
this
calendar
year.
A
A
If
it's
a
file
or
asset,
you
can
still
store
it
in
a
SharePoint.
But
if
it's
anything
else,
the
data
which
is
actually
list
in
a
list
format
or
relational
format,
you
can
actually
store
that
really
really
easily
in
the
provider
hosted
at
Einstein.
Rather
than
put
it
in
the
ad
in
web,
which
somebody
can
accidentally
delete
and
then
all
the
data
is
gone.
That's
that's
a
horrible
story.
From
that
perspective,
so
the
horrible
story
is
the
fact
that
somebody
can
actually
kill
the
Adhan
wave
or
understand
that.
A
Hopefully
did
that
did
kind
of
make
sense.
I
wandering
around
on
down
store
as
well
cool
moving
along
on
the
option.
So
what
about
the
alternative
option?
So
what
is
options
which
isn't?
Actually
that
often
explains
or
covers
within
the
books
or
in
the
in
the
internet?
There
are
some
material
on
this
one
as
well.
If
the
single
based
apps
/
s,
general
health,
adapts
and
in
this
context,
single
base
app
does
not
refer
to
shed
my
horse
to
edit.
A
This
refers
to
the
implementations
where
you
essentially
have,
for
example,
a
share
website
which
is
then
using
the
remote
AP
is
connected
to
sharepoint,
get
the
data
and
render
the
stuff
up,
and
in
these
cases
you
do
have
full
flexibility
on
choosing
your
own
technology
stack
and
because
you
can
actually
secure
alternative.
It
doesn't
have
to
be
moist
of
technology
and
you
can
still
secure
depth
access
using
Azure,
Active
Directory
security
settings.
A
You
have
also
full
flexibility
on
the
user
interface
on
a
downside
or
both
ways
that
you
need
to
implement
the
full
user
interface
by
yourself,
because
you
can
take
advantage
of
anything
in
SharePoint,
but
it
gives
you
whatever
you
want
to
do,
and
then
you
can
still
access
the
data
and
SharePoint
and
then
surface
and
aggregate
the
data
any
way
you
want
from
SharePoint
or
from
Microsoft
graph.
For
so
as
an
example,
the
external
hosted
apps.
A
In
this
case
they
can
be
scaled
independently
from
SharePoint
which,
by
the
way,
I'll
applies
also
for
provider,
hosted
at
ease.
But
it's
a
slightly
different
approach.
It
really
the
key
difference
is
way
to
grab
it.
Just
adapt
I'll
be
registering
that
the
your
Active
Directory
or
using
the
classic
ship
on
you
is.
You
can
secure
an
access
additional
endpoints
without
your
Active
Directory.
A
So
you
can
do
this
model
using
whatever
technologies,
what
you
want,
not
just
Microsoft
technologies,
and
then
you
do
have
that
similar
kind
of
a
security
isolation.
As
with
adding
model
the
details
of
that
security.
Isolation
is
slightly
different,
but
the
same
rules
apply.
You
are
giving
that
app
specific
permissions.
What
that
can
actually
do-
and
those
are
being
let's
say
in
quote
well.
This
is
absolutely
being
followed
when
you're
calling
back
on
the
SharePoint
and
obviously
on
the
disadvantages
side,
which
is
which
one
as
we
didn't
go
through
you.
A
You
are
fully
responsible
of
the
implementation.
It
cannot
actually
take
advantage
of
anything
in
SharePoint.
It's
not
a
single
piece
and
the
SharePoint
you
guys,
you
actually
need
to
take
care
of
the
whole
UI
implementation,
and
then
these
are
hosted
externally
from
SharePoint.
So
you
need
to
really
there's
this
implications
on
that
one
for
maintenance
and
operations
perspective,
so
that
has
to
be
taken
into
account
as
well.
B
So
I
have
actually
two
days
right,
so
I
should
only
suppose
that
those
are
actually
apps
that
can
run
on
your
phone.
Your
client
apps
web
apps,
basically,
everything
that
runs
anywhere.
So
that's
going
to
be
an
embedded
app
app
on
your
phone
single
page,
app
client
application,
whatever
it
is
right,
just
an
application
that
needs
to
connect
to
SharePoint,
Online,
sure
and
another
thing
that
I
wanted.
As
you
talked
about
it,
is
this
only
for
SharePoint
Online.
Or
could
you
use
the
same
approach
in
one
way
or
another
with
on-premises.
A
One
way
or
another
yes
for
on
premises
as
well.
Obviously
the
authentication
model
would
be
slightly
different
than
on-premises,
but
sure
we
could
have
a
asp.net
application
in
on-premises,
which
has
been
using
the
on
premises,
authentication
process
to
get
access
on
their
own
from
the
SharePoint
cool.
B
A
B
We
have
something
yeah,
yes
over
time,
I've
built
few
of
these
and
I
really
like
the
idea
approach
and
for
some
things.
It
makes
perfect
sense
that
I
own
own
DUI,
because
I
could
go
anywhere
I
wanted
around
it
and
I
wasn't
logged
down
to
using
particular
master
page
or
ad.
If
I
could
use
anything,
I
wanted
and
I've
built
quite
a
few
times
application
with
angular,
where
I
own
the
whole
UX,
and
it
would
scale
it
would
work
on
the
phone
it
would
be.
B
Responsive
I
could
do
anything
with
it
and
with
all
I
could
connect
to
a
ie
and
with
that
get
access
to
SharePoint
or
even
exchange,
email
and
calendar.
Anything
terms
right.
So
it
is
really
powerful
approach.
Whenever
you
have
the
requirement
that
you
have
to
build
application,
that
might
not
feel
like
a
part
of
the
portal.
If
you
will
sure.
A
Sure
absolutely
good
moving
on
on
the
option,
so
the
last
and
the
logical
option.
What
we're
going
to
talk
about,
obviously,
is
the
SharePoint
framework
and
right
now
on
the
SharePoint
web
framework
when
we're
recording
this
one.
We
are
in
release
candidate
studies
with
the
client-side
web
parts
and
there
will
be
other
components
in
SharePoint
framework
as
well
and
bring
the
calendar
year
of
2017,
but
let's
concentrate
on
what
does
it
mean
for
the
time
being
and
how
the
SharePoint
framework
is
essentially
working
right
now,
so
advantages
on
SharePoint
frameworks.
A
Well,
the
customizations
are
executed
in
the
context
of
SharePoint
page,
and
this
actually
gives
a
lot
of
flexibility
on
the
unscalable
on
rendering
on
infant
implementing
the
functionalities.
You're
not
actually
tied
into
the
you
might
say
an
iframe
like
with
the
adding
part,
there's
no
complex
permission
model
and
I
will
come
back
on
that
and
discussion
in
a
second,
because
there
is
no
or
off
model
with
the
SharePoint
framework
applications,
the
tenon
administrators.
They
need
to
still
approve.
A
So
somebody
needs
to
approve
that
adding
to
be
deployed
or
being
available
within
the
tenant
or
within
their
own
premises,
form
in
the
future,
but
there's
no
conflicts
permission
model
to
consider
from
adding
the
or
a
perspective
or
SharePoint
framework
a
perspective.
There
is
a
consistent
user
experience
across
the
this
one,
especially
if
you
use
the
components
and
controls
with
which
we
are
providing
from
Microsoft.
It's
always
up
to
you
how,
if
you're
going
to
do
that
or
not,
but
it
improves
your
development
productivity
enormously
cross-platform
cross-platform
development.
A
A
It
is
industry
standard
for
web
development
and
nowadays,
and
the
SharePoint
framework
has
native
support
cross
different
devices,
essentially
meaning
that
when
you
aren't
implementing
your
client-side
web
boards,
using
the
existing
effects,
which
we
are
providing
that
client-side
web
part
will
test
magically
by
itself
without
any
additional
gimmicks
line
and
resize
itself
to
any
device
where
it's
used.
Well,
obviously,
unless
you
do
fixed
wipe
tables
in
your
web
part,
which
would
be
foolish
but
anyway,
that's
a
different
discussion
on
a
disadvantaged
side
kind
of
a
mention
that
the
permission
model
already.
A
So
it
is
the
the
Shepherd
framework
application
client-side
web
parts
in
this
case
or
in
the
first
case
they
run
with
permissions
of
the
end
user
without
additional
permission
model,
and
this
is
really
the
reason
why
the
tenant
administrator
has
to
approve
the
app
to
get
and
deploy,
because
the
quite
the
JavaScript
which
is
executed
from
the
page
does
not
follow
any
old
model.
That
could
be
a
challenge
or
that
might
not
be
a
challenge,
but
it's
a
typical
model,
especially
with
even
with
adding
model.
A
If
you
have
embedded
JavaScript
on
the
slides
and
that's
been
a
really
really
classic
way
of
doing
that,
so
people
are
embedding
JavaScript
the
script,
editor
wit
board
or
user
custom
actions
or
J's
link.
So
exactly
the
same
experience
from
that
perspective
and
shape
and
framework
introduced
is
completely
new
development
model
for
sharepoint,
with
new
tools
and
ypur
issues,
and
this
no
doubt
is
one
of
the
sugars.
For
let's
say,
cutting
quotes
classic
shape
on
developers.
A
I
can
actually
do
this
other
development
as
well
or
at
least
you
have
this
cutting
point
to
do
that
as
well,
and
that's
a
really
key
advantage
and
from
a
process
perspective,
the
shape
one
framework
does
do,
does
no
doubt
require
new
guidance
and
policies
for
development
process.
So
you
need
to
think
through.
How
do
we
do
develop?
And
how
do
we
do
this
first
control?
How
do
we
do
well?
That's
would
be
aligned
on
the
existing
models
that
that's
not
that
different.
How
do
we
do
deployment?
A
B
So
the
one
interesting
thing
that
we
didn't
talk
about
yet
is
the
fact
that
SPF
X
is
only
the
UI
part.
Imagine
that
you
would
want
to
build
a
web
part
that
needs
to
do
some
additional
operations,
imagine
creating
a
site
or
maybe
creating
few
sites
and
playing
a
list.
It's
not
a
thing
that
you
would
want
to
do
in
browser,
because
if
someone
closes
the
tabs
moves
over
to
the
other
page,
that
process
would
stop.
B
So
you
have
to
have
some
other
place
or
an
API
or
application
or
process
that
is
able
to
do
that
independent
of
the
web
part
it
actually
lifts
client-side
on
the
page
right,
so
SPF
X
is
only
one
part
of
the
whole
solution
that
you
would
build
to
write.
You
will
probably
need
more
the
richer,
so
solution.
You
want
to
build
sure.
A
A
Or
this
multiple
options
and
then
from
your
JavaScript
you're,
just
poking
that
the
start
as
a
back-end
process,
absolutely
suitable
model
and
that's
a
really
good
point.
This
is
only
the
UI
part
of
the
story,
a
lot
of
stuff.
What
we,
for
example,
use
the
implement,
that's
an
ending
model
implementation
hosted
in
the
end.
Let's
say
our
share
web
sign
absolutely
still
valid.
We
need
that
stuff
because
then
we
might
have
implemented
a
whip
job
or
an
Asha
function
or
whatever
functionality
or
your
provider
hosted.
A
A
Will
be
additional
models
and
there
will
be
or
we
come
up
with
a
variations,
and
then
we
call
it
five
models
or
six
models
of
seven
model
doesn't
really
matter
and
all
of
these
actually
technically,
when
I
think
about
the
SharePoint
framework,
it
is
actually
something
which
you
could
have
been
able
to
do
already,
with
sandbox
solutions
or
actually
in
before
that
in
in
2007,
the
toasting,
the
JavaScript
and
in
the
JavaScript
you're
hitting
Web
Services
Network.
What
we're
doing
here
with
SharePoint
framework
as
an
example
with
modernizing
the
models
and
processes
and
implementation
options?
A
What
people
been
able
to
do
already
in
the
past
and
modernizing
that
and
aligning
that
with
the
industry
standard?
And
that's
a
really
really
really
the
key
point,
I
wouldn't
consider.
Well,
we
can
consider
the
SharePoint
framework
as
a
new
model,
but
actually
it's
an
evolution
of
the
approaches.
What
people
been
using
anyway,
plus
it's
actually
giving
us
a
lot
of
benefits
as
an
API
layer
as
well,
when
we
start
to
implementing
client-side
web
plans
good.
A
So,
like
mentioned
kind
of
a
four
different
models,
they
are
overlapping
between
each
other,
quite
often
or
mixing
them,
but
MIT's,
good
and
true
as
a
summary
on
the
on
one
page,
which
probably
helps
on
on
comparing
them
between
each
other.
So
we
have
the
double
SP
packages,
and
yet
those
are
mainly
form
solutions
or
sandbox
solutions.
The
supporting
clouds,
it's
debatable.
Yes,
you
can
actually
still
deploy
individual
assets
using
declarative,
sandbox
solutions
and
meaning
sandbox
solutions
which
only
have
xml
or
assets
in
them.
A
But
what
it
means
also
is
that
for
maisha
developer
perspective,
you
need
to
actually
have
a
deep
knowledge
on
a
ship
on
the
internals,
because
well
especially
in
the
central
solutionist
case,
and
you
need
to
consider
what
happens
if
you
need
to
update
something.
How
do
you
update
the
stuff
or
which
of
the
elements
you
actually
use
so
that
you're
not
actually
causing
yourself
challenges
in
the
future?
And
this
multiple
aspect
to
flexibility
marker
there?
It's
it's,
we
were.
We
were
actually
spending
quite
a
lot
of
time,
figuring
out
when
we
call
this.
A
Let's
call
it
flexibility
and
but
it
actually
refers
more
on
the.
What
we
can
do
with
this
particular
model
and
what's
the
future
roadmap
of
that
model,
as
well
and
with
ss3
packages,
the
we're
not
really
significantly
investing
on
them
anymore?
It
is
what
it
is,
it's
mainly
for
deploying
assets
on
SharePoint
and
obviously
in
a
farm
solution
case.
Yes,
that
might
be
service
life
code
as
well,
but
it's
we're
not
evolving
that
as
such
in
the
future
either.
A
Now
the
next
model
which
went
through
was
adding
models
which
the
key
point
was
decoupling,
customizations
from
step,
one.
That
was
really
the
key
challenge
which
we
were
actually
addressing
with
that
one
comparing
to
the
farm
solution
and
it
provided
the
security
model
for
the
customization
for
managing
customization
permissions.
A
Yes,
we
did
have
a
kind
of
a
webpart
experience,
but
that
was
the
adding
port
which
was
limited,
so
it
wasn't
really
optimal
and
additional
operational
maintenance
required,
because
if
you
do
adding
model
in
the
in
a
real
way
in
the
enterprise
scale,
you
are
falling
back
on
the
provider
hosted
adding
model,
and
that's
where
you
need
to
think
through.
Where
are
you
hosting
their
stuff?
A
Flexibility
is
fear,
and
the
future
roadmap
is
that
we're
investing
heavily
at
well
I,
wouldn't
say
significantly
heavily
massively,
but
we're
investing
on
that
level
as
well.
We're
trying
to
address
the
key
pain
points
with
that
one
as
well,
because
it
is
absolutely
an
option
from
a
security
isolation
perspective
as
an
example.
The
third
option,
with
revenge-
reverse
external
app
single
beta
applications,
hosted
outside
of
the
SharePoint,
and
that
is
actually
decoupling.
The
customization
from
SharePoint
as
well.
A
Yes
in
that
model,
you
can
use
alternative
technologies
as
well,
but
it's
much
more
difficult
than
with
the
external
apps
and
a
single
based
applications
registered
using
Azure
ad,
mainly
because,
as
your
ad
guys
are
actually
helping
these
other
technologies
to
use
that
model
as
well,
and
it
has
its
security
model
and
it
requires
a
custom
implementation
of
user
interface,
which
is
a
one
consideration,
because
the
stuff
is
actually
stood
outside
of
the
sharepoint.
So
I
need
to
implement
the
additional
stuff
as
well
support
it
in
office.
A
I'm
going
to
use
script,
editor,
wave
board,
I'm,
going
to
use
user
custom
actions
or
and
very
much
JavaScript,
and
that's
really
the
what
we
saw
from
Microsoft
perspective,
and
now
the
SharePoint
framework
is
giving
us
more,
let's
say,
railed
way
of
implementing
exactly
those
scenarios
and
more
easy
way
to
implement
them
as
well,
a
more
standardized
way
to
implement
them
as
well.
It
runs
on
the
permissions
of
current
user
because
it's
JavaScript
running
into
permissions
of
the
of
the
process
and
but
one
of
the
key
challenge.
A
Our
key
advantages
is
that
this
is
actually
industry
standard
model.
We,
you
can
take
advantage
of
Conoco
to
react,
angular,
angular
2.
It
doesn't
matter
you're
using
the
the
open
source
tooling,
how
people
are
doing
customizations
outside
of
SharePoint
as
well.
Now
the
flexibility,
obviously
from
a
double
SP
is
limited
at
in
sphere
external
apps,
SBA's
cute,
so
slightly
improved
from
adding
model.
Maybe-
and
that's
because
of
the
the
additional
aid
surface
which
is
easily
available
and
then
which
share
point
frameworks.
A
One
thing,
maybe
dimension
on
the
on
the
slide
also
is
the
costing
back
shorten
a
long
time.
If
you
just
look,
the
SS
b
packet
is
three
dollars
and
then
the
SharePoint
framework,
one
dollar.
The
first
reaction
for
somebody
might
be
no
but
I
need
to
learn
so
much
new
stuff
with
SharePoint
framework.
Absolutely
that's
the
short-term
costs.
Now
the
problem
with
or
the
challenge.
Let
me
switch
the
Consulting
moment.
A
The
challenge
of
the
WSB
packages
is
really
the
long-term
impact
of
those
XML
and
long
term
impact
of
a
double
SP
packets
of
safe-side
as
a
template
or
model
people,
don't
quite
realize
the
impact.
Until
then
they
hit
doubt
those
problems
sooner
or
later,
shape
and
framework.
That's
a
future-proof,
proven
model,
a
short-term
cost.
Yes,
you
need
to
learn
new
stuff.
You
need
to
spend
some
time
on
learning
de,
but
in
a
long-term,
that's
highly
beneficial
model
and
that's
future
proof.
That's
the
model.
What
we
use
internally
in
in
SharePoint
engineering
as
well.
A
B
Re
I,
don't
think
you
left
any
room,
hasn't
one
one
that
I
want
you
to
keep
in
mind
that
whenever
we
say
that
one
approach
is
limited,
the
other
one
is
excellent.
We
take
into
account
a
number
of
things
like
which
stack.
Can
you
build
on?
Is
it
easy
to
scale?
Is
it
easy
to
host?
Is
it?
Can
you
build
it
only
in
c-sharp,
or
can
you
do
it
in
any
language
on
any
second
one?
How
easily
you
can
reach
out
to
order
things
like
the
Microsoft
draft
right?
B
So
we
take
a
number
of
things
into
account
and
try
to
come
up
with
a
total
score.
If
you
will,
which
approach
makes
sense
or
which
gives
you
the
most
options
trip
right
and,
as
you
said
often,
you
will
need
more
than
one
approach
combined
to
build
solution,
because
you
might
have
a
piece
that
is
exposed
in
UI
and
then
piece
that
runs
as
an
operation
in
the
the
background
processing
data
right
so
and
it
would
in
the
past
they
have
to
you.
You
only
had
one
model
to
do
it
of
your
piece.
B
Then
we
got
added.
So
we
had
two
approaches,
then
don't
go
three
at
with
external
apps,
and
now
we
actually
have
more
tools
in
our
box
to
choose
from,
and
the
key
thing
is
I
guess
that
we
covered
that
on
the
next
slide,
right,
which
just
might
be
the
good
time
to
to
choose
to
move
to
which
is
all
of
these
approaches
are
still
available,
and
it's
okay
to
use
them.
B
The
most
important
part
is
that
you
do
not
look
at
which
approach
is
the
most
modern
or
the
hottest
one
or
about
which
approach
people
talk
the
most.
The
key
essential
things
for
you
to
understand
is
understand
what
you
are
trying
to
achieve
and
choose
the
model
that
will
support
you
with
that,
the
best,
including
what
your
team
can
do,
how
efficient
you
are
right,
because
it
will.
It
will
take
you
two
years
to
build
something
fancy
in
SPF
X.
B
A
Absolutely,
and,
and
also
the
fact
that
quite
often
you're
mixing
those
approaches
between
each
other
so
like
the
story
of
an
client-side
with
porridge
calling
deadness
secures
with
API,
which
is
actually
implemented
using,
let's
say,
adding
model
or
ACS
or
a
ad
so
for
connecting
back
as
an
apple
in
the
cold
Chevron's
online.
So
this
is
not
a
black-and-white.
Discussion,
obviously
analyse
your
requirements.
A
We
had
a
pretty
long
discussion,
no
live
demos,
but
I
think
you
guys
seen
and
guys
and
girls
have
seen
quite
enough
of
the
demos
with
SS
pay
packet
is
adding
model
and
single
based
applications
and
even
share
bond
framework
implementation
so
having
this
kind
of
a
open
discussion
on.
What's
the
what's
the
good
thing
and
what's
the
passing,
we
thought
that
it
would
be
highly
beneficial,
but
really
think
about
think
about
the
fact
that
these
things
are
not
black
and
white.
There's
no
one
single
best
practice
for
SharePoint
development
in
the
future.
A
You
need
to
consider
the
options
you
need
to
understand
and
select
the
right
one
with
securing
your
business
requirements.
That's
the
right
rule
to
follow
anything
else.
At
the
final
world.
Words,
public
vision,
earth,
peace
on
earth;
yes,
excellent!
Thank
you,
everybody
for
watching
and
listening
and
we'll
come
up
with
a
new
webcast.
You
know
later
bye,
bye.