►
From YouTube: What’s new in Teams Toolkit for Visual Studio 2022
Description
📺 In this 15 minute developer focused demo, John shows us how to use Teams Toolkit in order to create apps for Microsoft Teams as a .NET developer. He first walks us how to get Teams Toolkit for Visual Studio, use a project template to create a new app like a Notofication Bot, a Command Bot or a Workflow Bot. In the scaffolded project, he provides a comprehensive code walkthrough and then demoes how the app works in Microsoft Teams as well.
This demo is taken from the Microsoft 365 & Power Platform weekly call – 22nd of August, 2023. Join the next call! Download recurrent invite from https://aka.ms/community/calls
✨ Presenter
John Miller (Microsoft) | @jmillerdev
💡 Learn more about the Microsoft 365 & Power Platform community
• Microsoft 365 & Power Platform Unified Sample gallery - https://aka.ms/community/samples
• Microsoft 365 & Power Platform Community in YouTube - https://aka.ms/community/videos
• Microsoft 365 & Power Platform - http://aka.ms/community/home
Sharing is caring! You are awesome! 🧡
A
Foreign
this
morning,
I'll
show
you
the
team's
toolkit
for
visual
studio
and,
if
you're
not
familiar,
the
team's
toolkit
is
our
tools
for
helping
you
develop
and
build
and
publish
and
all
sorts
of
things
that
you'll
probably
get
into
as
you
make
teams
apps
if
you're
a.net
developer
inside
of
BS.
We
also
have
these
tools
in
vs
code,
which
I've
also
jumped
on
here
and
shared
before,
but
we're
going
to
look
at
BS
today
and
see
what
we're
doing
for
net
developers.
So
let
me
get
started.
A
I'll
share
my
screen
and
show
you
some
areas
where
you
can
get
started.
So
I
have
a
couple
things
up.
First
thing:
I
want
to
show
you
is
how
do
you
even
get
the
tools
so
the
way
you
install
the
team's
toolkit
is
inside
the
vs
installer
in
the
asp.net
web
development
workload
thing.
If
you
have
that
installed,
there's
an
option
over
here
called
Microsoft
teams,
development
tools.
A
So
if
you
check
that
box
you'll
get
a
couple
megabyte
download
and
that
installs
our
extension,
so
once
you
have
that,
then
you
can
jump
back
into
vs
and
you'll
get
this
project
template.
So
this
is
the
teamstack
project,
template
and
and
create
a
new
project
and
you'll
get
a
couple
options.
So
these
are
the
templates
that
we
have
to
get.
You
started
with
a
teams
app
if
you're
not
familiar
with
a
teams
app,
you
don't
really
need
any
of
these
things,
because
a
teams
app
is
really
just
a
Json
file.
A
It
just
kind
of
defines
some
metadata
about
how
you
want
to
extend
the
team's
client.
So
those
are
things
like
if
you
want
to
embed
a
website
inside
of
teams
or
if
you
want
to
create
a
conversational
experience
using
a
bot
or
you
want
to
extend
the
chat
compose
area
with
some
kind
of
special
search
functionality
or
some
kind
of
action
to
do
something.
A
You
can
do
that
as
well
and
all
that's
expressed
inside
of
a
Json
file
and
you
point
to
the
URLs
and
things
of
these
hosted
experiences
that
run
those
and
then
there's
other
some
dependencies
that
you
need
like.
If
you're
going
to
do
a
conversational
thing,
you
might
need
a
bot
and
then
so
you
need
to
go
down
the
rabbit
hole
of
Bot
framework
and
figure
all
that
out.
So
the
team's
toolkit
tries
to
help
reduce
some
of
the
tediousness
of
the
configuration
for
those
things.
A
So
you
can
just
jump
right
into
your
code
and
focus
more
on
your
app.
So
we
have
these
templates
to
jumpstart
you
and
those
experiences,
and
so
we've
kind
of
opinionated
where
how
you
can
get
started,
but
it's
all
pretty
flexible.
If
you
want
to
change
it
later,
so,
for
example,
so
these
templates
are
based
on
scenarios
that
we've
seen
folks
start
with.
A
So
you
want
to
show
some
type
of
little
UI
inside
of
teams
with
maybe
links
or
text
or
clickable
things,
whatever
you,
whatever
you
want
to
do,
then
you
can
use
a
notification
bot
template
to
get
started
with
that
or
if
you
want
to
kind
of
do
it
the
reverse
way
and
type
something
in
the
chat
and
then
execute
something
in
a
remote.
You
know
internal
process
somewhere
you
can
do
a
command
bot,
so
this
helps
you
set
up
with
a
team's
chat
command
and
then
you
can
run
it.
A
A
If
you
want
to
do
something
like
a
q,
a
or
like
a
ticketing
system,
or
something
like
that,
you
want
to
show
an
Adaptive
card
with
some
kind
of
action
that
someone
can
do
or
people
in
a
chat
can
do
and
then
a
tab
is
an
embedded
website
and
then
a
message
extension
is
a
way
to
exp,
extend
the
chat,
compose
area
with
I.
Think
this
example
does
both.
It
does
both
a
search
based
message
extension,
so
you
can
do
a
custom
search.
A
I
think
the
example
shows
how
to
query
npm
and
and
show
like
a
list
of
the
packages
inside
of
teams,
and
then
it
pastes
an
Adaptive
card
with
you
know,
whatever
you
want
to
customize
that
so
I
already
to
save
some
time.
I
already
created
some
of
these,
so
we
don't
have
to
wait
for
vs
to
scaffold
this
stuff,
so
I'll
just
open.
This
is
I,
think
a
workflow
bot
template.
A
A
Oh
okay!
Okay,
great
thanks!
Bessa!
What
you
get
by
default!
Is
you
get
it
dot
net
project
I
think
this
is
a
web
API
project
and
we
have
some
setup
in
here
for
the
teams
related
stuff.
So
there's
some
configuration
for
it
since
this
uses
a
bot
there's
some
configuration
using
the
bot
framework
SDK.
So
all
of
that's
in
here
there's
also
for
net
developers.
A
We
have
an
SDK
called
the
teamsfx
SDK,
and
this
is
some
higher
level
abstractions
built
on
top
of
the
bodicedk
to
make
some
of
these
scenarios
a
little
easier
like
commands
and
responding
with
adaptive
cards.
There's
a
lot
of
boilerplate
needed
to
do
those
things.
So
we
have
some
abstractions
in
our
SDK
that
you
can
optionally
use
to
make
these
scenarios
a
little
easier.
So
I'll
give
you
an
example
of
that.
A
For
example,
we
have
this
interface
for
implementing
handling
commands,
so
you
can
just
Define
whatever
the
trigger
is
for
that.
In
this
case
it's
do
stuff
and
this
one
is
used
as
a
response
to
an
Adaptive
card
to
create
kind
of
a
sequence
of
actions
and
I'll
show
you
what
that
looks
like
in
a
second
and
then
you
can
Define
how
you
want
to
respond
with
that
adaptive
card.
A
In
this
case,
it's
going
to
replace
the
card
instead
of
posting
a
new
one,
and
then
it's
going
to
send
the
actual
card
which
is
handled
here
and
then
it
uses
the
Adaptive
card
SDK.
So
there's
a.net
SDK.
For
that
as
well,
so
you
can
Define
your
adaptive
card
with
Json,
and
then
it
has
a
bunch
of
dot
net
classes
to
wrap
all
that.
So
let
me
show
you
what
that
looks
like
to
do
this
to
debug
this
right
from
vs.
A
You
do
have
to
run
some
type
of
tunnel,
because
this
is
a
Azure
bot
framework
needs
a
way
to
communicate
between
teams
and
itself,
and
then
your
local
machine,
so
new
in
the
team
still
kit
for
17.7
in
BS
is
we
have
support
for
Dev
tunnels.
So
you
can,
if
you
haven't
seen
this
yet
you
can
create
tunnels
directly
inside
vs,
for
not
just
for
teams
toolkit
for
anything,
so
I've
created
one
I've
just
named
it
teamstev
here
and
I've
already
selected
it.
So
when
I
have
this
selected,
our
extension
will
have
this
menu
here.
A
There's
a
manifest
already
here
and
there's
all
this
information
all
this
metadata
about
how
I've
wanted
to
extend
the
platform-
and
you
don't
have
to
get
into
all
this,
but
eventually
you
probably
will
learn
it
and
you
can
go
in
and
customize
it
as
you
need
to.
But
teams
needs
to
know
about
this.
So
the
way
you
do
that
with
with
vs
is
use
this
menu
command
for
now.
So
you
just
prepare
the
app
dependencies
and
you
sign
in
with
an
account.
So
this
would
be
your
M365
account.
A
This
is
the
tenant
where
you
want
to
run
this
and
I'm
using
a
Dev
program
account.
So
if
you
can't
run
custom
maps
inside
of
your
tenant,
then
we
recommend
you
use
a
Dev
program
account.
So
it's
a
free
account
to
get
your
own
subscription,
your
own
developer,
identity
and
kind
of
a
sandboxed
environment
to
run
these
apps,
and
when
you
click
this,
the
toolkit
is
going
to
run
through
a
bunch
of
tasks
to
set
up
all
the
dependencies
needed
for
the
platforms.
A
This
is
registering
a
new
app
ID
for
teams
and
in
this
case
it's
also
creating
an
Azure
ID
application
for
the
bot,
which
is
required
for
bot
framework
to
work
and
and
a
bunch
of
other
steps
and
all
of
those
steps
are
expressed
in
this
yaml
file.
But
so,
if
I
open,
this
I
can
go
through
and
the
toolkit
the
output
menu
here
jumped
up
and
showed.
So
you
can
see
this
actually
shows
all
the
things
it
did.
A
So
it
goes
through
all
these
steps
and
all
these
steps
are
expressed
inside
of
this
yaml
file.
So
something
new
that
we
did
in
the
past
year
is
all
of
the
toolkit
actions,
so
everything
that
your
project
needs
to
run
and
do
whenever
you're
either
running
locally
inside
of
vs
or
if
you
want
to
use
this
as
a
provision
and
deployment
solution,
you
can
also
Express
those
in
this
other
file.
So
there's
two
yaml
files,
one
for
your
local
kind
of
setup
and
one
for
your
remote
and
all
the
actions
are
expressed
here.
A
A
There's
a
provision
step
here
and
this
you
can
think
of
this
like
a
task
Runner,
something
you
know,
I
think
I,
most
think
of
it
like
Gulp
or
something
like
that
in
other
projects
could
think
of
like
Ms,
build
I
guess.
But
basically
you
have
a
bunch
of
these.
What
we
call
actions-
and
it
looks
a
lot
like
a
GitHub
actions
file
or
an
Azure
devops
pipeline
file,
and
we
have
all
these
predefined
kind
of
actions
to
do.
A
Teams
related
stuff,
so
we've
tuned
them
all
for
all
the
things
that
you
would
need
to
do
for
teamstev.
You
can
mix
and
match
whatever
you
want.
These
task
Runners
to
do,
and
so
I'm
going
to
create
a
teams
app
and
save
that
as
an
environment
variable
and
just
go
through
all
the
steps
I
need
so
I
need
a
teams.
A
App
I
need
a
bot
and
a
I
need
an
aad
for
my
bot
and
then
there's
some
other
specific
stuff
in
here
about
just
putting
it
into
app
development
Json
file
to
make
it
a
little
easier
to
work
with
net
projects.
So
we
have
an
action
to
do
that
because
we
found
developers
often
want
to
do
that
kind
of
stuff
and
then
create
a
bot
framework
registration.
So
this
is
normally
you'd
have
to
jump
through
a
bunch
of
portals.
A
To
do
this,
you
have
to
go
to
the
bot
framework
portal
or
or
the
Azure
portal,
and
also
the
team's
developer
portal
and
create
all
this
stuff
manually
and
then
paste
it
into
these
files.
But
instead
you
can
automate
all
this
with
just
these
tasks.
All
that
stuff,
all
the
outputs
of
these
get
saved
in
environment
files.
So
if
I
look
at
my
local
environment
file,
here's
all
the
outputs
so
when
I
ran
that
prepare
command
I
get
my
app
ID,
my
tenant
ID,
all
this
stuff.
A
Here's
here's
the
tunnel,
URL
I,
created
all
that
gets
saved
as
an
environment
file.
If
I
don't
want
to
use
teams
toolkit
to
do
a
piece
of
this
I
can
I
can
just
delete
some
of
this
or
comment
it
out.
I
could
just
delete
these
and
say:
hey
I,
don't
want
to
create
a
teams.
I've
already
have
an
app
ID.
A
My
admin
gave
me
one,
that's
all
configured
and
been
blessed
and
everything
I
could
just
delete
this
or
I
can
just
go
into
the
environment
file
and
just
paste
it
in
here
and
then
what
this
helps
you
do
is
it
helps.
You
have
a
single
manifest
file
that
you
can
keep,
which
is
here
and
then
use
these
environment
variables
to
help
with
replacement.
A
So
the
toolkit
can
help
you
manage
like
if
you
want
to
create
a
local
one
and
then
maybe
you
want
to
run
this
in
a
QA
or
staging
or
production
and
Dev
all
sorts
of
other
remote
environments.
You
can
have
one
manifest
file
and
just
use
replacement
strings
like
this,
and
then
it
just
reads
through
the
environment
files.
You
just
name
them.
However,
you
want
and
those
are
kind
of,
like
your
environments,
so
toolkit
helps
you
manage
that.
A
Okay,
so
now
that's
running
and
I've
already
ran
prepare.
So
teams
knows
about
my
app
I
got
my
app
IDs
and
everything
we
can
just
hit
deep
start
debugging
and
it
will
launch
teams
in
a
browser
for
the
for
the
tenant,
for
the
account
that
I
signed
in
with
and
it'll
go
right
to
the
install
app
window.
So
we'll
wait
for
that
to
run
and
let
me
grab
the
browser
and
bring
that
over
I
think
it's
going
to
pop
up
a
new
browser
for
me.
A
A
All
right,
so
teams
is
it's
already
logged
me
in.
If
you
do
this,
the
first
time
you
you'll
probably
get
a
login
screen.
I've
already
done
this,
so
it's
already
remembered
my
identity
for
teams,
so
I'll
go
ahead
and
add
my
app
and
then
it
will
jump
right
over
and
I've
already
ran
this
app
a
couple
times.
So
this
template
just
defines
a
single
command,
so
you
just
type
in
hello
world
and
let
me
make
sure
I
don't
know
if
it
matters
but
go
ahead.
A
A
A
So
there's
no
new
card
here
and
it
just
updated
it
to
a
new
card
that,
just
as
an
act
says,
hey
you
click
the
button,
so
you
can
imagine
you
can
start
chaining
these
things
and
create
some
type
of
workflow,
whether
it's
an
approval
system
or
ticketing
system,
or
something
like
that
and
you
can
customize
that
all
with
the
Adaptive
card
SDK.
However,
you
want
to
display
these
things.
A
So
that's
what
the
toolkit
does
for
you
places
to
get
started.
Let
me
jump
over
here
in
the
docs.
You
can
get
started
here.
We
have
a
section
for
vs
code
which
is
over
here
but
make
sure
you're
in
the
vs
section
and
then
you
can
go
through,
and
this
gives
a
good
example
of
kind
of
what
what
I
talked
about.
These
are
kind
of
the
opinions
we
express
of
you
create
a
project.
A
You
have
some
development
and
then
you
can
optionally
choose
to
use
the
tools
to
provision
and
deploy
we
didn't
get
into
that
here.
But
we
do
scaffold
you
a
bunch
of
bicep
files,
so
you
can
host
these
in
Azure
very
easily
and
the
toolkit
has
commands
to
help
you
with
that,
and
let
me
jump
over
here.
Also,
we
have
a
lot
of
the
project
is
open
source
on
GitHub,
so
the
good
place
to
file
issues.
You
can
start
a
discussion.
A
The
vs
extension
is
not
open
source,
but
the
rest
of
the
project
is
so
you
can
take
a
look
at
here
like
the
sdks
are
open
source.
The
samples
are
all
available.
The
templates
are
in
here
for
net
and
for
JavaScript
and
typescript,
and
this
is
where
all
the
this
is,
where
all
the
planning
and
communication
and
issues
happen
so
feel
free
to
jump
in
there.
If
you
have
any
questions
and
I
think
that's
my
time.