►
Description
Recording of the SIG from November 15th. Latest SharePoint Development news from engineering and concentration on SharePoint 2019 dev platform.
Detailed agenda and covered topics are available from SharePoint Dev blog at http://aka.ms/spdev-blog.
Download recurrent invite from http://aka.ms/spdev-sig-call. More details on the SharePoint Dev community from http://aka.ms/sppnp.
A
It's
because
I
wanted
to
skip
the
standard,
slides
relatively
fast
and
and
that's
one
of
the
feedback.
We've
got
from
our
survey
as
well
now
opportunities
to
participate
with
the
within
the
community.
So
please,
please,
if
you're
interested
on
gaining
visibility
or
being
an
MVP
in
the
future.
These
are
great
opportunities
for
you
to
do
a
live
demo.
So
if
you
build
something
cool,
you
tested
something
cool.
You
have
a
technical
solution
or
architecture.
A
Now
you
want
to
demonstrate
that
for
the
rest
of
the
community,
this
are
create
opportunities
for
you
to
do
that
and
get
some
visibility
for
you
as
well,
and
even
though
it
wouldn't
be
interested
on
getting
to
the
MVP
status.
You
might
want
to
show
your
stuff
and
get
some
feedback
on
the
on
the
on
your
solution.
You
can
always
also
contribute
in
a
key
table.
Those
contributions
are
more
than
welcome.
We
have
a
pretty
large
open-source
github
sample
collection,
already,
I
think
we're
hitting
500
samples
pretty
soon.
A
A
So
please
keep
on
providing
feedback
having
in
discussions
and
providing
feedback
related
on
our
surveys
and
what's
missing,
and
especially
when,
when
they're
stuff
in
deaf
preview,
please
tell
let
us
know
using
the
issue
list
if
you
run
into
any
box
or
if
something
isn't
working.
Probably
it's
super
valuable
for
us
to
be
able
to
address
your
concerns
or
our
SEO
box
as
fast
as
possible,
and
obviously,
if
there's
any
critical
box
as
well.
A
Please
please
please
let
us
know
as
well
now
today,
I
have
few
slides
on
the
general
announcement
and
update
section
related
on
what
has
happened
within
the
last
week
kind
of
a
pinpointing
few
topics
from
there,
and
then
we
can't
concentrate
on
the
ship
on
2019
development
platform,
so
really
walkthrough
with
that.
There
are
some
known
issues
related
on
that.
So
we're
going
to
talk
about
those
today
as
well,
which
were
a
plant
to
get
fixed.
A
Obviously,
the
well
SharePoint
for
SharePoint
2019
rtems,
pretty
recently
shape
on
framework
1.7
when
it
was
released
pretty
recently
and
now
we're
finding
few
things
here
and
there
which
we
need
to
still
adjust
and
I
will
cover
all
of
those
true
today.
So
we
get
a
clear
clarification
where
we
are
with
this
platform
and
what
you
should
be
aware
of
now:
I'm
not
right
now,
I
we're
not
seeing
a
massive
uptake
on
SharePoint
2019
from
a
development
perspective,
yet
because
it
is
still
quite
a
new
platform.
A
So
it
was
released
only
a
few
weeks
ago,
but
we
can.
There
was
already
discussions.
For
example,
I
was
in
a
office
register
for
connect
conference
this
week
yesterday,
and
there
was
of
numerius
partners
who
already
were
planning
their
my
creation
activities
for
SharePoint
2019,
which
will
happen
then
early
next
year,
so
they're
already
growing
to
use
to
share
one
2019
and
they
need
to
understand.
What's
available
there.
A
A
We
are
significantly
falling
behind
of
this
issueless
tracking.
We
do
have
an
active
team
in
China
who's,
helping
us
on
the
labeling
this
between
engineering.
We
really
are
looking
into
investing
more
and
more
time
on
helping
you
with
the
issues
and
I'll
come
back
on
this.
One
I
want
to
talk
about
the
roadmap
on
the
on
the
SharePoint
development,
after
three
slides,
but
technically,
if
you
run
into
any
developer
or
extensibility
related
issues,
please
report
them
using
take
MSS
bit
of
issue.
A
This
is
issue
list
in
SSP,
dev
Docs,
and
this
is
really
for
you
to
tell,
for
example,
that
I
you're
hitting
in
a
standard
API
and
suddenly
the
API
surface
or
the
response
has
been
changed,
and
this
is
not
what
you
were
expecting
and
then
we
can
actually
loop
that
internally
to
the
right
people.
That's
super
super
important
for
us
to
know
what
has
happened
and
then
also
fixed
those
things.
A
If
your
whatever
issue
running
into
is
not
developer
oriented,
it's
not
it's
an
out
of
the
box
functionality,
one
out
of
the
box
webparts
seems
to
paper,
can
be.
We
really.
Please
use
the
standard
support
channels
in
the
tenant
admin
UI.
So
as
a
tenant
that
administrator
you
can
go
to
the
tenant
admin,
UI
and
open
a
support
ticket
and
based
on
the
priority
of
the
ticket.
It
will
be
then
routed
to
the
right
people,
the
non
developer,
oriented
issues.
A
Do
our
internal
agreement
within
the
ship
on
to
engineering
so
just
letting
setting
the
scenes
on
that
one
now
going
back
on
the
on
the
new
stuff,
so
not
just
repeating
the
old,
slides
and
under
interest,
but
shape
and
frame
reference
released
one
and
the
1.7
was
released
the
week
ago
on
Thursday,
so
pretty
much
few
hours
after
our
community
call
the
SharePoint
framework
community
call
and
I
got
some
comments
on
the
Twitter
on
that
one
because
in
the
community
call
I
said
well.
This
is
gonna
happen
in
a
matter
of
days
rather
than
weeks.
A
Obviously,
I
could
not
have
said
that
it
will
happen
in
a
matter
of
hours
because
we
would
kind
of
given
away
when
the
release
will
happen.
Now
we
wanted
to
release
the
SharePoint
framework
1.7
way
before
to
Thanksgiving,
so
there
will
be
a
time
for
us
to
fix
if
there's
any
findings
related
on
1.7,
which
we
need
address
as
fast
as
possible.
We
are
potentially
looking
into
releasing
1.71
still
prefer
during
this
calendar
year,
which
will
be
mainly
a
a
kind
of
a
bug
fixing
release.
A
So
it
will
not
actually
move
any
of
the
preview
capabilities
to
GA,
but
it
will
address
some
of
the
late
findings
or
the
findings
which
we
have
now
found
in
the
1.7.
So
that
would
be
1.71,
which
is
then
the
in
quotes
a
buck.
Vixen
release
potentially
still
and
during
this
year
and
I'll,
come
back
on
the
schedules
and
everything
else
after
that,
but
one
of
the
a
lot
of
the
stuff
what
which
the
1.7
was
one
of
the
biggest
releases
we've
been
having
in
SharePoint
framework
and
it's
related.
A
For
example,
ASD
and
Chicanos
commented
on
his
blog
post
as
well.
It's
a
big
release,
but
a
lot
of
the
stuff
is
in
previewing,
which
is
absolutely
correct,
and
we
want
to
bring
all
of
the
new
capabilities
first
to
preview
and
then
from
preview
data
GA.
So
we
can
reduce
the
potential
issues
in
production,
so
we
can
actually
ensure
that
whenever
recorded
the
GA
with
those
capabilities,
we
do
not
pray
q,
and
so
there
is
a
thinking
behind
of
this
that
why
they
go
to
the
Deaf
preview
and
obviously
really
the
big
thing
here.
A
Is
the
Microsoft
teams
teams
tap
development
alignment,
so
you
can
use
the
exact
same
code
base
as
a
SharePoint
framework
web
part
or
surfaced
exact
same
code
as
a
Microsoft
themes.
Tab
and
note-
maybe
on
that
one
just
to
clarify
that
if
you
are
more
into
user
driven
thinking
and
access
the
developer,
you
can
absolutely
surface
SharePoint
pages
as
such
already
as
a
Microsoft
team
stamps
or
you
can
a
surveys
individual
sites
as
a
max
of
team
stamp.
A
But
this
option,
which
open
framework
is
that
you're
actually
surfacing
the
LOB
or
line
of
business
or
your
custom
solution,
as
in
the
in
as
a
web
part
or
as
a
Microsoft
team
step.
So
either
way
you
can
serve
as
the
same
thing
in
multiple
locations,
and
the
thinking
behind
of
this
is
that
we
give
the
end
users
or
the
customers
the
option
to
decide
other
will.
A
They
want
to
use
the
Microsoft
teams
on
what
they
want
of
use
the
SharePoint
as
their
platform,
but
regardless
of
that,
you
as
a
developer
can
expose
the
same
capability
in
both
sites,
which
is
very
important
and
that's
definitely
the
most
important
one
here
into
dynamic
data
and
GA.
So
that's
not
general
availability
general
generally
available
for
custom
web
parts,
so
you
will
see
also
the
first
party
web
parts
most
likely
by
end
of
this
year.
A
Still,
even
though
there's
holiday
season
starting
pretty
soon
in
u.s.,
you
will
see
some
of
the
first
body
wet
parts,
exposing
data.
So,
like
a
list
view
web
part
will
start
exposing.
This
item
has
been
selected
and
then
your
custom
web
part
can
select
or
connect
itself
to
that
selection
in
the
list
view
web
part
or
library
a
great
part.
So
all
of
that
is
coming
still
by
end
of
this
year.
Cute.
A
Now
one
of
the
things
which
we
actually
talked
about
on
a
Tuesday
school
as
well
well,
I,
wasn't
on
a
Tuesday
called
because
I
was
in
Amsterdam
in
the
office
resist
fire
conference.
But
the
one
of
the
question
was:
we
wanted
to
have
some
feedback.
We
actually
got
a
58
submissions
or
replies
already
on
this
one
I
haven't
really
collected
the
full
set
of
feedback
is
the
question
around.
Do
we
have
too
many
calls?
Should
we
reduce
the
amount
of
activities
and
the
community
costs
in
the
SharePoint
development,
or
should
we
keep
on
using
them?
A
Because,
for
example,
this
week
we
have
two
calls.
So
typically,
we
have
every
single
week
to
Thursday
five
BFI
at
7
a.m.
PST
equal,
and
then
we
have
also
the
monthly
community
call,
which
is
meant
to
be
more,
let's
say,
collective.
What
has
happened
within
a
month
and
then
on.
These
calls
with
deep
dive
on
a
specific
topic
like
on
a
SharePoint
framework
or
open
source,
open
source
initiatives
which
were
running
under
the
SharePoint
engineering.
A
Now
your
feedback
is
welcome,
obviously
in
time
window
as
well,
but
I
would
actually
ask
you
to
go
to
take
a
MSSP,
dev
call
feedback
and
catch
your
votes
in
in
there
we're
collecting
it's
a
really
simple
question:
there's
like
two
questions
than
a
free
text,
form
very
able
to
then
write
your
opinion.
It
is
an
anonymous
survey.
So,
if
you
don't
like
somebody,
you
can
actually
be
pretty
rude
on
that
one
for
him
or
her.
A
It
doesn't
really
matter
if
you
want
to
have
write
something
something
some
messages
for
the
people
not
really
asked
you
to
do
that.
Obviously,
but
we
really
want
to
get
your
input
related
on.
Should
we
reduced
number
of
calls?
Do
you
have
any
alternative
ideas?
How
we
should
tackle
the
amount
of
information,
what
we
are
also
providing
in
the
and
and
technically
obviously,
we've
been
personally
I've
been
thinking
this
in
a
way
that
we
have
multiple
different
calls.
We
have
multiple
videos.
A
We
have
multiple
different
ways
of
communicating
because
there's
multiple
different
ways
of
consuming
all
of
this
information.
What
we're
sending
and
reality
is
that
there's
no
way
for
any
community
or
community
person
really
to
stay
up
to
date
on
all
of
the
materials.
What
we
are
shipping
and
we're
not
really
expecting
everybody
to
be
up
to
date.
A
What
and
that's
one
of
the
reasons
why
we
repeat
repeat
repeat
on
a
lot
of
these
messages
so
that
if
you
catch
one
of
those
messages,
one
time
you're
able
to
then
actually
understand
where
we're
heading
and
why
we're
heading
so
don't
wear
but
anyway.
So
please
answer
the
survey,
so
we
get
your
input
on
on
the
course
and
we'll
probably
come
up
with
a
is
like
the
larger
Community
Survey
at
some
point
to
understand
what
would
be
your
thinking
where
we
should
be
driving
and
hitting
with
this
community
I
use.
A
These
numbers
are
growing
insanely
fast.
The
community
is
growing
insanely
fast
again
at
some
points.
Sharepoint
development
wasn't
cool,
it's
clearly
cool
again,
because
you
can
actually
use
the
same
tools
to
also
did
do
development
for
Microsoft
teams
in
the
future
and
for
other
applications,
but
that's
it
for
that
one.
So,
let's
actually
move
on
on
the
slides.
Now
shape
on
the
roadmap,
so
1.7
came
out
last
Thursday.
What
was
released
on
8th
of
November?
A
It
was
a
dinner
I
think
it
was
yes,
it
was
8th
of
November
last
Thursday
and
that
had
a
native
support
for
SharePoint,
2019
internet',
a
dynamic
data
GA
and
then
numerius
preview
capabilities
like
alignment
with
Microsoft
Microsoft
team
experience
is
now
the
next
steps.
What
we
are
concentrating
we're
not
actually
pinpointing
or
calling
out
exact
capabilities
into
lists,
except
what
what's
now
in
the
dev
preview,
but
we're
really
looking
into
sa
a
the
whole
engineering
by
looking
into
stabilization
and
performance,
optimization
throughout
the
api's
and
the
UI
layer.
A
So
we
do
know
that
there
has
been
some
scalability
issues.
There
has
been
some
performance
issues
related
on
the
API
surface
and
we're
really
looking
into
optimizing
that
stuff.
There
are
certain
areas
in
the
SharePoint
see
some
API
or
REST
API
surface.
We,
where
you
can
as
an
example,
you
can
achieve
the
same
end,
result
using
multiple
ways
and
if
you,
if
you
used
one
of
those
ways,
it
might
actually
cause
a
significant
sequel
server
impact.
A
So
performance,
optimization,
big
things,
double
ization,
big
things.
Obviously
big
thing
for
SharePoint
framework
and
SharePoint
platform
perspective
is
also
carrying
the
SPF
X
and
def
preview
capabilities
shipped
and
then
there
is
a
continuous,
continuous
flow
of
additional
capabilities
coming
in
soul.
Ok,
let's
say
make
a
menu,
and
how
do
we
then
adjust
that
make
a
menu
from
an
API
perspective
or
additional
UI
settings
like
to
footer
settings
as
the
static
out
of
the
box,
footer
settings
or
the
header
settings
which
we
demonstrated
in
8/9?
A
So
just
a
lot
of
small,
pretty
significant
features
coming
up
from
a
UI
and
branding
and
all
of
that
perspective
as
well,
which
we,
which
we
will
be
then
releasing
gradually.
Now
we
haven't
set
a
date
yet
for
the
1.8
release
of
SharePoint
framework.
So
we
don't
yet
disclose
any
exit
dates
on
that,
but
you
might
expect.
So
let
me
explain
this
in
a
in
a
understandable
way,
so
we
just
released.
A
It
was
November
8th,
we
release
in
a
1.7
and
we
wanted
to
release
that
release
way
before
Thanksgiving,
so
we
actually
get
it
out
and
potentially
release
a
a
hotfix
or
1.71
before
the
holiday
season
start
we're
not
looking
into
releasing
any
actual
larger
capabilities
during
the
holiday
season.
So
you
can
expect
us
not
to
release
anything
during
December
and
only
after
the
well
next
year,
early
January,
mid
January,
maybe
potentially
early
February.
You
can
expect
this
following
version,
then
larger
version
coming
out
which
would
be
Tennessee
open
framework.
A
One
point,
eight
as
an
example
which
will
then
chie
some
of
the
functionalities
as
well.
The
same
actually
applies
for
site
designs
and
a
lot
of
the
branding
capabilities
and
a
lot
of
nice
stuff.
So
during
the
December
timeframe,
you
can
expect
not
us
not
to
release
anything
really
significant,
because
we
don't
want
to
break
anything
and
the
reason
for
that
one
is
is
quite
simply.
It's
the
same
that
why
you
should
never
ever
ship
anything
in
the
production
on
Friday
5
p.m.
and
why
is
that?
A
Because
if
you
do
that,
it's
Murphy's
Law
that
something
is
gonna
fail
and
it'll
lose
your
weekend
or
it's
gonna
be
a
long,
lasting
Friday.
So
we're
not.
We
don't
want
to
compromise
people's
vacation
and
holidays
ation,
and
we
also
want
to
make
sure
that
you
don't
have
to
actually
push
well,
obviously
more
selfish
reasons,
but
it's
good
for
you
as
well,
so
there
won't
be
too
many
new
stuff
coming
on
the
holiday
season,
so
you
can
concentrate
on
the
family
as
well
now
and
in
general
to
be
fair.
A
The
SharePoint
framework,
one
point
and
the
reason
why
we
want
to
actually
concentrate
also
on
the
stabilization
and
optimization
is
that
we're
kind
of
a
I
wouldn't
say
that
we're
ready,
definitely
not
ready.
We
will
add
capabilities
based
on
your
feedback.
We
will
add
new
office
365
services,
which
you
can
customize
your
SharePoint
framework,
so
we're
not
really
ready,
but
we
are
starting
to
be
in
a
good
position
with
SharePoint
framework,
so
you
can
actually
already
do
cool
customizations.
We
certainly
need
to
have
new
placeholders.
A
So
there's
multiple
set
of
functionalities
which
we've
been
releasing
during
the
past
year,
which
are
fulfilling
the
requirements
what
customers
have
been
having
so
the
craft
access
the
custom,
API
access,
the
tenon
wide
deployment
of
extensions
and
all
of
those
things
are-
are
really
really
valuable
and
they're
fulfilling
that
basic
set
of
scenarios,
which
is
great
to
see
as
we're
getting
to
done
just
a
level
already
now
Thank
You
Nigel
for
the
less
code.
Let's
go
to
comment
so,
let's
actually
move
into
the
ship
1:28
2019
development,
oh
and
there's
a
nice
type
out.
A
That
said,
that
was
me
right
in
that
slide,
and
that
was
the
last
slide
which
I
wrote
just
before
this
call
on
this
presentation.
Now
what
I
wanted
to
do
with
this?
One
is
because
the
2019
was
released
so
chirpin
2019
RTM,
pretty
recently,
you
can
already
get
it.
You
can
download
it.
You
can
use
the
Microsoft,
MST
and
keys,
or
your
company
keys
to
actually
didn't
get
the
license
and
an
install
to
your
environments,
but
I
wanted
to
explain,
what's
actually
included
in
the
SharePoint
2019.
A
We
cover
all
of
the
different
development
options.
What
we
have
in
2019,
so
certainly
farm
solutions
are
100%
still
supporting
in
SharePoint
2019
and
we're
not
taking
any
any
functionalities
away
from
the
farm
solutions.
Sure
some
api's
might
be
changed
and
welcome
back
on
the
documentation
slightly
later
on
this
presentation,
but
it's
100%
supported
in
SharePoint
2019
we're
not
planning
to
take
from
solution
support
away.
A
So
if
you
have
any
existing
solutions,
any
existing
SharePoint
funds,
you
can
update
those
to
use
SharePoint,
2019
relatively
easily
and
I'll
come
back
on
the
tooling
and
all
that
slightly
later
as
well.
Now,
the
only
thing
what
you
might
want
to
consider
here
is
that
the
the
modern
experience
is,
if
we
think
about
the
farm
solution.
Technically,
modern
experiences
do
support
form
solutions,
but
the
form
modern
experience
is
I'm,
not
really
aware
of
the
farm
solutions.
A
So
there
isn't
really
a
functionality
in
the
modern
tea
sites
for
modern
communication
science,
where
you
could
plug
in,
for
example,
a
custom
farm
solution
web
part.
Those
are
not
visible
in
the
modern
experiences.
If
it's
a
SharePoint
framework
report,
it
is
visible
or
if
you
would
pushing
a
custom
masturbates
to
a
modern
site.
Well,
it's
gonna
be
ignored
because
customers,
the
basis,
are
not
the
way
to
print
a
modern
theme
signs
in
the
in
SharePoint
Online
or
in
the
SharePoint
ad
2019.
A
Now,
and
that's
why
I
kind
of
put
the
modern
experiences
in
a
pocket
section,
because
it's
not
really
technically
farm
solution,
sure
the
modern
experience
is
it
doesn't,
mix
and
match.
Let's
put
it
this
way,
it
doesn't,
it
doesn't
break
anything,
but
it
doesn't
really
submit
Okita
now
the
second
option
and
sample
solutions.
So
in
SharePoint
Online
we
removed
the
code-behind
support
for
sample
solutions
a
few
years
back
or
one
and
a
half
years
back.
A
Our
good
friend
in
this
call
Patrick
Rodgers
had
a
peak
role
on
helping
all
of
the
customers
on
this
transition
and
it
was
relatively
painful
a
transition
and
we
do
still
apologize
on
the
on
the
missed
communication
potential
and
that
one
in
on-premises,
if
you
are
using
code
behind
sandbox
solutions,
which
would
be
slightly
a
surprise
actually
because
they're
not
that
widely
used
in
on-premises
and
those
are
still
actually
technically
supported,
so
you're
able
to
enable
that
service
and
you
are
able
to
use
them.
You
can
absolutely
use
declarative
sample
solutions.
A
The
third
thing
here
is
ship
on
talents
absolutely
still
104
cents,
opponent,
anything
what
you
had
built
on
for
SharePoint,
2013
or
SharePoint
2016
are
still
working
in
SharePoint
2019
platform
as
well.
So
no
changes
for
me
from
a
adding
model
perspective.
The
only
thing
here
which
I
added
as
a
question
mark
that's
actually
a
question
mark
for
myself,
because
I'm
not
100%
sure
if
the
addends,
if
we
cut
the
ad
in
support
for
modern
experiences
for
sharepoint
2019,
so
just
to
be
clear
on
that
one
in
in
sharepoint
online.
A
If
you
have
a
modern
experiences,
we
will
actually
expose
the
custom
add-ins
in
the
as
a
web
part
in
the
web
part
picker,
but
in
the
on-premises
I
can't
remember
which
version,
and
when
did
we
enable
that
in
SharePoint
Online,
so
I
need
to
come
back
on
that
one
and
where
we
find
that
and
we'll
update
the
documentation
in
the
docs.
Based
on
that
conclusion,
so
I'll
just
double
check
that
one
so
I
didn't
want
to
guess
the
situation.
A
And
then
the
the
final
person
I
need
to
compare
contras
triskin,
say
a
comment
there.
The
final
piece
there
is
to
SharePoint
framework,
which
is
then
meaning
that
the
customization
is
running
as
part
of
the
SharePoint
page.
So
it's
not
running
in
an
iframe
like
the
add-ins
are
running
in
an
iframe.
It
is
a
flexible
web
part.
An
extension
experience
are
able
to
embed
these
things
on
the
on
the
extent
on
the
modern
basis
as
well.
A
It
runs
under
the
permission
of
a
current
user,
so
any
of
the
Java
Script,
which
is
running
there,
is
running
based
on
the
permissions
of
the
user
and
it's
an
industry
standard
development
model,
which
is
true
it's
now.
Finally,
we
are
aligning
the
sharepoint
development
with
what
other
people
are
also
doing
and
not
just
having
our
own
sharepoint.
Specific
development
model
won't
be
heard
about
this
one,
probably
in
the
past
as
well.
Now
one
point
one
point
here
to
notice
the
sharepoint
framework
and
development
absolutely
supported
in
Chevron
2019.
A
Modern
experience
is
yes
for
webparts
and
extensions.
The
classic
experience
is
for
webparts,
so
you're
able
to
actually
build
SharePoint
framework
with
parts
and
they
do
work
on
the
classic
experience,
but
the
extensions
do
not
work
in
the
classic
experience.
So
that's
the
that's.
The
base,
which
is
kind
of
a
I,
wouldn't
say
debatable,
but
it's
partially
supported
now.
Chris
Ken
had
a
awesome
comment
actually
on
window
related
on
the
fact
that
100%
supported
does
not
mean
100%
recommended
and
that's
absolutely
correct,
so
to
be
fair
and
and
I
understand.
A
This
I've
been
working
with
SharePoint
for
so
many
years
and
everybody
is
always
looking.
What
is
the
Microsoft
official
recommendation?
Watch?
Which
of
these
I
should
be
using
Dobis
answer?
Is
that
well
technically,
it
depends.
It
depends
on
what
the
customer
is
asking.
What
is
meant
to
be
implemented
and
if
possible,
you
should
be
using
a
SharePoint
framework,
but
it
might
be
that
they're
asking
an
API
they're
asking
a
customization
or
hitting
an
API
which
is
not
exposed
in
on-premises.
A
So
let's
say
something
with
something:
something
which
isn't
exposed
using
a
REST
API
or
a
seasoned
API.
You
would
like
to
use
that
or
implement
stuff
using
SharePoint
framework,
but
it's
not
exposed.
Then
you
aren't
basically
restricted
to
implement
something
as
a
farm
solution.
In
those
kind
of
scenarios,
though,
I
don't
have
a
slide
on
this
one,
but
I'm
trying
to
explain
this
in
a
when
I
in
English
in
those
kind
of
scenarios.
What
I
would
personally
recommend
as
a
old
consultant,
hands-on
solve
this
in
the
atom
model
timeframe
as
well.
A
I
would
actually
implement
my
own
custom
wcm
as
sorry
w
CF,
no
SVC
so
service
with
a
P
is
how
would
I
put
it.
I
would
actually
implement
a
farm
solution
and
the
farm
solutions
only
purpose
is
to
expose
that
API
word
submission
and
then
I
would
actually
implement.
The
UI
is
still
based
on
SharePoint
framework
and
not
using
a
classic
webparts
just
because
of
that
one
API
limitation,
because
that
will
actually
give
me
the
opportunity
of
still
using
SharePoint
framework,
which
is
fluent
it's
it's
performance.
A
It's
super
flexible
and
it's
aligned
on
the
future
of
SharePoint
sure.
We
still
need
to
have
a
farm
solution
to
expose
that
API
surface.
But
how
often
would
you
change
that
phone
solution,
because
the
one
and
the
really
the
biggest
pain
point
with
farm
solutions
is
the
updates
where
they
don't
well,
they
do
work
properly.
A
If
you
know
how
the
farm
solution
should
be
upgraded
and
how
they
are
upgraded
and
what
you
can
do
with
them
so
having
a
farm
solution
with,
but
having
a
farm
solution
which
just
exposes
additional
API
using
SVC
or
accustomed
with
means
that
you
don't
actually
update
that
you're,
just
exposing
the
a
bare
surface,
but
your
customization,
which
is
running
as
a
SharePoint
framework
solution,
is
then
the
one
which
is
evolving
once
faster.
Then
the
final
solution.
This
way,
you
don't
have
to
schedule
service
breaks
for
the
farm.
A
That
often
you
don't
have
to
make
maintenance
breaks
for
the
farm,
which
would
be
the
case
if
you're
using
a
classic
form
solutions
now.
But
all
of
this
is
debatable,
so
it's
it's
really
there's
no
right
or
wrong,
and
so
you
shouldn't
really
be
like
hey.
We
should
do
this
because
Microsoft
says
and
that
you
have
to
do
always
this
and
that's
not
correct.
It
always
depends
on
the
requirements.
A
Now,
moving
on
are
things,
so
this
is
the
slide
which
we
showed
related
on
the
dev
preview
ownership
on
2019
def
review,
and
this
is
a
high-level
summary
on
how
to
get
started
with
SharePoint
2019
as
well.
So
I
updated
this
based
on
the
latest
changes.
So
you
can.
Oh
I
didn't
update
the
link,
download,
SharePoint,
2019
and
I
do
apologize.
That
link
is
still
pointing
to
a
wrong
location.
I,
don't
think
we
have.
Actually
let
me
do
this.
You
can
probably
say
my
edit.
A
Now
then,
you
need
to
enable
adding
model
to
be
able
to
to
be
able
to
to
be
able
to
use
SharePoint
framework
or
Adams,
and
that's
really
a
key
point,
and
this
you
need
to
have
the
app
service
application
enables
you
need
to
have
add,
subscription
settings,
service,
application
and
I'll
come
back
on
this
one
in
a
slides
in
a
second.
So
you
are
aware
what
it
actually
means,
and
so
there
is
a
powerful
commands
how
to
make
that
happen.
A
Now
that
somebody
is
asking
the
link
or
SharePoint
download
in
SharePoint
2019,
it
is
literate
here
we
go.
There
is
a
link
in
here
now,
all
of
the
by
the
way,
presentations
not
shared
in
the
we
release,
a
summary
and
recording
of
this
video
and
the
presentations
will
be
released
as
part
of
test
post
as
well,
and
that
blog
post
will
be
available
in
the
SharePoint
Deathlok
and
the
SharePoint
dethklok
URL
is
following,
so
you
can
actually
access
that
from
there.
A
So
you
can
then
download
the
PP
Dex
files
as
well
now-
and
this
is
a
really
important
thing
to
remember
so-
you
need
to
actually
also
enable
the
app
domain
in
the
phone
and
even
though
you
wouldn't
be
using
the
the
SharePoint
add-ins,
this
is
required
because
the
SharePoint
framework
actually
uses
the
had
in
infrastructure
to
get
the
functionalities
deployed
in
the
site
level.
So
if
you
do
not
enable
that
domain,
you
will
see
an
exception
also
that
in
upcoming
slides
as
well.
A
So
you
are
aware
of
that
and
then
you
obviously
install
the
basic
setup
of
SharePoint
framework.
So
you
install
the
no
js'
and
of
that
you
install
the
ship
one
framework,
1.7
version,
and
whenever
we
are
then
using
the
wits
or
asking
the
wits
version
environment,
we
actually
choose
to
2019
and
onwards,
and
then
your
solution
is
created
against
the
right
SharePoint
framework
versioning
if
you're
building
chef,
one
framework.
A
Obviously,
if
you're
implementing
this
was
studio,
I'll
come
back
on
that
one
if
you're
doing
farm
solutions
or
sample
solution,
I'll
come
back
on
that
one
in
a
second,
a
cute
point
from
Joe.
David
typically
has
a
summary
of
all
of
the
links
and
everything
else
in
two
minutes
after
this
call
in
Twitter
I,
don't
know
how
he
does
that,
but
it's
just
amazing
now
on
SharePoint
2019,
their
platform
just
to
be
100%,
sure.
A
There
are,
there
are
certain
things
which
are
not
supported
and
certain
things
are
which
are
supported.
So
let
me
explain:
I
didn't
create
a
slide
on
this
one,
explaining
how
to
whiten
with
this
or
limit
it
or
not.
But
the
reason
why
it
certain
things
are
not
supported
is
that
at
the
time
when
we
took
SharePoint
Online
code
paste
and
forked,
the
SharePoint
Online
codebase
and
created
sharepoint
20:19,
those
capabilities
person
were
not
released
yet
so
that
means
that
they
are
not
available
in
SharePoint
2019.
A
A
But
that
means
that,
for
example,
a
Christians
comment,
the
view
formatting
is
not
as
not
supported
in
SharePoint
2019,
because
it
wasn't
really
ready
and
released
at
that
point
now.
What's
what
supported
and
let's
actually
have
a
look
on
this
one?
So
the
modern
and
classic
data
store
I
want
to
be
clear
here
as
well.
So
this
is
not
just
about
modern
experiences.
All
of
the
classic
templates
site
template
site
definitions
are
still
there,
so
you
can
do
classic
pages.
You
can
do
modern
pages.
A
You
can
do
modern
sites,
which
means
modern
team
sites
or
a
modern
communication
sign.
The
modern
sub
sites
are
always
a
modern
team
sites.
So
just
a
bit
clearer
on
that
one.
There
is
no
modern
sub
communication
science.
What
would
it
be
communication
size
with
subside
so
technically,
and
there
is
a
so
you
can
create
a
new
site
collection
using
a
modern
team
site
which
doesn't
have
a
Kruk
associated
to
it.
A
So
it's
modern,
looking
themes
like
or
a
communication
sign,
and
then
you
can
create
a
sub
site,
which
is
always
a
modern
team
sign
so
or
any
other
classic
games
are
any
other
classic
side,
but
you
cannot
create
a
subject
communication
site
as
a
sub-site.
That
option
is
not
exposed
from
the
UI
now
SharePoint
framework
extensions
are
available,
SharePoint
framework
of
eight
parts
of
us
they
are
available
as
well.
Web
hooks
are
available
as
a
packaging
is
available.
A
This
is
a
huge
thing,
because
that
packaging
means
that
you
don't
need
to
worry
about
where
your
code
is
being
hosted
because
it's
being
hosted
automatically
from
that
catalog.
A
big
big,
big
thing,
because
it
basically
just
package
your
code
and
you're
good
to
go
with
the
customization
tenants
group
deployment
is
supported.
A
But,
let's
let
me
show
those
and
absolutely
the
UI
as
well
hub
sites
not
available
hub
sites
were
not
available
at
the
time
when
the
the
code
base
was
forked.
So
if
you
want
to
have
a
consistent,
similar
kind
of
a
hot
navigation
or
whatever,
you
would
have
to
implement
that
using
a
a
SharePoint
framework
extension.
Luckily,
the
extension
is
not
as
important.
Then
a
property
is
not
available.
Custom
warrant
themes
are
not
available.
This
is
a
pity.
A
So
what
it
means
is
that
the
modern
teams,
modern
teams,
are
available
for
modern
team
sites
and
communication
signs,
but
you
can't
modify
them.
You
cannot
add
a
custom,
modern
themes
for
the
modern
site,
and
that
is
a
nasty
limitation
which
I
absolutely
understand
and
we're
looking
into
potentially
enabling
that
at
some
point,
but
there's
no
promises
when
and
if
what
capabilities
will
be
further
released
on
SharePoint
2019
or
will
it
be
the
next
version
for
on
premises?
And
we
don't
know,
will
we
have
an
expiration
on
SharePoint
a
SharePoint
in
on
promises?
A
I,
don't
know
I'm,
not
I'm,
not
person
who's,
making
those
decision,
site
collection,
app
catalog,
also
is
not
available.
Technically,
the
capability
was
available
in
English
Airport
online,
but
the
site
collection,
our
catalog
in
the
code.
It
has
a
dependency
on
a
tenant
level
of
10
on
subscriptions
and
services
and
that's
not
available
in
on-premises.
So
we
were
unable
to
get
the
psychology
nav
catalog
to
work
in
on-premises,
now
disable
2019
SharePoint
framework.
A
The
third
party
version
is
one
point
for
point,
X
and,
and
the
reason
why
I'm
saying
one
point
for
point
X
is
that
it's
actually
a
combination
of
one
point.
Four
and
one
point
four
point
one,
but
you
don't
really
need
to
know
about
this
as
long
as
you
install
yourself,
a
SharePoint
framework,
one
point:
seven
and
it
chooses
your
target
to
be
a
SharePoint
2019.
It
will
create
you
a
solution
with
the
right
settings.
That's
basically
what
happens
behind
off
the
scenes
and
I
can
show
that
quickly
today
as
well.
A
Now
these
are
the
things.
What
we've
kind
of
quickly
went
through
and,
like
said,
slice
will
be
sure
tomorrow
after
the
window
o'clock
post,
go
lives
and
into
a
of
SharePoint
if
a
platform,
so
you
can
actually
copy
these
things
as
well.
When
you
set
up
your
initial
SharePoint,
we
know
19
employment,
you,
if
you're
a
developer-
and
you
don't
really
worry
about
these
things
and
all
Spencer
Harper
or
something
wouldn't
like
me
to
say
this,
but
as
an
example
personally
I
wanted
to
concentrate
on
this
form,
just
get
it
up
and
running.
A
But
after
that
you
still
need
to
enable
the
site
subscription
settings
service
that
is
not
created
by
default,
and
this
is
required
for
the
adding
infrastructure,
because
the
adding
infrastructure
again
is
required
for
SharePoint
framework
to
work.
So
we
need
to
first
create
an
app
catalog.
Then
we
need
to
create
the
subscription
setting
service
and
in
the
form,
and
then
we
need
to
go
and
set
the
app
URL
either
using
PowerShell
or
using
the
UI
and
I
just
added
that
as
an
image
under
on
the
slide
as
well.
A
So
if
you're
running
into
this
hey
my
solution,
my
I
can't
install
my
SharePoint
framework
solution,
double
check
that
you
have
the
subscription
setting
service
application
created
and
you
have
the
app
URL
enabled
in
the
forum.
So
after
that
this
thing
will
start
working
and
it's.
How
would
I
put
it?
A
It's
a
nasty
limitation,
because
SharePoint
framework
solutions
has
nothing
to
do
with
app
URLs,
but
the
code
in
inside
of
the
SharePoint
2019
and
the
server-side
code
is
basically
checking
that
and
it
is
not
allowing
you
to
deploy
anything
on
the
site
unless
the
app
URL
has
been
set
and
sure
we
should
have
fixed
that
what
we
didn't
and
that's
now
in
our
time.
So
it's
something
to
know
when
you're
setting
up
the
diff'ent,
the
other
things.
A
What
I
wanted
to
actually
cover
in
here
to
see
some
shape
on
2019
look
at
see
some
see
some
API
is
out
it's.
It
is
a
evolved,
client-side
object,
model
from
ship
and
2016.
It's
basically
the
same
season
as
it
was
for
SharePoint
Online
in
January
this
year,
except
to
ten
month
level.
Settings
again
because
tenant
level
operations
are
for
tenants
and
we
don't
have
a
tenant
object
in
the
on-premises.
We
have
a
form
object
and
let's
go
ahead
and
it's
slightly
different.
A
There
is
a
look
at
package
which
is
available
named
Microsoft
SharePoint
2019
season.
It
is
a
version
16
one
zero,
ten
thousand
ten
thousand
three
hundred
and
thirty
seven.
If
you
did
this,
did
test
anything
using
the
dev
preview.
This
might
be
slightly
confusing
because
the
RTM
version
is
actually
lower
than
the
def
preview
version.
That
was
a
decision
which
somebody
took
in
redmond.
A
I
don't
know
why
and
quite
understand
what,
and
but
it
is
a
slightly
lower
version,
but
that's
why
you
can
actually
see
only
one
version
right
now
available
from
nougat
for
this
one.
Now
there
is
a
known
issue
related
on
this
101.
First,
we're
not
planning
to
release
a
chevron,
2019
client-side
SDK
as
an
MSI.
A
The
problem
with
them
aside
that
the
MSI
setting
is
that
that
instance,
those
are
simplest
in
the
global
assembly
CAC,
and
you
should
never
ever
do
that,
because
those
Probot
are
simply
kak
sm,
please
overwrite
the
local
assemblies
which
you
might
actually
use
from
a
nougat
package
and
that's
not
the
right
way
how
you
should
be
doing
development.
So
that's
the
reason
why
we
don't
really
is
an
msi
with
this
one.
Now
there
is
a
known
issue
related
on
this
one
on
the
no
CAD
package.
A
Oh
there's
a
good
question
related
from
kamal
on
a
sharepoint
designer
for
chevron.
2019
answer
is
no
we're
not
looking
into
releasing
sharepoint
a
designer
for
chevron.
29
did
technically
the
sharepoint
designer
2013
should
still
work
for
sharepoint
20:19
as
well,
but
not
against
the
modern
sites,
so
those
are
plucked
from
SharePoint
designer
and
the
sharepoint
designer
isn't
really
a
future
proven
way
of
customizing
chevron.
So
it
is
somebody
wrote
a
SharePoint
is
a
destroyer
in
the
window
and
that's
that's
technically
what
could
happen
with
the
sharepoint
designers
as
well
now
PMPA
components?
A
This
question
is
coming
up
quite
often,
what
is
the
BMP
and
component
support
for
Sherman
2019
right
now?
We
do
not
have
a
PMP,
PowerShell
or
PM
pcs
encore
for
SharePoint
2019,
we're
looking
into
working
on
that
one
during
the
holiday
season,
so
we're.
Finally,
getting
that
one
up
and
running
the
team
has
been
forced
to
prioritize
prioritized
some
other
things
as
well,
and
this
is
surprisingly
time
consuming
thing
to
rethink
all
of
our
build
processes
to
get
the
shipment
when
a
19
included.
So
this
is
estimated
roughly.
A
First,
the
season
no
get
buckets
for
SharePoint
2019,
and
then,
after
that,
we
can
start
working
on
this
one
now
Visual
Studio
2017
support
is
to
that
2017
tooling,
to
new
version
off
to
Visual
Studio
17
business
to
do
2017,
which
was
released
on
Monday
or
Tuesday,
is
supporting
SharePoint
2019.
So
already
at
this
point,
which
is
great-
we
actually
fix
this
in
a
matter
of
weeks,
we're
already
supporting
SharePoint
2019.
A
So
if
you
have
a
farm
solution
build
for
SharePoint
2016,
you
want
to
test
how
to
migrate
that
or
create
that
to
the
SharePoint
2019.
We
are
supporting
that
in
a
Visual
Studio
sign
or
if
you
want
to
create
for
a
clean
form,
solutions
for
SharePoint
2019.
You
can
already
do
that
with
the
latest
version
of
Visual
Studio
2017
tool.
I
do
not
think
we
will
be
releasing
it.
This
operate
for
Visual
Studio
2015,
unless
I'm
completely
mistaken,
but
it's
already
2018,
so
it's
kind
of
understandable
as
well.
A
A
Could
a
shape
on
framework
support?
We
talked
about
this
one
already
Chevonne
2019
sports
as
part
of
its
chip,
1
2019
support
as
part
of
SharePoint
framework
1.7,
so
you
can
install
21.7.
After
that
you
will
get
an
environmental
selection
and
there
you
can
then
choose
to
share
1
2019
as
the
platform,
and
then
that
will
provision
you
the
right,
looking
solution.
Now,
however,
we
found
a
new
bunker
earlier
today,
based
on
our
our
testing
team,
found
out,
unfortunately
way
too
late.
A
This
mark,
because
1.7
came
out
week
ago
within
the
SharePoint
2019
or
Cher
119
few
weeks
ago.
So
if
you
are
selecting
a
react,
as
your
Chava
Script
framework
option
in
the
yeoman
template,
it
actually
provisions
you
a
solution
with
referencing
react
16,
and
that
does
not
work
in
on
in
SharePoint
2019,
and
this
is
a
limitation
or
a
it's
a
clear
buck
which
we
will
be
fixing,
and
this
is
one
of
the
reasons
why
there
will
be
SharePoint
framework
1.7.1,
most
likely
by
end
of
this
year,
hopefully
relatively
soon.
A
So
we
can
get
this
one
fixed.
Technically.
What
it
means
is
that,
if
you're
looking
into
doing
react
based
components
for
SharePoint
2019
right
now,
what
you
should
be
doing
is
the
provision
or
scuffled
your
project
with
which,
by
choosing
and
the
no
JavaScript
framework
and
then
reference,
those
rights
react
15
components
inside
of
the
solution
afterwards,
so
to
default.
A
Scaffolding
is
doing
this
stuff
stuff
in
a
wrong
way,
but
you
can
figure
can
fix
that
by
not
using
the
different
scaffolding
rather
manually
built
the
whole
thing
good,
that's
it
prune
are
killing
on
the
on
the
finally
on
the
on
the
quickie
ml
part
next
day
for
the
shipment
2019
development.
Well,
the
tooling
is
pretty
much
there
we're
looking
into
fixing
the
the
box,
which
we
know
which
are
unfortunate,
but
unfortunately
we
are
human
being
as
well
so
mistakes
do
happen
and
we
then
we're
looking
into
fixing
or
improving
our
documentation.
A
This
really
requires
your
input
as
well,
so
we
need
to
understand
how
much
documentation
is
actually
required.
What
is
the
demand
for
the
documentation
but
bare
minimum
we're
looking
into
doing
a
proper
API
documentation
refresh
so
we're
looking
into
having
a
season?
Maybe
I
document
that
for
SharePoint
2019
and
also
the
server-side
API
documented
for
shipment
2019
and
obviously
the
information
which
are
seeing
in
this
slide
deck,
which
we
went
through
today,
will
be
transformed
to
the
documentation
side
of
SharePoint
Docs.
A
So
you
can
clearly
go
back
on
the
official
Docs
and
see
what
was
the
website
supported
or
not.
Then
we
clearly
explained
that
it's
not
supporting
as
an
example
but
really
and
the
other
documentation,
which
is
the
the
kind
of
conceptual
documentation
what
you
can
do
with
Chevonne
2019.
This
is
where
we
need
your
input.
What
kind
of
documentation
is
needed
and
we
need
to
understand
to
demand
on
that,
because
we
don't
want
to
invest
our
documentation,
resources
for
doing
stuff,
which
is
not
actually
important
for
the
for
the
community.
A
So
we
need
to
prioritize
people's
time
here
as
well.
Now,
let's
quickly
do
a
demo
here,
a
lot
of
slides
I
do
apologize
on
that,
but
I
wanted
to
actually
walk
through
the
whole
stack
and
make
sure
that
we
touch
all
of
the
different
components
and
all
of
the
different
elements,
and
let
me
actually
share
my
screen
and
we
can
quickly
have
a
look
on.
How
does
the
SharePoint
look
like?
We
will
have
a
look
on
the
on
the
site.
A
A
Louis,
correct
Chris
got
it
I
got
it
excellent.
So
so,
let's
start
with
a
a
centralized.
Obviously
Center
I
mean
not
a
really
a
development
functionality,
but
it
is
the
way
how
we
control
the
form
and,
if
you're,
an
architect
and
you're
setting
up
or
a
team
lead,
you
probably
need
to
understand
the
basics,
but
like
I
mentioned,
and
just
quickly
referencing
this.
So
what
I've
done
here
is
that
I,
after
the
initial
execution
of
the
configuration,
wizard
I've,
actually
changed
or
instant
a
subscription
setting
service
and
I
missed
an
in
apparently
there
as
well.
A
You
also
need
to
have
that
management
service,
but
this
is
created
by
the
configuration
wizard
if
you
just
run
to
basically
sort
and
let
that
create
all
of
the
service
applications
for
you,
and
if
this
would
be
an
IT
protocol,
most
likely
some
people
would
be
jumping
in
my
window
and
say
you
should
never
use
the
configuration
of
this
work.
But
if
we
concentrate
on
the
developer
platform,
I
think
it's
fair.
We
save
some
time.
A
The
second
thing
I
like
mentioned
Thank
You,
Todd,
oh
client,
in
the
car
and
second
thing
animation-
is
that
you
need
to
absolutely
have
an
avocado
created.
So
when
we
create
and
the
app
catalog
from
Central
Admin,
it
gives
you
the
the
create
a
site
collection
and
basically,
we
have
to
have
that
app
catalog
available.
So
we're
able
to
upload
in
our
solutions
in
this
app
catalog
catalog
available
and
maybe
a
few
things.
A
One
note
one
thing
to
notice
here:
what
I
did
just
a
quick
tip,
so
IRA
I
modified
the
view
and
added
the
Skip
feature
deployment
column
here,
and
this
means
that
is
the
solution,
form
scope,
sorry
tenon,
scoped
deployed
solution
or
not
in
this
case
no,
and
that
means
that
this
solution
has
to
be
manually
installed
on
a
site.
Also
key
point
when
you're
uploading.
Anything
here
is
that
your
app
packets
error
messages,
it
says
no
ik
errors,
so
you
know
that
it's
actually
available
to
be
used
good
and
then,
let's
get
back
on.
A
Where
was
where
is
it
here?
We
go
and
the
final
thing
is
and
like
I
said,
this
is
a
slightly
nasty,
but
you
need
to
have
an
app
domain
available
here.
Otherwise
you
can't
activate
even
SPF
X
evolutions
available
in
the
site
level.
After
all
of
this
is
actually
done,
we
can
then
go.
For
example.
Let's
go
one.
Actually,
let's,
let's
do
this,
let's
create
a
new
site.
So
if
I
go,
we
have
a
SharePoint
home,
so
we
can
see
that
we
have
an
app
launcher
in
the
same
way
as
we
have
in
SharePoint
Online.
A
You
can
go
to
the
SharePoint
home
and
we'll
see
a
cool
SharePoint
home
functionality
here,
I'm
going
to
skip
that
one,
and
we
can
actually
say
that
we
have
a
modern
site
creation
experience
like
in
the
shipment
online.
They
made
a
follow-up
questions
at
this
point
we'll
be
raising.
You
will
be
raising
your
hand,
most
likely
saying.
Excuse
me,
can
I
add
additional
site
types
here,
and
the
answer
is,
unfortunately,
no.
A
You
can't
change
this
experience,
so
the
options
are
mainly
basically
disable
this
functionality
or
then
show
a
completely
custom,
UI
or
but
you
don't
have
an
option
right
now
than
that
and
third
option
as
a
side
time
now
in
here,
if
I
choose
a
communication,
sign
I
will
get
a
same
basic
set
of
designs
and,
like
we
noticed
site
designs
and
slide
scripts
are
not
supported
in
shipment
on
2019.
So
you
can't
actually
control
what
happens
so
you
can
modify
the
site
creation
flow
from
that
perspective.
A
If
we
call
this
seek
and
let's
actually
create
this
of
a
creating
communication
site
slide.
Creation,
though,
is
still
fast
because
in
the
same
way
as
with
on
prior
SharePoint
Online,
this
is
super
fast.
It's
based
on
the
new
implementation.
It
is
not
necessarily
as
fast
and
SharePoint
Online,
because
this
is
again.
This
is
at
the
end,
which
is
running
in
Maya
sure.
What,
in
a
matter
of
seconds
one
two
three
four
come
on,
we
should
have
the
communication
site.
A
They're
available
really
depends
where
my
time
jobs
and
the
study
session
of
them
is
they're,
a
native
see
some
see
some
way
to
create
these
sites.
Answer
is
yes,
so
good
point,
so
we
can
actually
create
communication
sites
and
modern
team
sites.
They
are
just
like
normal
site
design
definitions.
So
as
long
as
you
create
them
using
the
right
type,
that's
a
good
thing
for
us
to
actually
document
so.
A
To
our
dogs,
how
to
create
those-
and
now
we
have
a
communication
site
available
and
here
can
I
there's
a
good
question.
Let
me
actually
show
that
one
as
well,
so
we
obviously
the
list
and
libraries
you
can
use
the
modern
experience
or
you
can
use
the
classic
experience.
Let's
create
here
a
list
and
we're
gonna
create
that
that
is
by
default
in
the
modern
experience,
but
we
can
always
fall
back
on
the
classic
experience
in
the
same
way
as
with
SharePoint
Online.
There
is
the
button
or
a
link
in
the
left
navigation
again.
A
This
is
technically
a
fork
from
SharePoint
Online
from
January
this
year
or
so,
and
so
and
so,
and
so
so
it
means
that
the
same
functionality
is
what
we're
when
the
sharepoint
online
earlier
would
be
now
available
within
the
on-premises
in
here.
The
question
was
related
on
power.
Apps.
The
answer
is
no.
The
power
apps
modification
and
overrides
is
not
available,
and
that's
actually
understandable,
because
the
power
apps
is
a
sharepoint
online
capability.
It's
an
online
capability.
A
It
is
not
a
service
which
would
be
available
in
the
end
on-premises
environment,
so
it
can't
override
the
setting
thought.
The
frog
date
is
not
public
knowledge,
so
I
can't
give
you
the
exact
date
on
that
one.
So,
but
it's
it
somewhere
around
early
this
year,
it's
the
fourth
day.
Unfortunately
fair
question,
yeah
I
but
I
think
I'm
not
allowed
to
actually
say
when
exactly
that
happen
now
on
on
the
on
the
settings,
so
this
is
already
a
slightly
customized
size.
A
A
Point
is
being
the
solutions,
so
in
the
SPF
solution
repository
if
I
go
to
the
solution,
folder
we
used
to
have
here
SP
dev
preview
solution.
It
will
be
there
relatively
soon
again
and
from
there
you
can
actually
download
than
ASP
pkg
phone,
which
you
can
use
for
testing
the
modern
experiences
so,
in
my
case,
I
already
installed
that
in
here,
and
that
means
that,
as
an
example,
I
have
a
custom
footer
included
in
my
all
of
my
pages
within
the
site.
A
So
it
doesn't
really
matter
in
my
in
the
Welcome
page
of
the
con
documents
list.
It
will
actually
have
that
footer
I
rendered
there
or
in
my
in
the
Welcome
page
of
the
site,
and
there
is
the
photo,
actually
render
there
as
well.
So
that's
the
the
SharePoint
framework
extension
added
in
the
in
this
level.
Also,
what
that
solution
will
contain
is
a
simple
custom
web
part
and
the
source
code
for
it,
which
is
called
a
to
do
web
part,
and
it's
using
been
the
right
version.
A
I
was
technically
planning
to
upgrade
that
solution
earlier
today,
but
then
I
run
into
that
react
issue.
So
we
found
out
that
react
issue
earlier
today
and
that's
the
reason
why
that
solution
is
not
available
right
now
from
from
the
katana,
but
here
we
have
a
sample
SharePoint
framework
report
running
on
a
page.
You
can
see
that
there's
no
really
post
backs
it's
a
modern
experience.
It's
a
fluent
experience
and
I
cannot
do
trop.
A
Trash
I
can
add
tasks,
for
example
to
the
task
list
behind
of
the
scenes
and
there's
a
fluent
experience
for
doing
this
stuff
and
I
can
manipulate
things.
This
is
a
SharePoint
framework.
Wakeboard,
what's
behind
of
the
scenes
is
actually
creating
content
in
a
task
list
in
the
steam
side.
So
there's
now
two
items
behind
the
scenes,
but
basically
the
the
experience
are
pretty
much
the
same
within
the
modernist
modern
team
side
and
the
communication
science
as
they
were
in
the
ship,
went
online
earlier
this
year.
A
One
note
here:
we
were
slightly
running
out
of
time.
I
do
apologize
on
that,
but
if
I,
if
I
choose
the
sub
site
creation,
the
sub
site
creation
numbers
are
still
showing
the
classic
way
of
creating
subside.
So
there's
no
modern
sub
site
creation
style
because
that's
a
relatively
new
thing
and
SharePoint
Online
and
the
default
option
in
the
sub
site
creation
is
a
team
site
without
the
classic
Xperia
classic
experience
option,
and
this
is
a
modern
team
sign.
A
So
basically,
you
can
select
and
create
a
modern
team
sites
under
a
modern
component
team
sites
under
a
modern
team
sites
or
communication
side.
So
now
we
can
actually
say
here,
for
example,
I
seek
and
I
can
choose
a
a
team
site
and
let's
actually
create
that
and
oh
let's
call
this
Cygnus
Oh
special
interest
group
and
creation
of
a
modern
team
site
is
relatively
fast
as
well
and
there
we
go.
We
have
a
modern
team
side
under
the
team
side
now
there's
most
likely,
and
we
need
to
talk
about
those
two
options
later
on.
A
But
if
one
one
logical
question
at
this
point
would
be
that
can
I
somehow
magically
control,
how
the
what
are
these
templates,
which
are
visible
in
the
selection
and
technically
you
can
actually
control
those.
So
if
you
would
like
to
filter
and
only
show
the
modern
team
site
and
not,
for
example,
a
classic
book
or
a
classic
project
side
or
a
classic
documents
and
their
side
here,
you
can
do
that.
You
can't
control
that,
but
that
requires
then
a
farm
level
configuration
or
farm
level
solution
which
will
then
filter
down.
A
What's
visible
in
this
in
this
selection.
Now
and
obviously,
if
there's
a
demand
for
all
of
those
questions
will
definitely
provide
guidance
on
how
which
you,
as
an
example,
filter
down
those
list
options
and
whatever
settings
has
to
be
done
for
your
customer
deployment.
But
we
really
need
to
understand
would
be
the
common
questions
where
people
are
having
common
things,
what
they
need
to
solve.
So
we
can
prioritize
our
time
efficiently.
A
There's
a
quick
question:
I
need
to
go
back
on
slides
because
we're
slightly
running
out
of
time.
I
do
apologize
on
that.
Maybe
just
quick
note
here
to
get
a
a
picture
screen
shot
for
David
as
well,
is
that
in
the
black
mentioned
in
the
15.9
version
of
the
which
is
the
chip,
1
2019
Chancery,
Visual
Studio
2017
latest
version
which
can
live
on
Tuesday.
It
actually
has
now
the
shape,
1
2019
farm
solution.
Templum
templates
are
able
to
actually
already
create
farm
solutions
in
Visual
Studio,
using
the
classic
template
models.
A
There
is
nothing
new
in
these
templates.
It's
just
a
vision,
pump
to
support
SharePoint
2019,
now
I'll
actually
flip
back
on
the
slides.
So
we
can
go
back
on
the
content
and,
if
needed,
will
absolutely
walk
through
more
shipment
winning
on
test
stuff
in
the
future
as
well.
This
is
kind
of
a
quick
run
through
everything.
What
is
supported
and
one
hours
isn't
a
humongous
amount
of
time.
There
is
a
question
from
you
on
around
SPF
x.
A
One
point:
seven
and
above
are
you
planning
to
add
support
for
shipment
29
2016
answer
is
no
we're
not
looking
into
upgrading
SharePoint
framework
support
in
SharePoint,
2016
and
people
might
be
wondering
on
why
well.
Chevonne
2016
doesn't
support
modern
experiences
so
and
because
Chapman
2016
does
not
support
modern
experience.
These
modern
pages,
modern
lists
and
libraries.
We
can't
up
create
the
SharePoint
framework
version,
which
it
would
actually
support
as
well.
So
we're
not
looking
into
up
changing
the
division,
support
on
SharePoint,
28
2016
right
now
in
SharePoint
2019.
A
The
supported
version
is
one
point,
four
point
X
like
mission
and
most
likely
it
might
be
that
there
will
be
a
version
pump
on
that
one
with
some
future
version,
maybe
for
SharePoint
2019,
but
there
has
been
no
decisions,
no
plans
who,
later
on
that
related
on
that
functionality,
thomas,
is
asking
worst-possible
SPF
X
custom
footer
also
shown
in
the
layout
spaces.
It
is
actually
shown
on
layout
pages
by
default.
If
the
the
custom
folder
is
available
and
on
the
side,
so
it
will
override
DF
by
default.
The
layout
space
is
like
the
site.
A
A
Well.Did
good
sorry
Russell
for
your
friend,
a
chef
on
2016
server,
cool,
sorry
for
taking
slightly
above
more
than
plan
from
a
timing
perspective.
We
really
wanted
to
walk
through
the
current
status,
all
of
the
different
things,
because
people
do
farm
solutions
and
resolutions,
add-ins
and
SharePoint
framework.
The
feature
is
absolutely
in
SharePoint
framework,
but
and
we'll
update
our
official
documentation
based
on
the
information
which
is
our
today
on
the
slides
as
well.
A
The
recording
of
this
session
will
be
available
in
YouTube
channel
within
24
hours
and
whenever
that
goes
live,
it
goes
live
together
with
an
air
with
a
plug
post
in
our
Dethklok
and
in
the
Dethklok
sorry
SharePoint,
dev
blog.
Let
me
actually
paste
that
one
more
time
there,
where
you
can
also
find
in
a
link
to
the
presentation,
so
we
were
able
to
download
the
presentation
which
were
used
today
as
well.
If
you
need
that
for
a
reference
for
anything
for
your
own
discussions
or
your
own
development.
But
thank
you
everybody
for
joining.
A
Thank
you
for
staying
a
slightly
over
time.
I
do
apologize
on
my
time
management,
five
minutes
over,
not
too
bad,
but
still,
and
hopefully
that
was
useful
for
the
on-premises
developers
as
well.
We're
not
forgetting
you.
There
is
a
big
part
of
people
who
are
doing
on-premises
deployments
and-
and
definitely
please
give
the
feedback
repeat
repeat-
repeat:
don't
give
up.
We
will
listen
as
long
as
we
know.
What
is
the
demand
for
the
on-premises
guidance
as
well?
It's
not
all
just
about
the
cloud
over
the
cloud
is
the
future.