►
From YouTube: XAF Blazor Value Manager Discussion
Description
Click Here to Subscribe: http://xaf.life/35
Websites:
https://xafmarin.com/
https://xari.io
https://www.xafers.training/
http://xafersweekly.com/
Facebook Group
http://xaf.life/4g
Free XAF Support Hour
https://calendly.com/xari/free-xaf-support-hour
A
A
Obviously,
we
were
used
to
the
value
manager
in
windows
like
that
it
was
using
like
a
static
variable
and
we
were
using
the
web
phone
that
was
using
the
user
sessions
and
right
now
in
blazer
is
a
scope
and
the
when
we're
logging
in
the
blazer
application
is
also
a
scope.
So
there
have
been
some
few
changes
there
and
in
some
time
when
we
expected
the
value
manager
to
return
the
value,
we
have
had
some
issues
there,
but
I
saw
this
ticket
from
the
support
center
and
this
implementation.
A
I
really
like
it
about
that
gosha
provide.
Basically
we
create
a
service
that
it
will
have
a
dictionary
with
a
username
and
any
value
that
we
might.
We
want
to
pass
and
then
we
register
that
as
a
singleton,
so
yeah
everyone
will
get
an
instance
of
that
service.
Everyone
will
get
an
instance
of
that
dictionary,
but
only
the
current
user
will
access
his
key
with
the
username
and
get
his
value.
So
that's
a
simple
work
around,
but
I
think
that
we
have
like
this
is
a
new
business.
A
Really
it's
really
nice
and
I
have
honestly
changed
to
this
implementation
for
a
lot
of
things.
I
remember
jose
when
we
did
the
example
of
changing
databases
on
time
before
the
official
example
came
up
and
we
had
an
issue
with
that
value
manager
in
the
logging
in
when
we
come
back
so
at
the
end,
we
have
to
create
a
cookie
and
put
it
on
there.
B
And
that's
not
the
only
case
here
also.
We
have
one
case
when
we
implemented
a
middleware
for
because
I
was
working
with
the
people
from
developer.
Express,
I
don't
know,
I
think
it
was
russia
who
helped
me
for
that,
that
we
wanted
to
have
a
middle,
a
middleware
service,
and
we
wanted
to
access
the
value
manager
there
also
for
a
quartz
implementation,
and
they
actually
did
like
they.
As
always,
they
came
out
of
their
way
to
help
us
and
they
make
a
great
example.
B
I
don't
know
if
that
sample
is
still
valid
today,
because
we
did
in
the
really
early
days
of
sub
lasers.
So
I
wanted
to
take
a
look
to
that
because
I
remember
that
in
the
office,
like
you
know,
internal
chat.
We
were
having
a
lot
of
discussions
just
about
this
case
right.
So,
let's
put
something
together
like
and
say
like.
This
is
how
we
will
officially
work
somehow.
C
Yeah
yeah,
I
think
it
was
our
fault
to
expose
this
value
manager
ipi
many
years
ago
to
be
honest
and
yeah.
This
approach
with
custom
service
is
perfect
and
I
think
we'll
document
it
somewhere
in
the
official
documentation,
because
value
manager
is
an
internal
api
and
it
may
change
and
change
it
in
the
past.
So.
A
Well,
I'm
glad
that
we
are
not
crazy
here
then,
and
we're
going
to
the
front
implementation,
because
I
saw
that
that
tickets
wrong.
That
gotcha
gave
that
answer,
and
I
said
I
really
like
that
implementation
we're
going
to
use
it,
and
actually
we
actually
did
a
training
on
our
thing
and
saying
everybody
is
going
to
start.
This
is
the
way
to
go
from
now
on
when
we
need
to
share
a
value
that
is
only
for
that
user.
So
yeah.
Thank
you
for
that
to
the
support
for
their
stress,
as
always,
it's
great
and
actually
jose.
B
And
you,
I
think
that
the
implementation
that
gosha
shows
and
the
one
that
we're
using
at
the
moment
is
actually
the
right
way
to
go.
The
thing
is
that
we
were
so
spoiled
by
using
the
value
manager
that
was
so
easy
in
windows,
forms
and
web
forms
that
we
say
like
yeah,
we'll
buy
your
manager.
We
always
use
it
like.
We
need
to
pass
a
value
from
one
place
to
another.
B
C
Yeah
exactly
exactly-
and
you
know
it's-
this
concept
is
well
documented
by
microsoft.
When
you
create
a
new
blazer
application,
you
without
xf,
you
see
this
weather
forecast
service
by
default
and
it's
also
in
maui
applications
and
yeah.
It's
a
well-documented
concept.
So
why
try
on
a
new
excise
api.
B
There
was
one
case
denis
that
sometimes
we
want
to
to
do
the
stuff
on
the
same
way
in
all
the
platform,
because,
even
though
we
don't
use
web
forms
anymore,
that
much
we
can
use
windows
form.
So
sometimes
you
need
to
do
you
or
you
wanted
to
have
the
same
code
for
windows
forms
and
the
same
code
for
blazers,
but
now
that
we
can
use
the
dependency
injection
from
microsoft
in
windows
forms,
then
we
just
a
service.
We
fix
all
of
this.
I
guess.
A
I
think
that
what
you
say
about
we
were
like
used
to
do
it
a
certain
way.
That's
the
sacrifice,
because
one
thing
that
it
happens
to
us
a
lot
as
well-
and
this
is
a
an
example
with
the
security
system,
question
user-
we're
having
a
lot
of
criteria.
So
when
we
went
to
summary
and
we
went
to
oil
platform,
that
was
failing
and
then
it
was
used
to
change
our
thought
about
using
the
the
the
function
operator,
they
get
user
id.
So
we
get
it
the
same
way
without
having
to
use
the
security.
B
A
A
Okay
right
so
right
here
we
we
switched
from
this
implementation
that
we
had
at
all
the
time
to
this
one,
so
that
was
also
a
change
somewhere.
What
we
used
to
do,
and
now
we
have
the
other
going
everywhere.
So
I
think
that
is
also
a
way
like
you
get
used
to
do
one
thing
one
way
and
they
you
are
a
little
resistant
to
change,
that
little
part.