►
From YouTube: .NET Foundation Project Spotlight - DotVVM
Description
.NET Foundation Marketing Committee member Isaac Levin spoke to Tomáš Herceg, one of the maintainers of DotVVM. For more detail, be sure to check out the Project Spotlight page
https://dotnetfoundation.org/projects/spotlight?project=DotVVM
A
A
B
Yeah
sure
so
the
tvm
is
an
web
framework
for
making
websites
and
web
applications
it's
using
the
mvvm
approach.
So
if
you
know
mvvm
from
wpf
or
submarine
projects,
dot
vm
will
be
very
easy
to
to
start.
Because
the
pattern
is
is
the
same.
You
have
view
models
in
c
sharp
and
you
are
just
using
html
as
templating
language
for
for
the
views
and
basically
you
can
use
the
vm
for
two
different
things.
B
So
you
can
install
vm
in
into
existing
web
forms
application
and
start
to
migrate,
the
application
to
net
core
page
by
page,
so
incrementally,
because
these
two
technologies
can
run
side
by
side
in
the
same
application,
and
this
scenario
is
getting
more
and
more
popular.
Actually,
maybe
most
of
the
new
users
of
dot
vm
are
using
it
to
modernize
old
apps,
because
the
the
ability
to
write
new
applications
using
the
mvvm
pattern
is
also
quite
feasible.
But
it's
not
the
only
way
how
to
make
web
apps.
A
B
A
You,
if
you're
building
dot,
if
you're,
building.net,
core
apps
or
even
dotnet
framework
apps
using
wpf,
is
like
a
big
example
right,
like
you
have
like
this,
this
mvvm
pattern
and
for
web,
you
have
that
more
mvc
or
even
like
client
server
type
of
interaction.
So
what
is
a
huge
benefit
to
using
mvvm
for
non-desktop
apps.
B
Approach
for
public
facing
websites
or
for
websites
that
are
more
presenting
data
to
the
users,
because
it's
it's
very
easy.
It's
it's
very
straightforward,
but
if
you
are
building
some
applications
that
that
maybe
they
shouldn't
be
on
the
web
at
all,
maybe
it
should
be
desktop
apps,
but
if
they
have
very
complicated
forms
with
multiple
steps
or
where
things
are
dynamically
changing
and
all
you
are
dealing
with-
is
to
have
some
very
complex
state
that
you
need
to
maintain.
B
Then
I
think
that
mvvm
can
be
a
great
way
because
you
are
working
with
one
view
model
which
can
be
very
complex.
It
can
have
child
objects,
it
can
work
with
collections
and
all
those
things
together.
There
is
two-way
data
binding,
so
these
pieces
of
the
view
model
can
interact
with
each
other.
So
if
the
user
interface
is
complicated
and
I'm
sure
everybody
has
seen
the
screens
with
hundreds
of
text
boxes
and
it
breaks
all
the
user
experience
rules,
you
can
imagine,
but
still
there
is
tons
of
these
applications
and
some
companies
or.
A
A
Yeah
no,
I
agree
and
I
think
a
lot
of
people
have
gone
down
this
path
with
mvc,
for
instance,
where
it's
okay.
I
have
a
lot
of
views
and
making
sure
all
these
views
are,
you
know
valid
making
sure
they
all
connect
to
each
other.
It
can
be
very
challenging.
So
it
sounds
to
me,
like
mvvm
kind
of
helps,
manage
that
complexity,
a
bit
better.
B
A
B
Maybe
some
crap
scenarios,
like
you,
have
a
great
list
of
records
and
then
you
have
a
detail
of
a
record
which
can
be
very
complicated.
It
can
have
multiple
tabs
or
something
like
that.
So
that's
that's.
The
main
use
case
that
we
went
was
created
for
because
I'm
running
a
software
company
and
we
have
been
building
a
lot
of
these
applications
and
we
kind
of
created
it
with
them
for
ourselves
to
have.
A
A
B
A
A
What
is
one
of
the
main
reasons
where,
like
obviously,
you
said,
you
were
working,
you're,
building
the
same
sort
of
projects
over
and
over
again
at
what
point
in
time,
were
you
like
hey?
This
is
this
is
something
that
everybody
can
use
and
then
what
was
that
process
like
of
quote
unquote,
open
sourcing?
It.
B
Yeah,
so
basically
we
needed
feedback,
because
I
was
always
worried
that
we
are
doing
the
things
our
own
special
way
and
it's
not
compatible
with
anyone
else
and
of
course
we
then
are.
We
are
restricted.
We
are
isolated
from
other
other
views,
so
I
I
and
at
the
beginning
it
really
started
like
that.
I
just
wanted
to
show
the
project
to
my
colleague
and
uploading
it
on
github.
What's
the
easiest
way,
it
was
easier
than
just
zipping
it
and
send
it
via
email.
B
A
A
Yeah,
no
that's
great,
and
what
I
think
is
really
really
interesting,
especially
about
vvm.
Is
that
you
can't
you
have
a
very
interested
approach
to
add-ons
right.
So
if
you
take
a
look
at
the
dot
vavm
site,
you
provide
a
a
quote-unquote
free
version
which
is
kind
of
like
the
bear
framework,
and
then
you
actually
provide
more
styled
ones
using
more
traditional
styling
like
bootstrap,
for
instance
right.
So
I'm
interested
in
the
decision
around
that,
because
one
of
the
things
that's
very
interesting
about
open
source
is
that
one
it's
very
hard
to
make
money.
B
Yeah,
so
I
think
that
it
started
very
early,
so
we
we
created
the
basics
of
the
frameworks
and
then
of
course,
and
also
it
was
driven
by
our
own
needs.
So
in
my
company
we
needed
to
build
some
project
on
bootstrap
and
we
could
we
we
wouldn't
need
that
commercial
add-on.
We
have.
We
have
created
because
it's
just
css
framework,
you
can
just
write
the
the
correct
sequence
or
hierarchy
of
diff
elements
with
the
correct
css
classes
and
it
will
work,
but
it
was
a
ton
of
code,
so
we
said
so.
B
We
thought
we
were
thinking
about
this
and
then
decided
okay.
So,
let's,
let's
keep
the
framework
open
source
and
free.
So
it's
available
for
everyone
and
there
are
no
restrictions.
You
can
do
anything
with
the
framework.
There's
no
there's
no
limitation,
but
if
you
are,
if
you
want
to
use
it
for
something
serious
and
you
want
to
save
some
time.
B
So
let's
make
this
a
commercial
because
it
will
help
the
framework
to
be
sustainable,
because
if
it's
only
a
framework
designated
for
one
company,
it
can
never
be
sustainable
and
everybody
would
be
worried
about
okay.
What
will
happen
in
one
or
two
years,
but
we
found
out
that
keeping
the
core
of
the
framework
open
source
and
free
is
great,
because
it
lowers
the
entry
barrier
for
everyone,
yeah,
and
also
people,
students
or
people
who
cannot
afford
to
pay
for
a
developer
technology.
B
They
can
use
it
freely
with
no
restrictions,
and
if
you
have
a
company-
and
you
want
to
use
it
for
serious
long-running
project,
then
being
able
to
support
the
project
at
least
with
buying
some
commercial
stuff
can
help
the
project
to
succeed.
So
I
think
that
this
is
the
only
model
that
could
work
in
the
long
term
and,
of
course,
it's
it's
very
difficult.
We
had
to
learn
about
how
to
do
marketing
it's
about
documentation.
We
have
to
provide,
because
we
are
charging
people
for
money.
A
A
The
number
one
thing
that
I
am
not
a
fan
of
personally
is
styling
it
and
it's
especially
if
it's
a
large
app
putting
css
markers
all
through
an
application
can
be
very
challenging
and
then
all
the
testing
that
comes
with
it
right
so
things
like
bootstrap
are
extremely
valuable
in
that
sense,
but
you
still
have
to
configure
bootstrap.
So
I
think
there's
it's
fair
and
it's
very
valid
to
be
able
to
ask
for
a
little
bit
when
people
want
to
use
mvvm
without
having
to
do
those
stylings
right.
B
My
biggest
problem
problem
with
bootstrap
was
that
I
was
still
looking
in
the
documentation.
I
wanted
to
create,
let's
say,
model
dialogue.
Okay,
so
I
go
to
the
bootstrap
documentation
copy
paste,
this
very
crazy,
long
piece
of
code
and
then
do
some
changes
in
it.
So
what
we
can
do
is
that
you
have
one
simple
component,
just
model
dialogue
and
that
vm
also
comes
with
a
free
extension
for
visual
studio,
which
gives
you
intellisense,
because
we
have
our
own
markup
language
based
on
html,
but
it's
different
than
razer.
B
B
A
A
A
Achievement
of
bootstrap,
I
mean
also
think
I
don't
have
a
very
creative
side
either,
like
somebody
gives
me
a
a
wireframe,
and
I
can
do
it
very
very
quickly,
but
the
thinking
around
that
is
what's
hard
and
the
ability
to
have
something
out
of
the
box.
That
looks
good,
like
I
think
that
just
makes
mvm
far
more
approachable
for
folks.
I
am
curious
when
about
the
community
of
mvvm
right.
I
know
that
a
lot
of
people
use
it.
Some
people
are
very,
very
passionate
about
right.
B
Well,
I
had
when
we
started
this
project
and
when
we
started
being
serious
about
open
source,
I
expected
more
community
involvement
like
at
least
more
submitted
issues,
or
maybe
even
some
pull
requests,
but
still
we
are
getting
some.
So
it's
it's
not
that
bad
and
what
I've
found
out
is
that
for
many
people,
it's
just
too
difficult
to
to
create
a
good
pull
request
that
can
be
just
reviewed
and
merged
into
the
code
base.
So
we
have
thinking
about.
B
B
But
it's
very
helpful
for
us,
because
that's
the
only
way
how
to
see
how
people
are
using
the
framework
and
what
features
they
would
they
would
like,
and
we
found
out
that
very
often
we
are
observe
we
are
running
into
the
same
problems
or
have
the
same
scenarios
as
the
people
who
are
using
the
the
framework.
So
it's
it's,
it's
a
feedback
and
it's
also
a
validation
of
our
own
thoughts
and
ideas.
So
that's
that's.
That's
very
helpful.
Of
course
it
can
be
better
in
every
situation.
B
You
will
find
something
to
complain
about,
but
we
are
getting
some
submissions
from
the
community
some
issues.
So
it's
not
bad,
and
I
understand
that
if,
if
somebody
is
working
on
the
project
on
the
tight
deadlines,
these
people
just
don't
have
time
to
clone
the
repository
and
to
try
to
understand
how
it's
composed,
how
you
can
build
it,
how
you
can
run
it
and
how
it's
working
internally,
so
they
can
fix
the
issues.
I.
A
The
new
discussions
feature
in
github
is
amazing.
Right,
like
yeah
it.
The
ability
to
just
have
a
conversation
outside
of
issues
and
pull
requests
is
super
valuable
and
I
think
one
thing
that's
great
about
dot.
Vm,
especially,
is
that
the
community
is
so
passionate
right
like
whenever
you
see
people
talk
about
evm,
they
immediately
get
very
excited,
because
even
the
community
isn't
as
big
as
you
know.
Maybe
the
mvc
community,
like
folks
that
are
really
diehard
nbc
fans,
but
they
know
that
there's
enough
of
them
out
there
and
it's
fun.
B
We
had
a
release
of
the
version
2.5.
It
was
in
november
and
next
month
in
february,
we
hope
to
release
the
vvm
3.0,
which
includes
almost
a
year
of
work.
So
it's
a
big
release
with
big
with
some
big
features,
and
one
of
the
most
important
features
is
the
we
don't
have
the
final
name
for
it,
but
we
are
called.
We
are
calling
it
page
modules.
B
Basically,
it's
a
way
how
you
can
better
interact
with
the
javascript,
because
the
3vm,
if
you
want
to
start
with
vm,
you
don't
need
to
know
javascript
at
all.
You
can
just
use
csharp
and
html,
because
that
vm
translates
bits
of
c-sharp
code
to
javascript,
for
you
and
the
rest
of
the
c-sharp
code
is
running
on
the
server.
B
So
this
integration
bridge
between
these
two
worlds
and
still
you
don't
need
to
know
javascript
you
use,
not
vpm,
but
still
we
are
on
the
web,
and
I
think
that
if
you
are
building
web
applications-
and
if
you
know
javascript,
you
will
be
way
better
web
developer
than
if
you
use
some
magic
tool
that
will
prevent
you
from
using
javascript.
Oh
sure,
that's
also
the
way
which
is
getting
more
and
more
more
popular.
Today,.
A
B
Yeah
yeah,
I
agree,
but
there
is
other
thing.
I
would
like
to
point
out
that
we
them
started
five
or
six
years
ago,
because
we
were
I
I
didn't
like
javascript
at
that
time,
but
there
was
a
huge
progress
in
the
javascript
world
and
if
you
look
at
javascript
today,
I
would
say
that
it's
completely
different
language
and
if
you
look
at
what
tools
are
available
and
how
it
evolved.
A
No,
that's
fair
and
javascript
has
definitely
came
a
long
way
other
you
know
when
it
first
started.
It
was
something
completely
different
than
what
it
is
now
I
guess
my
point
was:
is
that
for
a
lot
of
people,
javascript
is
still
challenging
at
times
and
the
ability
to
have
frameworks
that
kind
of
do
a
lot
of
the
plumbing
or
the
boiler
plate,
for
you
is
super
valuable.
A
A
Yes,
that's
a
great
lead
out,
so
one
of
the
things
that
I
want
people
to
do
is
I
want
people
to
go
to
the
dot
via
vm
website.
The
vvm
github
page.
Take
a
look
at
it.
You
know
maybe
open
some
issues,
pull
requests
or
help
thomas
out
with
the
documentation
which
I
imagine
a
lot
of
folks
probably
would
appreciate.
I
guess
at
the
end
of
the
day,
you
know
it's
projects
like
dot
vm
that
make
the
damn
foundation
great.
So
I
want
to
thank
you
again
for
being
on
the
show.