►
From YouTube: Packaging and deploying .NET Core for Linux - Part 2
Description
In this episode, Rich sits down with Todd Gardner to talk about his team’s experience with building a real commercial product with .NET Core.
[00:50] - The good and not so good of choosing .NET Core
[05:15] - Sometimes things change
[07:05] - Thinking about performance
Host ASP.NET Core on Linux with Nginx
https://docs.microsoft.com/aspnet/core/host-and-deploy/linux-nginx?WT.mc_id=ondotnet-c9-cephilli
Visual Studio publish profiles (.pubxml) for ASP.NET Core app deployment
https://docs.microsoft.com/aspnet/core/host-and-deploy/visual-studio-publish-profiles?WT.mc_id=ondotnet-c9-cephilli
TrackJS
https://trackjs.com/
Request Metrics
https://requestmetrics.com/
The Building of Request Metrics (YouTube Channel)
https://www.youtube.com/channel/UCIklNDcnPT8_eVFM1oOoQyA/videos
#dotnet #linux #deployment
A
A
A
Hey
welcome
to
another
episode
of
the
on.net
show
today
we're
doing
part
two
with
todd.
Last
time
we
talked
about
how
he
deployed
asp.net,
core
apps
on
linux,
and
now
we're
gonna
talk
about
his
experience
of
using.net
core,
and
you
know
whether
that
was
a
good
idea,
thanks
again
for
being
on
the
show
todd.
A
So,
let's,
let's
just
like
dive
straight
into
it,
you
know,
I
guess,
like
you
know
any
regrets
like.
Okay,
yeah,
let's
see,
let's
see
what
what
do
we
want
to
cover?
It
should
be.
What
did
you
like
about
using
dynacore
doing
a
real
project
on
it?
What
surprised
you
in
a
positive
way,
what
surprised
you
in
a
negative
way
and
what
are
the
things
that
it's
like?
I
really
want.
This
changed.
B
Can
I
can
do
those
things
all
right,
so
what
was
surprising
or
let's
put
the
headline
up?
First,
do
I
have
any
regrets?
No,
I
think.net
core
worked
great
for
us.
It
was.
It
was
a
good
move
for
us.
I
have
no,
no,
no
regrets
no
problems
with
the
overall
decision.
There
was
no
other
alternative
out
there
available
to
us
that
would
have
fit
our
needs
quite
as
as
well
things
that
worked,
particularly
surprisingly.
B
Well
for
us
was
around
packaging,
which
is
what
we
talked
about
in
the
last
episode,
the
ability
to
take
our.net
core
application
and
package
it
down
to
a
single
file
and
not
need
to
worry
about
deploying
a
framework
to
our
servers
or
getting
the
runtime
up
and
going
just
having
a
file
and
putting
it.
There
was.
Oh,
it
was
so
it
was
so
refreshing
and
nice
to
not
need
to
worry
about
this
on
on
both
sides
of
the
deployment.
B
Maybe
some
of
the
things
that
were
a
little
frustrating
is
the
overall
asp.net
core
kind
of
stack
seems
very
married
to
the
idea
of
dependency
injection
and
everything
is,
is
based
on
the
idea
that
you
you're
absolutely
going
to
be
running
one
of
these
in
di
containers
and
you're
absolutely
going
to
want
to
inject
all
these
things
with
middleware,
and
I
frankly
don't
want
to
do
any
of
that.
We
tend
to
keep
our
our
asp
stack
like
really
thin
and
try
not
to
do
a
bunch
of
stuff
in
that
layer.
B
B
The
dependency
injection
ideas
kind
of
get
in
the
way,
and
we
end
up
like
kind
of
round
housing
around
how
asp.net
wants
to
work
with
middleware.
I
really
love
the
concept
of
middleware
taken
from
you,
know,
node.js
and
express,
but
we
don't
use
any
of
it
in.net
core,
because
it
seems
to
be
forced
down
the
idea
of
dependency
injection
to
make
any
of
it.
Work.
A
B
A
few
things
in
the
middle
link
continues
to
be
amazing.
Every
time
I
leave
you
know,
net
development
for
javascript
and
then
come
back,
and
it's
just
it's
so
amazing
the
the
the
tool
chain.
It's
so
good
that
I
I'm,
I
don't
know
why
it's
not
a
default
using
in
the
classes
anymore
like
when
you
create
a
class.
It
used
to
just
be
like
you're,
using
link,
of
course,
you're
using
link.
Why
wouldn't
you
use
link
and
now
I'll
like
just
start
typing
something?
It's
like.
I
don't
know
what
map
means.
B
A
B
A
A
So
in
some
cases
like
you
had,
you
know
a
particular
property
exposed
in
a
place,
but
it
was
exposed
too
low.
So
as
a
result,
it
like
caused
this
total
dependency
chain
to
exist,
and
if
you
moved
it
to
a
different
place,
then
you
didn't
have
that
problem,
and
so
what
it
enabled
is
for
people
that
were
using
just
low-level
apis.
A
Then
they
didn't
need
to
bring
high-level
apis
with
them
and,
like
you
know,
I
saw
you
obviously
you're
using
self-contained
and
trimming
well
that
that
helps
a
lot
for
that
scenario
is
just
breaking
api
dependencies.
So
that's
one
that
when
asp.net
core
and
also.net
core
was
was
first
introduced.
That
was
at
least
one
of
the
the
design
considerations
at
play,
so
just
fyi
that
doesn't
change
any
of
your
feedback
to
be
like.
B
It
makes
a
lot
of
sense
and
I
I
totally
get
it
I'm
only
just
sharing
that,
like
that
was
a
point
of
friction
like
going
from
old.net
into
the
new
one
like
we'd,
be
off
and
running
and
like
you'd,
get
80
of
the
way
there
just
like
going
from
muscle
memory
and
like
here's,
just
how
it
works
and
blah
blah
blah
and
then
all
of
a
sudden.
It's
like
that.
That
object.
Isn't
there
anymore
or
it's
just
what?
Where
is
it?
How
do
I
get
it?
B
A
A
A
A
And
it's
the
sort
of
thing
where
it's
difficult
for
a
user
to
rewrite
their
code,
to
avoid
some
of
these
things.
So
if
we
can
just
change
them,
then
it
just
removes
the
whole
conversation
for
sure.
Okay.
Well,
I
think
maybe
maybe
this
was
pretty
good.
I
really
just
wanted
to
get
your
feedback
on
kind
of
the
highs
and
lows
from
your
perspective.
Obviously
yeah
cool,
okay,
awesome!
Well,
thanks
for
you
know,
taking
the
time
out
just
to
do
another,
quick
video
to
give
your
feedback
on
the
product.