►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
Awesome
well,
this
is
this
is
oddly
quiet
we
have
fewer
people
today,
so
this
is
this.
Is
me
and
Steve
Sanderson
on
the
SP
community
stand
up
so
I'm
gonna
be
sharing
some
community
links.
Steve's
gonna
be
showing
off
some
updates
for
the
spot
templates
and
we
will
be
happy
to
take
any
questions.
So
it's
great
all
right.
So
let
me
share
my
screen
and
we'll
just
get
right
to
it.
This
is
this
is
so
strange
for
me.
I'm
used
to
people
interrupting
me
all
the
time.
Sorry
I'll!
Thank
you
all
right.
A
So,
first
of
all
we
have
we
have
a
post
from
Dan
broth
on
the
SP
note
team,
and
this
is
about
preview,
one
of
SP
net
nbc5
point-to-point
for
web
api.
Five
point
two
point:
four
and
web
pages
three
point
two
point:
four,
and
the
big
thing
here
is
web
api
client
support
for
dotnet
standard,
so
showing
how
you
can
use
web
api
client
and
calling
into
asp
net
core-
and
you
know
using
all
the
dotnet
standard,
goodness
there
with
the
code
sample
and
all
that,
so
that
is
cool.
A
Next,
we
have
a
few
kind
of
like
debugging
perf
analysis
tips,
so
this
one's
from
benjamin
perkins
always
great
stuff
from
him.
So
this
one
is
on
capturing
an
asp
net,
core
memory
dump
on
azure
app
service.
So
in
this
case
he
shows
publishing
gap
service
and
then
going
out
to
to
kudu
and
digging
into
process
explorer
and
capturing
a
full
dump.
And
then
you
know
what
you
can
do
with
that.
So
that
is
handy.
A
We
also
have
one
on
per
view
traces
from
Naveen.
So
this
is
this
is
an
example
showing
some
code
here:
logging
some
things
out,
writing
in
some
debug
and
logging
commands
and
then
going
in
and
capturing
you
know
capturing
the
perfu
trace,
so
that
also
handy
I
have
to
admit
I,
don't
really
know
much
about
perfu
I've
dabbled
with
it
a
few
times
and
it
gets
over
my
head
pretty
quick,
but
it's.
B
A
Right
now,
you
know
honestly
I
think
that
this
is
more
instantaneous.
This
is
this
point
in
time,
but,
like
I
said
I
I,
my
the
extent
of
my
perfume,
maybe
somebody
watching
can
jump
in
the
extent
of
my
perfume.
Allah
has
been
when
I've
been
running
into
some
problem
and
someone
would
say:
can
you
capture
perfu
for
me
or
something
you
know?
Okay,
that's.
A
This
is
cool
here.
This
is
a
coat
rack.
This
is
a
free,
profiler,
for.net
and
some
new
thing.
There's
a
nice
one
minute,
video,
like
literally
one
minute,
which
is
really
you,
know,
cool,
tight,
quick
explanation
of
what
it
is.
The
the
neat
thing
with
this
release
is
that
it
supports
plugins,
and
so
you
know,
there's
some
examples
of
plugins
and
showing
the
console
plug-in
here.
A
So
this
is
actually
as
part
of
the
you
know,
it
captures
the
the
console
output,
but
then
part
of
the
reason
I'm
mentioning
it
here
is
that
he's
asking
for
some
help
creating
plugins.
So
specifically,
here
we've
got
some
SP
net
experts
watching
so
anyone
that's
got
ideas
or
would
like
to
create
a
plug-in.
There
are
some
example:
plugins,
like
I,
said,
there's
this
console
plug-in
here,
and
so
this
is
an
example
of
you
know.
A
A
This
is
from
Elton
Stoneman.
So
Elton
is
a
death
of
Angeles
at
docker
and
does
a
lot
of
great
stuff
with
it
with
ASP
net
so
he's
here.
This
is
kind
of
an
in-depth
look
at
connecting
to
a
database
database
containers,
so
that
can
be
a
little
tricky
how
you
do
handle
the
networking.
So
you
know
explanation
about.
A
You
know
how
the
networks
and
DNS-
and
you
know
how
your-
how
you
can
configure
that
in
a
little
more
depth
inside
your
docker
file,
so
and-
and
you
know
digging
into
things
like
default,
password
and
custom,
password
and
stuff.
So
a
lot
of
good
stuff.
This
from
Jeremy
he's
looking
at
five
restful
web
design
patterns
in
asp
net
core,
so
that
you
know
there
are
different
styles
and
and
kind
of
patterns
that
people
use
around
rest
and
restful.
A
You
know
web
design
patterns,
so
it
really
kind
of
goes
through
them
with
some
implementations.
A
nice
thing
here
to
some
some
diagrams
as
well
so
kind
of
explaining
how
how
these
are
architected
and
showing
at
the
end
or
kind
of
all
throughout
actually
digging
in
with
swagger
and
showing
how
you
know
accessing
them.
A
Last
one
I
want
to
point
out
is
just
something:
that's
kind
of
neat.
This
is
Mark.
Rendell
tried
out
an
experiment,
this
is
called
beeline
and
what
he
wanted
to
look
at
here
was
serializing
to
to
jason
directly
using
the
new
kind
of
using
span
and
kind
of
all
the
new
goodies
in
dotnet
core
two
one
and
C
sharp
seven
two,
and
so
you
know,
with
direct
serialization
writing
directly
out
to
Jason.
A
He
was
interested
to
see
kind
of
what
would
his
performance
be
like,
so
he's
got
some
some
benchmarks
in
here,
and
he
said
you
know
he
was
hoping
for
better.
He
ended
up
about
ten
percent
faster
and
a
little
bit
lower
allocation
than
tapper.
So
you
know
it's
as
he
said,
you
know
it's.
It's
not
a
clear
amazing
winner,
but
it's
you
know
not
not
a
total
total
loss
of
time.
Here
you
know
could
be
useful
for
things
like
very
tight
micro
services
or
stuff
like
that.
A
So
just
need
to
see
the
experiment
and
and
I'm
glad
that
he
you
know
showed
that
off
yeah.
B
A
Something
that
people
asked
him
on
Twitter
when
he
was
discussing
it,
and
you
know
that
that
is
true.
The
post-grad
sequel
server.
Are
there
different
things
with
that?
I
think
he
had
said
some
of
the
thing
here
was,
you
know
like
storing
it
directly
without
even
kind
of
handling
it
like,
for
instance,
if,
if
you
want
database
portability,
there's
some
things
with
Jason
storage,
syntax
in
different
databases
is
different.
You
know,
so
you
kind
of
have
to
plumb
directly
into
that
database,
whereas
this
is
kind
of
writing.
Direct
jason
out.
B
Might
depend
on
how
relational
your
data
schema
is
and
to
what
extent
you're
relying
on
lots
of
cross-table
joins
me
yeah.
That
kind
of
indexing
I,
don't
know
how
good
sequels,
fairies
are
doing,
say,
indexing
on
specific
paths
within
Jason
box
and
so
on.
I'm
sure
they've
done
something
in
that
area,
but
yeah.
A
B
B
Cli
is
just
one
sort
of
standard
system
that
allows
everyone
to
know
our
project
should
be
structured
and
to
share
a
set
of
infrastructure
for
building
yet
so
we
got
this
message
pretty
clearly
from
the
community
that
you
want
to
us
to
have
our
templates
for
angular
based
around
angular
still
I
haven't
slowed
up.
So
that's
what
we've
been
doing
over
the
last
little
while
we
released
a
preview
of
some
updated
templates
that
work
that
way
couple
months
ago
and
then,
just
last
week
we
released
a
release
candidate
of
those
same
templates.
B
B
Okay,
just
going
to
okay,
don't
see
my
mouse
pointer
yeah.
Turning
off
my
video,
great
sorry
and
so
I
I've
got
these
templates
installed,
so
they
are
templates
that
are
built
into
their
net
new
system.
So
if
I,
don't
you,
then
you
will
see
that
I've
got
everything
it
core
with
angular
react,
react
and
redux.
Those
are
exactly
the
same
names
as
the
existing
templates
that
we've
already
shipped
but
I
have
installed
the
updated
template
packages.
If
you
want
to
install
the
packages
yourself,
you
can
go
to
the
following
web
page.
You
can
go.
B
B
We
go
right.
You
will
see
the
using
the
spa
project
templates,
release
Candida.
If
you
go
into
there,
it
will
give
you
the
relatively
small
bit
of
instructions
that
you
need
in
order
to
install
that,
and
we
just
run
that
command
on
the
command
line
and
then
you'll
get
these
updated
templates.
So
I've
used
this
to
create
an
angular
and
a
reactive,
temblor
I'm,
going
to
show
you
just
now
and
in
fact
I'm
going
to
do
that
in
Visual
Studio.
B
So
here's
my
angular
application
and
I'm
gonna
do
a
control
f5,
just
together,
I'll
take
a
couple
of
seconds
to
come
up.
What
you
see
when
that
does
come
up
is
that
it
looks
quite
similar
to
the
projects
that
we
had
before
with
the
existing
project
templates.
It's
really
the
implementation.
That's
changed,
not
the
initial
appearance
of
it.
B
B
Lot
longer
than
usual,
here
we
go.
Alright
I
think
my
my
laptop
is
suffering
badly
from
being
honest
and
Google
Hangouts
for
some
reason:
yeah
anyway,
okay,
so
the
application
comes
up.
It
looks
similar
to
what
we
have
before
it's
another
bootstrap
type
layout,
where
you
can
do
backwards
forward
and
so
on.
We've
got
simple
examples
of
an
angular
component.
For
example,
we've
got
an
example
of
fetching.
B
Some
data
from
the
server,
but
what's
different
from
before,
is
the
structure
of
the
project,
in
particular
the
contents
of
this
client
app
directory
and
if
I
just
open
this
in
Windows
Explorer,
you
will
see
if
you've
ever
used
the
angular
CLI
to
create
an
angular
CLI
project.
You
might
recognize
this
particular
file
structure,
because
this
is
exactly
what
comes
out.
We've
got
interesting.
Yeah
we've
got
sourcing
here.
We've
got
all
these
many
different
config
files
that
are
all
generated
by
angular
CLI,
because
that
is
what
the
angular
part
of
this
application.
Actually
is.
B
It's
a
standard,
angular
CI,
CLI
application.
We
haven't
made
any
changes
for
specific
to
XP
net
inside
this
we've
added
a
little
bit
of
content
and
that's
where
these
different
pages
are
coming
from,
but
we
haven't
changed
anything
about
how
it
actually
works.
So
the
files
in
this
folder
are
an
angular
CLI.
My
application
they've
got
exactly
the
same
kit.
That
is
every
tutorial
that
you
can
find
on
the
internet
about
how
to
do
stuff
with
angular.
Cli
is
all
going
to
work
with
this
because
it
is
a
standard,
angular,
CLI
project,
okay,.
A
B
A
B
B
Unit
tests
in
between
the
grounds
are
there
and
you
can
see
it's
executed
two
of
two
and
we're
happy.
It's
all
working
correctly.
I
can
also
do
other
types
of
tests
like
I
can
run
end-to-end
tests.
That's
a
built-in
thing
that
comes
out
of
angular
CLI.
That's
also
going
to
compile
and
launch
a
browser,
but,
unlike
before
it's
not
just
running
individual
components
in
isolation.
It's
now
actually
running
the
entire
application
and
automating
the
browser
to
click
around
on
the
UI
inside
there
and,
as
you
can
see,
it's
going
to
test
there
and
not
succeeded.
B
So
we
can
do
everything
with
this
that
you
can
do
with
a
normal
angular
application,
and
so
you
might
think
okay.
Well
is
the
point
of
that.
Then.
Why
is
that
beneficial?
Or
why
don't
I
just
create
an
angular
CLI
application
myself?
Why
do
I
need
your
special
temblor?
And
the
answer
is
just
that:
a
lot
people
fight
convenience.
You
have
a
single
project
that
they
work
on
that
contains
both
the
client-side
part
of
the
single
page
application
and
any
API
methods
that
it
relies
on
so
that
you
can
build
it
all
at
once.
B
B
That's
right,
yeah.
It
means
that
you
create
one
project.
You
do
one
thing
to
start
your
project
running
and
you've
got
the
both
the
front
end
and
the
back
end
running
simultaneously
and
yes,
we've
set
up
all
the
relevant
conventions
to
make
sure
that
the
front-end
and
back-end
routing
stuff
works
together.
A
So
one
thing
that
that
when
I,
when
I'd
looked
at
their
kind
of
earlier
releases
of
this,
there
was
there
was
work
involved
so
that
web
pack
was
running
and
and
when
it
was
doing
the
bundling
like
if
I
requested
a
file
and
it
was
still
being
built,
it
would,
you
know,
there's
a
whole
virtual
path
provider
or
whatever
that
kind
of
virtual
file
provider.
Is
that
still
involved
there
or
has
that
changed
with
the
CLI
integration?
Okay,.
B
So
it
doesn't
matter
whether
you
want
to
build
an
MVC
site
or
a
razor
pages
site
or
your
own
weird
thing:
on
top
of
asp
net
primitives,
it's
all
going
to
work
the
same,
because
the
way
it's
ourselves
now
is
using
middleware,
and
that
is
how
we
can
control
the
build
system,
which
is
what
you
were
just
getting
out
there.
So
now,
if
we
look
inside
the
the
startups,
TS
you'll
see
that
we've
got
under
the
normal
use.
B
Mvc
we've
got
used
spar
and
that's
going
to
deal
with
receiving
requests
to
the
server
that
are
supposed
to
render
the
client-side
application
so
for
any
unrecognized
URL.
That
is
all
URLs
that
are
not
matched
so
the
normal
routing
system
that
you
using
on
the
server
which
in
this
case
is
MVC
that
wouldn't
have
to
be.
They
are
all
going
to
serve
the
default
page
for
the
single
page
application
and
you
can
control
where
on
disk
that
is
coming
from
and
what
I've
also
got
here
is
this?
B
What
occurred
that
says
if
we're
running
in
development
environment
then,
instead
of
assuming
that
the
angular
application
has
already
been
compiled,
I'm
going
to
start
up
dynamically
an
instance
of
the
angular
CLI
server
and
I'm
going
to
pass
through
any
requests
to
that.
So
that
is
how
the
application
is
getting
compiled.
It's
a
little
easier
to
see.
B
Actually,
if
I
run
it
on
the
command
line,
rather
than
just
launching
it
from
the
S,
so
I'm
going
to
just
kill
my
web
server
instance
there
and
go
back
to
you,
the
command
line
and
if
I
run
dotnet
run
now
you'll
see
that
well,
first,
it's
going
to
compile
the
dotnet
code
as
usual.
Then
it
will
start
up,
and
so
now
I've
got
a
nice
clean
application.
B
This
is
what
we
were
breaking
for
the
father
before
we're
waiting
for
the
angular
CLI
to
finish
during
this
build
and
when
it's
finished
doing
that
which
takes
you
know
five
seconds
or
so
or
longer,
if
you're
on
a
Google
hangout
for
some
reason,
then
it
comes
up
in
the
web
browser
there.
So
that's
one
of
the
various
ways
that
we're
guaranteeing
that
behavior
is
exactly
the
same
as
a
standard,
angular
CLI
application,
because
we're
using
the
angular
CLI
server
amongst
all
the
other
things
that
got.
A
B
Yeah,
it
will
definitely
not
change
existing
application
that
you've
already
created,
because
it's
just
a
package
of
templates.
It's
not
the
template
package
itself
does
not
contain
any
runtime
packages,
your
projects
that
you
create
where
they're
do
use
new
runtime
packages,
but
the
fact
that
you're
getting
new
runtime
packages
for
those
projects
will
not
affect
your
other
projects
on
your
machine.
One
way
might
affect.
You,
however,
is
that
you
can
only
have
one
dotnet
new
angular
or
one
Donette
new
react
command
installed
within
a
given
des
SDK
a
given
time.
B
B
Well,
that's
a
very
different
subject.
So,
okay
by
austin
norfolk
apps,
I
guess
that
he
means
to
do
with
server-side
rendering.
So
the
idea
is
that
your
code
could
run
on
the
server
as
well
as
it
could
run
on
the
client,
and
that
is
a
feature
and
that
we
have
had
in
our
previous
templates
for
the
angular
and
we
actually
the
redox
templates
that
we
did
not
have
the
reactor
template
I'll,
explain
why
that
is,
and
then
I'll
also
explain
why
we're
changing
this
arrangement
in
the
newer
templates.
B
So
in
the
previous
set
of
templates,
we
wanted
to
have
it
turned
on
by
default
wherever
possible,
because
we
figured
that
it's
easier
to
turn
it
off
than
it
is
to
turn
it
on,
like
anybody
can
just
turn
stuff
off
at
any
time
they
want
to.
But
if
you
want
to
turn
this
stuff
on
well
that
relies
on
you
not
having
done
anything
that
makes
it
difficult
to
turn
it
on.
I've
been
relied
on
in
the
assumptions
that
you
won't
be
doing,
server-side
rendering.
B
So
that's
why
it
was
on
before
and
previously
we
in
the
reactor
world.
We
only
had
it
on
the
Redux
template
and
not
the
react
without
redox
template,
and
the
reason
for
that
is
because
the
way
that
reacts
server-side
rendering
works
is
that
it
relies
on
the
idea
that
can
generate
identical
markup
on
the
server
to
you,
how
to
generate
it
on
the
client
and
in
order
to
that,
you
have
to
be
able
to
pass
the
stay.
B
B
Now,
if
you
don't
have
redux,
how
are
you
going
to
transfer
that
state
from
the
server
to
the
client
and
the
answer
is
you're
going
to
invent
your
own,
really
bad
version
of
redux,
and
so
we
figured.
Why
would
we
do
that?
Why
don't
we
just
say
if
you
want
to
do
this,
you
should
be
using
redux,
because
it's
the
only
thing
that
really
makes
sense,
don't
invent
your
own
bad
version
of
it
when
there
is
a
standard
think
out
there
that
you
can
do
now.
B
Does
that
make
sense?
Yep,
okay,
all
right,
good,
yes,
but
we're
changing
it?
Alright!
So
here's
what's
going
to
be
different
with
the
new
templates
in
the
new
templates,
we
will
not
have
server
side
rendering
turned
on
by
default
and
we
will
not
have
any
out-of-the-box
straightforward
way
of
doing
it
for
react
or
react
with
redux.
We
will
only
have
it
for
angular
now.
I
know.
That
sounds
like
two
steps
backwards,
so
let
me
explain
why
we're
making
those
changes
right.
B
So
the
reason
why
most
people
don't
need
it
is
because
most
of
the
applications
that
people
are
creating
with
angular
on
react
are
being
served
over
peoples
intranets
within
some
sort
of
cooperation
that
has
fast
internet
connections
and
people
are
just
accessing
these
business
web
applications
on
a
desktop
browser
and
in
that
case,
you'll
get
a
lot
of
benefit
from
server-side
rendering,
because
the
performance
of
starting
up
the
application
is
really
perfectly
good
anyway
time
from
0.2
of
a
second
2.05
of
a
second,
it
doesn't
make
any
real
difference
to
human
beings.
B
However,
it
does
make
your
development
experience
way
more
complex
because
it
forces
you
to
write
your
code
in
such
a
way
that
it
can
run
in
two
completely
different
runtime
environments.
You
have
to
write
your
code
such
that
it
works
both
under
node
for
service
of
IDE,
rendering
and
in
a
browser
for
client-side
rendering
and
those
two
runtime
environments
are
different.
They've
got
different
capabilities,
there
are
different
API
available
and
people
were
constantly
tripping
up
on
this.
B
The
most
common
thing
that
people
do
is
they
try
to
use
browser,
specific
api's
like
window
or
local
storage?
That's
our
thing
and
then,
when
it
tries
to
run
on
the
server
side,
rendering
node
that
just
gives
you
an
exception,
because
those
api's
don't
exist
that,
and
so
people
are
constantly
getting
troubled
by
that.
Okay.
B
Absolutely
yep
so
for
people
who
do
want
to
have
side
rendering
with
the
new
tablets
you
can
go
into
our
documentation.
Let's
say
here
for
the
angular
project:
template
and
you'll,
see:
we've
got
this
server-side
rendering
link
down
here
and
it
walks
you
through
the
process
of
exactly
what
code.
You
need
to
add
a
why
each
part
of
it
is
needed
so
that
you
get
server-side
rendering
in
your
application,
and
we
hope
that
for
the
presumably
5%
or
so
of
people
who
want
to
do
that,
that
will
be
a
reasonably
straightforward
thing.
B
A
I
really
like
with
that
is,
as
you
pointed
out
there,
it's
explaining
what
what
specifically
you're
doing
and
why
that's
it.
That's
a
difficulty
with
a
lot
of
these
templates,
where
it
kind
of
code,
spews
tons
of
code
out
there
and
you
don't
feel
like
you
own
it
or
understand
it.
So
the
this
seems
really
useful,
like
you
said,
if
you're
gonna
use
it,
you
need
to
understand-
and
you
know
like
own
the
code
so
you're
able
to
handle
things
if
they're
not
working
right,
absolutely.
B
Yeah
and
then
the
other
change
is
that
we're
not
going
to
have
this
there's
no
equivalent
documentation
react
now
there
might
be
in
the
future,
but
there
isn't
today,
and
that
is
because
the
create
react
app
tooling.
That
is
the
basis
of
the
react.
Templer
does
not
itself
have
any
mechanisms
of
building
service
side,
rendering
capable
bundles
the
create
react.
Type
project
has
just
decided
that
it's
out
of
scope
to
them,
so
there
isn't
any
sensible
way
for
us
to
enable
that,
while
also
being
consistent
with
create
react,
app
conventions.
B
So
that's
just
how
that
is.
If,
if
you
want
to
change
that,
then
please
work
with
the
create
react,
app
people
to
get
them
to
add,
at
least
in
the
same
level
of
support
that
angular
CLI
does
and
then
we
will
be
able
to
build
on
that.
But
and
until
that
exists
it
will
be
up
to
developers
to
use
the
create
react.
App
eject
feature
from
the
project
which
converts
it
into
a
standard
web
pack
based
project,
and
then
you
can
go
through
adding
in
all
the
extra
web
pack.
B
A
B
Another
good
question,
so
that
was
going
to
be
one
of
our
top
features
in
the
2-1
timeframe,
but
because
we
changed
our
focus
completely
to
these
new
they're,
partly
tooling,
based
templates
that
has
dropped
way
down
our
priority
list.
So
there
isn't
it's
not
currently
on
my
to-do
list
or
it's
not
anywhere
near
the
top
anyway,
so
I'm,
not
promising
that
that's
gonna
happen
anytime
soon.
It's
something
that
we
know
would
be
a
good
thing
to
have,
and
we
do
to
have
it.
B
It's
just
that
we're
focusing
on
other
stuff
at
the
moment,
and
so
it
would
be
great
if
anyone
in
the
community,
you
has
figured
out
a
method
that
they
consider
to
be
good
practice,
that's
applicable
to
other
people's
projects,
to
put
something
up
on
the
wiki
inside
the
JavaScript
services,
repo
I'll
do
a
blog,
post
or
whatever,
and
then
you
know
that
would
be
really
useful
and
when
we
get
to
it,
we
would
like
to
have
some
documentation
around
that.
But
it's
just
not
done
yet.
Okay,.
A
A
B
I
have
not
used
ng,
rx
and
I
can
only
just
vaguely
guess
at
what
it
does
from
its
name,
in
that
it
must
provide
some
kind
of
state
container.
They
expose
this
reactive
API
so
that
you
can
observe
changes
to
the
stay
I'm
guessing
primarily
wrong.
I'm,
not
really
qualified
to
answer
this
question
because
I
do
not
really
know
ng
or
X,
and
we
don't
have
any
specific
plans
to
do
anything
with
it
as
a
general
principle.
B
Our
goal
for
these
new
templates
is
to
be
as
consistent
as
possible
as
what
is
the
de
facto
standard
for
each
third-party
spar
framework.
So
in
the
world
of
angular,
that's
angular
CLI,
we
don't
aspire
to
do
anything
different
from
angular
CLI.
It's
just
not
desirable.
Everything
that
we
do
that's
different
is
going
to
trip
people
up,
because
every
additional
feature
we
add
is
going
to
be
a
thing
that
people
don't
know
how
to
combine
with
third-party
tutorials
or
or
whatever.
B
So
our
goal
is
to
stay
completely
consistent
with
what
comes
out
of
the
box
with
angular
CLI,
so
that,
if
you
want
to
do
angular
programming,
you
just
do
angular
programming
like
you,
don't
have
to
do
special
SP
net
version
of
angular,
but
you
don't
we're
not
telling
you
how
to
do
angular
stuff.
You
can
go
to
angular
to
become
part
of
the
angular
community
and
do
whatever
angular
people
say
and
it's
all
gonna
work
the
same,
because
we
are
just
letting
you
do
a
standard,
angular
application.
Okay,.
A
B
Well,
I
suppose
that
really
fits
in
with
the
previous
answer,
which
is
it's
as
easy
or
as
hard
as
it
is
to
do
it
with
the
standard
19
CLI
application.
Ram
I
would
hope
that
whatever
tutorials
you
find
us
say
how
to
use
parcel
with
angular
CLI
or
with
react,
create
rag
damned
if
that's
what
they
are
using
are
going
to
work
the
same.
B
A
So
we
have
a
few
people
jumping
in
explaining
what
ng
Rx
is
so
I.
Guess
it's
an
opinionated
redux
with
all
the
extensions
and
first-class
for
support
of
reactive
extensions
for
angular,
2,
plus
apps,
great
Lance
kinda.
As
you
guess,
there
yep
a
question
from
Doug
asking
any
plans
to
add
the
ember
CLI.
B
We
don't
have
a
handler
template
right
now.
We've
had
little
to
no
demand
for
it.
If
there
was
another
spar
framework
that
we
were
to
focus
on
next,
it
would
definitely
be
view
because,
there's
far
far
more
demand
for
that
than
there
is
for
Amber,
but
yeah
we're
not
we're
not
currently
got
any
specific
schedule
on
expanding
the
number
of
spa
based
templates
that
we
ship
we
do
have
currently
templates
for
our
angular
react,
react
and
redux
view
knockout
and
I
really
am.
B
However,
the
view
knocked
out
on
a
really
a
template
for
in
a
separate
package
that
just
not
ship
with
the.net
sdk,
because
there's
a
limited
amount
of
capacity
in
the
asp
net
team
for
the
wider
team
to
understand
all
these
third-party
frameworks
and
to
keep
up-to-date
with
all
the
changes
with
them.
So
really
we
want
to
enable
the
community
that
cares
about
a
specific
third-party
framework
to
manage
the
the
templates
of
the
packages.
Flora,
the.net,
a
new
system
itself
is
fully
extensible,
so
anybody
who
wants
to
ship
a
template
of
that
can
do
so.
B
The
all
of
the
technology
that
we've
used
to
create
the
angular
CLI
base
project
and
the
reactor
3
ducks
and
the
react
projects
are
all
in
NuGet
packages
that
you
can
consume
and
use
to
create
your
own
terms
or
packages.
If
you
want
to,
and
so
I
would
really
like
to
see,
the
whatever
part
of
the
community
is
enthusiastic
about
ember
to
create
an
ember
template
and
then
we
can
promote
it,
and
we
can
say
this
is
great,
but
yeah.
We
can't
create
one
for
every
third
party,
all
right,
yeah,
yeah,.
A
I
played
a
bit
with
ember
more
lately
because
of
glimmer,
and
it
was
I
didn't
quite
get
it
all
to
work,
wasn't
running
on
Windows
for
me
at
the
time,
but
there's
some
interesting
things
with
how
they
do
serialization
that
they
like
have
this
bytecode
thing
that
they
shipped
down
to
the
browser
which
was
interesting,
yeah
yeah,
but
okay.
So
now
we're
in
we're
getting
some
suggestions
and
wishlist
things.
B
Do
that
I
just
want
to
show
this
one
last
thing,
because
I
think
this
might
change
a
little
bit
of
what
people
see
as
being
the
workflow
for
this
one
thing
I
pointed
out
when
I
saw
it
the
first
time
with
us
there,
it
took
you
know,
5
to
10
seconds
to
start
up
and
that's
because
it
was
running
the
angular
compiler.
In
the
background
now
one
issue
with
that
is:
let's
say
that
you
are
making
a
lot
of
c-sharp
code
changes,
but
so
you
change
your
c-sharp
just
as
often
as
you
change
your
typescript.
B
Well,
that
would
be
kind
of
annoying,
because
every
time
you
change
your
c-sharp
code,
it's
going
to
restart
the
ASP
application,
which
means
it's
then
going
to
restart
the
angular
compiler
and
go
through
this
10
sec
compile
process
all
over
again.
Now
that
would
be
pretty
annoying
if
every
single
suitor
change
forced
you
to
wait
for
10
seconds
for
the
application
start.
B
So
one
thing
we've
done
to
make
it
possible
to
be
much
faster
still
is
that
you
can
optionally
run
the
angular
server
or
the
create
react
app
server
as
a
separate
process
in
the
background
and
just
connect
to
it
from
your
SP
net
application.
So
you
get
exactly
the
same
level
of
integration
at
runtime.
You
just
don't
have
to
keep
restarting
the
angular
several
other
reactive
server.
The
benefit
is
obvious.
It
starts
that
much
faster.
Their
cost
is
that
you
have
to
manually
start
it
up
in
a
command
prompt
yourself.
B
So
let
me
show
you
how
we
can
do
that
I'm
going
to,
let's
see,
let's
go
to
a
different
console
here.
I'll
go
to
my
my
angular
app
and
I'm,
going
to
go
into
client
app
here
and
I'm
gonna
run
ng
served
and
that
is
going
to
start
up
the
angular
server
as
a
standalone
process,
and
it's
going
to
listen
on
this
port
localhost
4200
right
now,
I'm
going
to
go
to
back
to
my
asp
and
application.
B
I'm
gonna
shut
that
down
and
I'm
switching
to
my
source
code
and
I'm
going
to
say:
okay,
I,
don't
want
to
use
the
angular
server
anymore,
because
I
don't
want
to
keep
waiting
for
it
to
start
up
instead,
I'm
gonna
use
use
proxy.
Just
spar,
development
server
and
I
can
give
it
the
URL
that
it's
listening
on.
So
it's
a
HTTP
localhost
4200
by
default.
Other
thing
you
can
make
it
run
on
other
parts
if
you
prefer
alright.
B
So
then,
now
I'll
go
back,
though
here
and
undo
dotnet
run
again
and
this
time
when
it
starts
up
it
will
again
as
usual.
It
will
do
the
normal,
compiling
they've
done
encode
and
it
started
up,
but
it's
not
starting
of
an
angular
CLI
instance.
In
the
background
anymore,
when
I
go
to
this
URL,
we'll
see
that
it
comes
up
just
the
same
as
before,
and
I've
still
got
all
the
same.
Integration
as
before,
I've
still
got
all
the
kind
of
features
like
live
reloading
and
so
on.
B
B
A
A
A
Cool,
let
me
see
a
couple
of
more
questions
here
if
it's
okay,
to
jump
back
to
those
good
for
yeah,
I,
I,
think
that
totally
makes
sense.
So
that's
that's
really
useful
what
you
just
showed
there.
So
here's
a
question:
can
anyone
tell
me
the
difference
between
dotnet,
new
and
yeoman,
so
I
think
we
Gilman
it
well.
You've
had
some
history
there
I'm
with
the
yeoman
side
here,
yeah,
okay,.
B
So
yeoman
is
a
a
tool
based
on
node.js,
yes,
tool
for
generating
projects.
It
can
generate
any
sort
of
project
right.
Rather
it
can
generate
any
set
of
files
on
disk
if
somebody
publishes
a
suitable,
temp
and
em,
and
so
we
used
to
have
our
spar
templates
bill
on
German,
because
when
we
first
started
this
project
about
two
years
ago,
the
only
available
option
and
it
was
fairly
standard-
and
it
was
quite
convenient
both
for
us
to
create
those
templates
and
for
people
using
them
to
get
them
using
that
way.
B
But
since
then,
dotnet
nu
has
become
the
standard
way
to
create
Dom
net
projects.
It
knows
specific
things
about
not
dotnet
such
as
how
to
restore
dependencies
and
how
to
fetch
templates
from
NuGet
packages
and
that
sort
of
thing.
So
since
that
has
become
standard,
it
made
sense
for
us
to
switch
over
to
shipping
our
templates
and
on
that
new
instead
of
on
yeoman.
So
we
no
longer
maintain
the
yeoman
templates.
We
could
maintain
both
human
and
don't
net
new
templates
at
the
same
time
if
we
wanted
to.
B
A
B
Yeah,
if
someone's
keen
to
come
up
with
a
design
pad
I,
should
work
and
is
interested
in
working
with
us
on
making
that
happen,
then
please
file
an
issue
on
the
JavaScript
services
issue,
tracker
and
we'll
see
if
we
can
get
somewhere
with
that.
But
it's
not
something
that
we
specifically
have
any
timescale
on
at
this
point.
Okay,.
B
Silly
yeah:
well,
we
are
well
aware
that
web
assembly
is,
you,
know,
sort
of
floating
out
into
the
web
develop
and
every
browser
now
supports
and
there's
lots
of
obviously
entities.
There
I've
personally
been
having
some
fun
during
storage.
Think
of
a.net
based
single
page
application
and
framework,
and
a
lot
of
people
have
said
they
are
interested
in
that,
and
so
that
is
a
thing
we're
talking
about
on
the
team
and
trying
to
figure
out
if
and
how
we
can
do
something
with
that.
B
A
B
Yeah
so
we've
got
the
I
know.
It's
really
not
obvious
at
all.
It's
kind
of
a
historical
work,
but
the
the
work
on
these
templates
is
coordinated
largely
on
this
JavaScript
services,
repo
or
at
least,
if
you
post
an
issue
there
I'm
going
to
see
it
personally,
even
though
the
code
for
it
is
actually
on
this
other
repo,
then
templating.
B
No,
that's
great,
so
I
haven't
shown
any
record
templates
at
all
really
need
to,
but
you
can
just
use
your
imagination
and
just
substitute
the
word
react
or
angular
in
basically,
everything
that
we
talked
about
would
be
correct
because
other
than
the
server-side
rendering
feed
show
the
exact
equivalents
are
true
for
react.
With
these
templates
and.
B
Yeah
they
look
exactly
the
same,
and
the
implementation
for
the
read
react.
Standalone
template
is
almost
like,
looks
the
same
in
terms
of
the
layout
of
files
and
so
on.
It's
very
very
similar.
The
redux
one
is
very
different,
because
Redux
itself
is
a
totally
different
type
of
architecture
and
still
which
of
those
two
you
want
to
use
really
just
depends
on
your
own
architectural
preferences.
A
B
A
All
right,
well,
I,
guess
I
guess,
that's
it!
So
thanks
a
bunch
for
your
time.
This
was
fascinating
for
me
and
it's
exciting
to
see
the
the
you
know,
kind
of
updates
and
as
I've
used
the
templates
in
the
in
the
past,
it
has
been
kind
of
like
I
felt
like
I'm,
often
the
the
asp
net
version
of
angular
or
react
in
the
past,
because
all
the
CLI
and
all
that
stuff
didn't
apply.
It's
exciting
to
see
that
now
kind
of
merge
back
together.