.Net Foundation .Net Community Standups, 23 Jul 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: ASP.NET Community Standup - July 23rd 2019 - ASP.NET Core 3.0 Preview 7

Description

Join members from the ASP.NET teams for our community standup covering great community contributions for ASP.NET, ASP.NET Core, and more.

Community links for this week: https://www.theurlist.com/aspnet-standup-2019-07-23

A

Magical things happen: the internet sends bits around there. It is so yes, look at all that.

A

Hooray. Welcome to the asp net community stand up, yeah, yeah, I'm, doing good so yeah. So we have the preview. 7 show we got Brady. We got dan Roth on it's exciting yeah, just to be sure that all the technical stuff worked. We started the stream 15 minutes early, and so we've already got tons of people that have been watching and chatting away. So that's exciting.

A

I cannot wait to see all the cool stuff you're gonna show off so I'm gonna jump right into the community links to get those done so I'm gonna share my screen here. Let.

B

A

Get the teams for you there.

B

A

Okeydoke, excellent, ok, so this one's fun, this is from Andrew Luck he's been doing a serious. This is part 5 of this series. This is a really interesting topic, I think. So the problem is that you have these IDs that are often integers and it's very easy to write a method that say it takes in a I, don't know, say a user ID and an order ID and a product ID and if you've typed those in the wrong order, they're all intz and so there's no way to validate.

A

What's happening, and you know be nice if you could actually on a class, you could say this: ID is a product ID.

A

Unfortunately, it's not really super easy to do, especially if you worry about things like Jason, B, serialization and stuff, like that, so Andrew had gone through and he'd created some things with. You know like some some snippets and- and you know ways that you could like you know you could do all this, but it was a decent amount of code and so then, what's really cool is he's actually created a strongly typed ID nougat package and using using you know, Roslyn magic. It's actually doing the stuff behind scenes. So here I've got you know.

A

I've got a strongly typed ID attribute on my food ID class and it can actually go through and like validate exactly what you know. It can validate the ideas and stuff so behind the scenes, it's generating code, but I don't have to see it and it's um you know it's it's automatically on builds generating the correct code for that. This also handles out the the Jason D serialization stuff, so Jason converters and all that so I think this is really neat. I. Really like this idea and again this gives you the whole.

A

You know ability to validate that you've got you know if I've got a product and I've got a product. Id I can behind-the-scenes. My entity framework model is still just saving it to it to an integer field, but it's I'm getting that kind of build time, validation. So.

C

It's all done at Build time and with the code. It's like code, getting a bunch of stuff.

A

It's Co Jenny, wait, yeah, that's not wonderful, I love this and so there's stuff, potentially on the way for c-sharp with record types and stuff. But it's like I forget, even if it's approved or if it's a way out so some other languages have this, where you can have like opaque types. I believe is that the feature name? We don't have that in c-sharp yeah. This kind of gives you a way to simulate that okay.

C

Sort of metaprogramming the compiler is that what kind of what this is doing like it's going in and saying, let me let me extend Roslyn a little bit. Yeah.

A

C

A

It's and it's using this dotnet cogent, and so he also points out this dotnet CLI to a reference being phased out in core 3 and I'm, not sure exactly what that is.

A

I haven't looked into that more, but that is also something to be aware of, but so this this NuGet package is just generating the stuff for you and he's got some extra configuration options for you too, like if you want a Jason converter and stuff so meets ok ahead, absolute champ of blogging lately, so he's finished up his 26, a through Z series of asp, net core and he's he's got this ebook available. This is actually really cool too, because he's got this behind-the-scenes.

A

This whole, like worker service, that takes all his blog posts and generates this ebook. So that's you know. That's pretty neat too he's actually generating this this this ebook too, so anyhow, great stuff love it- and this is he's been doing this thing where he's he's been digging into all these different features. You know like access for XML or you know, K is for Kestrel or whatever, and then he's um he's an.

B

Updated them to you.

A

Sorry, not cool thanks, good, alright, no worries, okay, great okay, Jim Bach! This is cool this. This post in Jim box on the live stream too, which is neat so here he's talking about the asp net core request type line. This is part one of the series and here he's looking at receiving requests. I like this just kind of how he's describing the different options. Server, implementations and you know what you can do. Castrol out of process in process love his diagrams here and then, of course, a handy TL DR down at the bottom.

A

Talking about you know, what's what are your options and and when you'd pick, which so nice post I'm looking forward to reading the rest of the series? Okay, this is cool scott addy recently posted this on on twitter, so I followed through to read up on this. So there's been this HTTP repple, here's I guess the actual release of it. There's documentation of the HTTP repple. You know in the docs, and also you know it's. It's moved I believe before it was in the labs or something person yeah okay.

A

So this is moved over into the HTTP into the asp net org right.

B

Yeah anything else it has its own repo now and we're gonna be adding some stuff to it. We have a lot of ideas on how to make use of this, maybe from the s or like an f5 type of experience. If you have any thoughts on that feel free to submit us some issues and give us some ideas on either how you've used it or features that you want in very.

A

Cool all right, so this is a cool one Brady that you sent over to me. Shoji Fez, written up this real-time blazer tic-tac-toe with bots and multiplayer, and signal R, and even even when you load this page, it does some neat little. That's.

B

A

Animation, stuff, yeah, so yeah, so you sent me this link. I mean it looks pretty straightforward. It looks really interesting anything else you wanted to add on here. I.

B

Mean I like this, because Glenn and I had worked on a demo for a dev intersection and right before it we had started. You know it was. It was a game demo and we kind of started working on it.

B

Thinking we would do signal R and then we kind of went messaging nuts and we started using service bus and a bunch of other stuff, and we talked about the other day and review this article, and we like this better, so I think I might read architect a little bit and kind of do the player versus player components, but I really like this sample a lot I would definitely take a peek at it.

B

I'd like to see this put in a kubernetes cluster and like have other BOTS, so maybe you know bots, you know you could write your own bot and you know, come up with your own. Algorithm to you know, beat beat the human so to speak, so see if we could actually make this into some sort of a sort of a viral game. I'd love to I'd love, to talk to TIA and see if we could do something with it very.

A

Cool had a question in the chat about posting the link, so I'll post all the links for these right after we go through them all, so yep cool all right, Edie Charbonneau sent me this. This is really neat he's got. um This is a blazer QuickStart guide. These are all just short little five ish minute little kind of intro things. So just very quick start, yeah, yeah, so tons of great content from Edie lately on blazer stuff.

A

He does a weekly stream on Twitch and just like kind of a community stand up style on Fridays, just focused on blazer, so lots of great stuff.

A

Well: okay, jeff fretts, speaking of the twitching, so Jeff went through two of our workshops, and so these were all live on Twitch full-day workshops, and then he posted the video for these. So this one is the blazing pizza walkthrough of the blazing pizza tutorial, yeah yeah. You did and I remember.

C

A

I loved the look on his face here. I think this may be due to reading some of these different. You know some of the pizza descriptions, especially the BRIT, there's some odd options here, yeah yeah, so this is cool and then also here he did the asp net core to to workshop, and so that is that is neat. If you would like to you know we do these workshops at conferences, they're, available online they're, actually in this presentation, stat foundation.org.

A

If you want to go through them yourself, if you'd like a video tutorial and then to follow along with the code, you can do that. So so that's all right here and yeah again, one other thing just by the way, this asp net core app workshop. The live version of this is because that's the release version, but there is a branch with 300.

A

So if you want to go through and do the trio version of this, that's out there it's still kind of in process, but but there is a version of it and damien and and david did go through this at NDC OWSLA all right now the excitement asp net core or excuse me dotnet core 3, o preview, 7.

A

And I confess to have not read this post yet because you sent me the link to it like about a second before we went.

C

A

Exciting so exciting, so I all these links I'm going to this is this I will post the link for this, and this has all the links where the show and I will stop with the sharing, and you can talk about dotnet core preview 7, once I find teams come on teams there we go and stop sharing. Ok,.

B

There we go back.

A

Over to you, let.

B

Me get it, you got teams up, ok, good.

B

Daniel Jago.

C

Me my turn. Your.

B

C

Right so actually, let's, let's look I, can share my screen right. I can do that photo.

B

Sharing thing I.

C

Can do that just yeah this thing would that work. It.

B

Did it's on the when.

C

People see my screen: okay, I'm pulling up the dotnet blog Ajay I, haven't gone through in detail as well, but I believe I'm told that there is a bunch of Awesomeness in here about like app size improvements ah yeah this one and, of course, for yourself. There's like two blog posts. Oh that's the that's the only framework one okay, so we've got the dotnet choreo preview, seven blog post and the EF core blog post.

C

That just came out as well, but I'm told that we did a whole bunch of work to like reduce the app size and add.

B

Event; counters, which is exciting, and that.

C

Is all in Donna core sdk size improvements? So let's see what we got here so installer size change, 440, kilobyte, that's nuts! That's a little, not much smaller! This one is fifty five megabytes, so 32% small. So this is just like the size of the SDK. When you go to install it, I think a lot of that work was that we removed a lot of these like offline package stores that were in here is that right thanks.

B

C

Way: script: by removing the purpose-built packs of various kinds in previous versions, we constructed the SDK from Mooga package, which included many artifacts that were not required and wasted a lot of space. You can see how we calculated these file sizes and the size improvement, gist yeah, so I think the reason why this is exciting and good is because this presumably affects the size of our docker images, all right, yeah so like these, like the Debian docker image, now is like half the size. That's.

B

C

The Alpine one like Alpine is like a tiny, tiny, Linux, Linux distribution right like isn't it just like, like under 10, Meg's or something, but because of all the stuff that we had to bring in with the SDK like it just gets bloated, even though you're you're building on a really time out tiny OS, but we get a huge size improvement there. So this should make it easier to like move your your containers around.

C

You know copy things around, and you have a lot just a lot less stuff that you're having to worry about like what is what is on your your docker images, so that's kind of cool, so the the size improvements have landed in this release. So that's they just want to highlight that. Let's go look at the a spinet blog and see what's new on the asp net side.

C

So so a couple things that you're going to want to know about about preview, 7, so preview 7, is it's actually now in the box, with visual studio so previously to this release. If you installed on a core 3, oh you were going to install Visual Studio and you, of course, would be installing the preview channel of Visual Studio, because you you need the latest Visual Studio tooling, to take advantage of all the stuff. That's in dotnet, core 3. Oh, there are in fact features that that won't actually work. Unless you use the preview channel.

C

We get quite a few issue reports from people who have tripped over that and tried to use Nick or 3 Oh with like the stable release official studio 2019. That's that's not a thing quite yet, but with this next update to Visual, Studio and I believe the update themselves actually because I've been watching my no no definitely not rebooting right now, I've I've been watching my Visual Studio install or waiting for bits to come to come in for the next update.

C

A Visual, Studio I believe visual studio, 16 I have 16 one installed right now, but I believe visual studio 16 to update to the 2019 is landing like every minute like it should. It should show up in the stable channel. You can see that preview. 4 of 16 2 is is showing up in my preview channel right now, but later today, I'm told that this will actually update to 16 3 preview 1 and that's actually, the version of Visual Studio that you're gonna want to use with this preview 7 release of dotnet core 3.

C

Oh, it looks like.

B

C

Quite landed yet I just installed 3 before and I'm, not gonna reboot, because that would be worrisome to do that on the live stream. But you're gonna want to make sure that you get 16 3 preview 1, which should be in the preview channel any minute now, 16 to the stable release, just should be going out any minute. Well, about the same, the same time and 16/3, that's the release that we will support without NIC or three.

C

Oh, so that's why you're gonna want to be on that train, and the great news is: is that dotnet course Rio will actually be included in that Visual Studio release? If you've got 16.3, then you have NIC or three oh and you're good to go and you've got in fact, you'll have a dotnet course. Rio version, that's aligned with that BS version.

C

This is one of the reasons why the schedule for dotnet course Rio will actually accelerate a little bit from now to the end of the release, we're targeting September for the final release of dotnet core 3. Oh and all the updates in between are actually aligned, visual studio and dotnet core 300 updates.

C

So you know you'll get up doing a preview one of sixteen three hopefully today, and that will carry preview, seven Nick or three up and when preview eight comes out for dotnet core three, oh, that will be carried with preview two of sixteen three, so those two things are now locked together at the hip and 16 3 will be the stable version of Visual Studio that you'll use with dotnet core 3. Oh, that makes sense everyone.

C

That's that's what you're going to want to get if you're, not on the preview channel today, make sure you get on the preview channel, so they can get all the the great new features in dotnet core 3. Oh, so, ok! So what else? What is actually new? Then? In this release we are getting closer to the end of the dotnet core 3, oh train I mean we've only got about two more months right until the release goes out, so we're starting to dial back from. You know major feature, work and moving more towards stabilization polish.

C

You know making sure that everything is production, ready and ready to go by the time we ship in September. So you may see that the these releases are don't have quite as much in terms of like brand-new features that we've been pushing out. It's more tweaks and updates that are happening in the release. So a couple things that we did so, first of all, if you're a blazer user, which I hope many of you are, there is a blazer update.

C

That is that shipped with, alongside this release, there's support for blazer server, apps, that's of course, in the box with Nick or three oh and there's updates there and then there's the support for blazer webassembly, apps or clients. I blazer apps, as we've been we've been calling them that ships out a band on new get as a new get package now in the past.

C

If you wanted to get the latest greatest blazer webassembly templates into visual studio, you not only had to install the SDK, you also had to install a visual studio extension to get those templates into the S.

C

You no longer need to do that, which is pretty cool so and this this is actually I, think a pretty awesome thing not just for blazer but for the dotnet ecosystem in general, we've always had a mechanism at the command line where you can create template packs as a nougat package and install them on the command line in order to get templates available from the CLI. That's what we've been doing with blazer for a while and lots of people have been shipping templates that way.

C

But then, if you wanted to make those templates available in Visual Studio, you had to do extra work. You had to create a visual studio extension so that visual studio knew about those templates. Visual studio didn't just like automatically figure out that oh there's, some templates on the command line I should expose those as well. You had to do extra work to create an extension with this update to visual studio, 16 3 preview 1.

C

There is now functionality in BS to detect new templates that are installed from the command line, so for the new blazer templates, it's sufficient just to install them from the command line and you'll get those templates now in visual studio. So that's that's pretty cool. If you're a template author, you have your own template packs online. Hopefully there'll be a feature that you can also leverage that people can get your templates not only on the command line, but also in visual studio by just running one command line, command and.

A

One minor thing from the chat there: it looks like there's an extra dot at the end of that dotnet new line, yeah.

C

That that someone put a period there and that shouldn't be there I will get that fixed, no problem. Thank you for pointing that out.

C

So yeah so just copy everything, except for that last time, so that'll get you set up, then, with all the bits, both on the command lines and in yes, the upgrade of existing projects from if you're messing around the preview, 6 and you're going to preview 7, it's actually pretty lightweight this time around. Not a lot of making changes between these two preview releases. Pretty much you're going to be updating package for references for those very few cases where you still have those.

C

You know one of the ways that we got that huge size savings in Nikora 300 on the sdk size that we saw previously was we moved to this idea of a framework reference where all of a snit core is now just one big framework along with all the dotnet core stuff that you just get reference implicitly by the fact that you're using the.net core SDK? So it should be pretty pretty easy to get updated. There are some more changes that are coming in preview 8, particularly in the blazer space.

C

So that's just something to be aware of. We are doing our API reviews right now, which means that we are going through all the api's that we've generated over the like year and a half of blazer experimental development and just making sure that these are the api's that we actually want to ship with. There are things some things that are that are moving around some some package names got shifted around as part of that that work that will be coming in preview 8. So just you know heads up on that.

C

If you are trying to use blazer in any sort of production scenarios today, just be ready to that there will be some some turn that you'll have to react to for preview 8. But after that we should be pretty much locked down as a concerns of api's and having them be stable. Ok, so this is kind of cool.

C

So if you're in Visual, Studio and I have a because it's not in the preview channel quite yet and I don't want to restart I, do have an internal preview build of Visual Studio installed in my machine, so I'm going to do file new project here. This is the internal build of 16.3 preview. One one thing that's really cool now is when you look at the templates and I have a couple filters here. Let me let me remove the project type filter.

C

Let's go look at all project types, so this is the file new project dialog, which surfaces a nice long list of all the templates that are available in the past. If you wanted to do a new, a snit core template, what you do would select a Smith core web app template and click Next, and then you say what template name.

C

You want it and then it would pop you into this additional dialog from him in a second that had all the a sment core specific templates in there their own list- and this was fine like the they were this. This enabled us do a bunch of additional tooling around the estimate, core templates like having all these additional checkboxes and authentication options which created uh you know some some some easier ways to get started. The downside of having this additional UI is.

C

It means that, like, if you were trying to let's say you, wanted to create a blazer app. A lot of people would go into this. You know file new, create new project dialog and the Atty blazer here, and nothing would show up, but one of the things that we've done in 16.3 is: we've now created placeholder templates in this UI, so that all the a smith core templates now do show up here at least most of them do the ones the common ones in the future. We expect to get them all to show up.

C

So if you want to create a blazer wrap, it now shows up in the top level dialog. If you click next, it will still show you that additional dialogue, but it'll be filtered to just the the the blazer templates get up and going so that's kind of fun. So that's not just for blazer, but also like here see the G RPC template shows up here. Worker service I believe also shows up here, yeah those who work or surface template for doing back-end services. All those things are now surfaced in the create new project. Dialog.

C

Were you saying some braids II? Do you have something to add to that I.

B

Just wanted you type worker, that's all.

C

We gotta get that one at it, so I think I. Think Web API will only highlight yeah like this uh basement core template. So that's one. We still need to add a blazer G RPC worker they're, all there. Alright. What.

B

C

Going back to the blog post, okay yeah, so we made some cleanup to the web templates, and you know part of this is a common source of feedback that we get with our template work. Is we always have this tension right between wanting our project templates to be really great sample applications like showing you how to use new features, how to get functionality into your app? How to get things done so we often will add features to the templates. That add.

C

You know some more code, some more complexity, but you know they're cool, and so we want to make them really easy to consume. At the same time, there's a bunch of people who are just like one, a blank slate: they SWANA create a project template and then the features that they want to the template and a lot of times with the way we author templates. They end up having to delete a lot of code and remove things that they don't actually need.

C

So we do have, of course, the empty template, which is like a really blank slate has like nothing in it for web app templates. We decided to do a little bit more cleanup. Let me go ahead and create one and we'll take a look at some of the things that we've basically removed from the template, so that the so that it's simpler one thing that we decided to go ahead and simplify. So if we look in the layout file before for all the like your script, references and your you know static assets.

C

We used to have a bunch of infrastructure in here for setting up using a CDN for when you're running in production, but then using local files in your app when you're in development, and they even had complicated stuff where it would, if the CDN wasn't there, there were fallback scripts and all this stuff, we've decided to simplify that and just say not like we're. Just gonna have the the static assets linked to in your in your application.

C

If you want the infrastructure for having the CDN s used when you're in production, having all the fallback script, we'll have samples and docks to help you set that up, so this got simplified quite a bit. The other thing that got simplified is before we used to have a bunch of code in the templates that we added right around the time that gdpr became a very relevant concern for a bunch of customers, GDP arm courses, a bunch of regulations around managing the privacy of your applications, users.

C

We had added a bunch of code to the template to help people with those concerns. Like we added the cookie consent policy code to the template for you and a corresponding UI, we decided to go ahead and remove that code from the template by defaults, but we will have samples and docs if you want to add it back. The features are still there. The underlying framework infrastructure is still there, but we just wanted to clean up the code and make it a lot simpler.

C

So that's why there's now quite a bit less stuff sitting in your startup class, so simplified web app templates.

A

Is that is that something that like customers are asking for then you're, like hey, there's too much clutter in here? Oh yeah,.

C

The common way this comes up is customers will tell us about all the code that they delete as soon as they create a new project. So.

B

C

New project and then they'll delete a bunch of stuff for us at like loss program managers at Microsoft. The tension is always well. We want those features there because it makes it really easy to demo. Alright, like you just do.

B

C

And they're all there and you can show all these cool new things without having to do any work at all, but for folks that are down in the trenches actually trying to write apps. They tell us pretty regularly that a lot of the code that we put them templates, they just delete so we're trying to make their lives a little easier since they're, the ones that are really using our product on a day to day basis the basis that get their job done. I wonder.

A

If we should have a like template or I, don't know like a either a template or just like a project, a demo project to clone that has those like standard features in there. You.

C

A

Just we have everything in the kitchen sink template. That's like here.

C

But a little bit more, the pretty bells and we'd like the demo model at the store right, the fancy car, that's like in the front of the parking lot that they try to. They want you to.

B

C

About yeah yeah I am we have talked about that as well. That's certainly a possibility, and especially now that it's so easy to author template packs that can then be made to show up in visual studio. It should be trivial to do like we could. Just we could just create a new get package that has that anyone could really do it with the demo variants that they really like I'll share them on you get anyone can install them on the command line, and then they should show up in visual studio and.

B

Then one other thing that we've talked about doing is creating an experience where it's not just at file new project. You can actually add this stuff later on, maybe like add puzzle pieces to your application after you've already started coding. So if I want to add logger into styles in logger, wherever I need it so forth, and so on so yeah.

C

Yeah we've started doing some of that already like.

B

C

Identity, we added the identity scaffold or for folks that want.

B

C

Identity support to their applications. After the fact you created a project and they're like oh darn, I needed identity in this app and I forgot to do it. Well, you can just scaffold it in so we use scaffolding quite a bit for features like that, and we can certainly do more functionality. That way like you could imagine. Maybe scaffolding in the cookie consents UI. Those things are certainly possible, but.

B

C

Guys think it, but for folks that are on call like take a look at the new templates like we'd love, to hear more feedback about what things do you think are useful to have in the template by default and what things do you think are just honestly noise and you would be happier if they were just removed and.

B

If almost like a class.

A

B

About that yep.

A

Okay, well we're talking about things: I always turn on and change, and you know what I mean features and stuff lip man. There's the lip man like dependencies, Fiat lip man I was like that's one of the first things. I do in a new project to switch over from those like direct dependencies to managing using Lib man. Is that something that you think is always going to be like a Doc's kind of thing, or is that going to be something that the templates would use? That's.

B

Actually, a great question around the use of we recently upgraded a site we'll talk about that later in the show, but what's it called the client-side power, so you know projects that you have to have Bower or they have Lib man or vice versa. How do you you know? You know? How do you upgrade from Bower to other stuff I'd like to have something easier to do there and Littman's also sort of complex with certain package names like angular asp, net microsoft, when there's an organization.

C

B

Think I think if there is a trailing at sign, so if is for at asp net whack signal or at next I think there was an issue that I saw on github, but that but I know the teams working on it. So that's.

C

B

Ongoing thing, but you can always go to the command-line limit. It's got a great command line. Experience too you.

C

Know I, we have absolutely considered to put it just putting Libman in the templates by default there there there are some really great things to lumen does really well, and there are some things that unfortunately make Libman a little difficult for us to make the default experience right now, like I think one of the issues that we hit was like the default provider that Libman used didn't support preview packages so like if we had like a preview version of the signal.

C

Our client, for example, that you needed to acquire the default configuration of Lehman wasn't wasn't friendly to dealing with reviews there. There was just some some rough edges that I think still just need to be. You know, polished before Lehman can become a thing, that's just always there and by default. But you know it's it's a it's. It's we listen to the community. If the majority of our customers told us that no no we're using live man, we love it. Can you just? Please just add it for me and that would make my life easier.

C

That would be absolutely be something we consider right now. I think we find that it's still a select audience. That's that's using that man and it finds a lot of value in it and for other people. That's there they're setting up other. You know full client-side, build pipelines or my installing node in NPM and all those things. So it's a bit of a mix. It could be an option. That's that's another possibility where you, if you want it, we could add it all. Those things are possible.

C

I think there's still those couple things that we need to follow up with the libman team on just to make sure the experience is really good right, cool.

B

If you have any feedback there, they're definitely listening on github, we were engaged in a conversation with them the other day with a customer. So if there's definitely a lot of listening going on, so please keep it. Keep the feedback coming. Yep.

C

Cool okay, so things that are new in the blazer world. If you're messing around with blazer, we did add a couple features in this release. One is support for attribute splatting what is attribute splatting?

C

Well, let's say you have a component components and blazer represented with elements, and you want to be able to capture not only the explicit parameters that you've defined on the component, but you also want to capture any additional attributes that were added to that that component element and then in your component, rendering you want to have a way to take those captured, attributes and splat them wherever they should go in the the rendered output.

C

So for an example would be, we actually have components built into blazer that need this feature like we have a bunch of components around doing forms, validation like we have an input, text, component and I, think input select and those types of things. Those are components that, under the covers, are rendering normal HTML input, elements and it'd be really great. If you could, you know pass in any additional attributes that are relevant for the rendered input like you want to specify the placeholder or other things like that attributes.

C

Flatting is a core piece of infrastructure to the Blazer component model that now enables that. So the way this works to capture all of the additional attributes that are defined on your component, you define a special parameter in your component that has this capture.

C

Unmatched attributes equals true property set, and then this dictionary will get populated with all the additional attributes that were passed, we're we're basically written on the component element when it was used and then, when you want to use these attributes and render them onto the component output, we've added a new razor directive, the app attributes with an S directive, and that's a way that you can then specify where you want that content to go, and this looks dude. This looks like not yeah yeah here.

C

This is use Eclipse, so at the top, when you, after you've, captured the dictionary on your input, then you use that attributes, and this was where all those attributes will go. It is, it is ordered, so, like will basically look at the the attributes um left to right. So if you had, for example, a type attribute in the additional set of attributes that were passed in to this component, but then you know here, the component is also specifying itself what tech of what type attribute it wants. Then the last one wins.

C

So this one do this one would would override. So that's a way that you can now have components that take in additional attributes that get rendered in the output.

C

That makes sense yes, okay and then for data binding in Blaser, we've historically only supported a fairly limited set of types. You could basically I, think I think you could. Data bind to a string in previous releases on enum and date. Time I think we're the only three types that we supported with data binding and laser in this release. We added support for type converters, so now any type that has a string type converter.

C

You can now use with with data binding so like an a bunch of the types that are built into the dotnet framework. Libraries already have type converters like this specified like if you wanted to bind to a good. You can now just do that without having to do any work because cou, it already has a string type converter assigned to it, and if you have other types that you want to use, you can associate type converters with them and then that will just work.

C

So that's a type converters with with data binding, and this is supposed to be a c-sharp I'm, still trying to figure out how to get that. The hash done. Another typo there we'll get that fixed last thing in the blazer space is in the he was the last release. We introduced this idea of directive attributes. These are attributes that you can apply as part of your component, rendering that effect the compilation output. They affect how your dot razor files get turned into into C sharp.

C

So event, handlers fall in this bucket bind falls in this bucket Raph key. We have a whole bunch of attributes that are special in that they impact the the compilation output. We introduced that feature in preview 6, as a standardized syntax for all of your directive act. Attributes scenarios there were a few places where the expected expected content of those attributes was a little bit, not quite right, like in preview 6. If you wanted to specify an event handler, you still had to put this at sign in front of the method. Name that you were.

C

You were indicating for that, like this onclick handler in this case that really shouldn't be necessary, because, if you're specifying an event handler using a directive attribute, it's pretty obvious, that's going to be c-sharp code, so that attribute shouldn't be at that at sign, shouldn't be needed. So in preview, 7, we've clarified all the cases for directive attributes which ones are HTML, which ones are sharp by default. So that add, that at sign is no longer needed for all your event.

C

Handlers, if you have it it'll still work it'll be basically get ignored, but it's just one less character that you no longer need to type, and so those are the main things that are new and Blaser other things that we're doing in parallel. Like we are actually spending a lot of time right now, getting Blaser ready. For you know, full-time production use making sure that blazer can handle.

C

High-Stress runs over long periods of time, doing our full security review process with blazer and going through and making sure that blazer server apps are secure and what our security guidance is doing. A lot of work around reliability and scalability like measuring the the memory perform usage and the CPU usage of server blazer apps when they're putting put under load. So a lot of that work is happening in previous avenues, continuing to happen in preview, 8 and things are looking really good. Actually like we're pretty much wrapping up our security review. Now.

C

Also, the API reviews I mentioned that we're wrapping those up. There will be a bunch of API changes that people will need to react to, but this will be the the last big change. So that's that's pretty exciting for us that we're pretty much about ready to lock down the API so for a preview, eight and then in terms of reliability and stress. You know it looks like we're the tests that we're seeing where we're taking place their apps and running them. For you know, hours and hours and hours. Those are looking good memory.

C

Usage is looking good, a few things that we still need to fix up there, but yeah.

B

C

We're feeling pretty happy about blazars readiness to ship in dotnet choreo later this year, yep.

B

And scroll down a little bit more because out, I love this next part, all the different event counters, especially when we get to the signal are part. You know that's very important to me in my my world. It's great that we've added a whole bunch of new event counters so that you have more capability to be able to kind of take a peek at. What's going on in your code and being able to instrument things now at a much deeper level and I think we're getting some comments in this dream.

B

I think it's C backslash up above Dan! If you scroll.

C

Our blog engine is is super strict about hash signs in the title, so I'm still trying to figure out what there right escape sequences to get that hash sign to show up so doesn't think that it's a heading marker. So if anyone knows they're marked down really well for those really strict, markdown parsers feel free to suggest what you think. This may.

A

Be you can.

C

A

The Unicode music sharp sign yeah.

C

B

Question do those counters work with Azure apps service I, believe you would see them in the logs. I haven't run a test with some of them.

B

I'll take a peek at that later today, but I believe that you'll be able to see those counters popping up, especially if you were to go to the diagnose and solve blade and look at the application logs or the event logs you'll start to see a lot more stuff popping up in there as well, because we've done a lot of work to make it easier for you to diagnose either startup problems or runtimes problems whenever you're running on App Service. So this.

C

This is basically the equivalent of like perf counters I've.

B

Always had in Windows and.

C

In dotnet framework, but event counters now are basically perf counters that are cross-platform and they work wherever you're running. You now have these moral equivalent of proof counters. In addition to tooling, it looks like for viewing and analyzing those those counters. So if you install this the.net counters tool, you can see the the counter outputs and see what's going on with your app and.

B

We're getting asked like in the charts on app service like if you were to go to the charts I'll, definitely take a big at that I, don't know for sure. If we're surfacing all those events up the way, we surfaced everything in the perf canter. But if you see here on Dan's screen you'll actually see dotnet counter skews you could. Actually you could do that in your kudu console, that's not as good.

B

We definitely like to see that in the charts, but I'll follow up with the teams and figure out if we're gonna get that that's a great great great question. Yeah.

C

Cool so like so this is all that net stuff. So it's like CP usage allocation rate, Total, Request yeah, it's great, but.

B

C

Of new instrumentation happened here as well. Right like these are all basically new counters, Kyle.

B

You much value. Oh ok, let's shift to me real, quick, ok, cool! Let me talk about signal, are real quick. So what I'll do is I'll shift to my screen and first thing: I'm gonna pull up here is I, want to go ahead and do control shift key to open up site on NPM. Most of you signal our developers know and love this. It's where the asp.net core signal our stuff lives, as of until today, eventually we're going to be moving it over here to Microsoft. We talked about this blog.

C

B

We're gonna move it over here and the reason why is that we've had some folks in the JavaScript community and then the Java community say well when I look over here and I see that it's under asp net it feels like signal. Art is just for asp net with the azure signal or service. It's definitely not just for asp.net anymore. So we wanted to kind of mitigate that confusion by putting it under the Microsoft banner. It's not that.

C

B

C

Yeah everyone can have the benefit, a signal arm. Every.

B

Exactly and I don't have the blogpost open. Let me pull it up. Real quick blogs go here to ASP nut. One thing that we talk about in that blog post down below we're getting asked about EF core, so I don't have any depth on the EF core stuff. So we could talk about that here in a moment. So you'll see here that we've also got new customizable hub method. Authorization I think it'd be better.

B

If I show you this in terms of a demo, because that's what I do so I'll flip over here to vs code and you'll, see that I have a chat hub because you know Fowler, so I've got a chat hub and I've got this authorized thing authorized attribute and I've got this new policy domain restricted. Well, that's not a role or a group or even a user. What that is, is I've actually added a domain restricted policy right here in my startup CS and the idea behind this is I'll.

B

Do add policy I'll, give it a name just like your course policies, and then I'll do policy, dot requirements ad and I've got my own custom requirement right over here and if I flip over to this you'll see that this requirement- and we talked about this a little bit more deeply in the blog post, but this requirement literally checks the hub method name. So in this case, I can actually come up with a very detailed control over how individual users can actually hit my Maya hub methods.

B

This is a much better control than like roles or users, because now we can get more granular. So what you'll see here is I've got a method. I've got some good real logic to check for later. Right now, it seems pretty restrictive just for me, because what I want to do is I want to restrict myself from being able to ban users, but I want to make sure that everybody at microsoft.com that logs into this application, can access the view.

B

User history and I've got the browser pulled up twice right here and you'll see that I'm logged in with my hotmail account and uh flip over here. You'll see that I'm logged in with my Brady G account, and anybody can send a message. You'll see here that I'm actually sending messages and we're not getting any errors. Now, if I were to go here and click on review, a chat review, a particular users history, you see that I'm not getting any errors.

B

I go over here now, you'll see that I'll be getting errors, because this is a hotmail address. Therefore, he's not going to be allowed to access anything over here, but we're disallowing Brady to ban users because he get a little ban happy. Sometimes so, if Brady tries to ban a user here, you'll see that he's actually going to be. You know disallowed as well. So what you'll see from this is that we have new. You know policy control, much much much better policy control.

B

When it comes to signal our hub method, you can get really really granular and then the only other thing in the blog post I'm going to do something really daring here and switch over to a different machine. Hopefully most guys, let's you'll, see that I've got a series of micro services here and I've got a bunch of worker apps that I've created and what I'll do is I've already published this one.

B

But this is a brand new feature that we've got in 16/3 that I'm excited about, because I like to do a lot of micro service development, I'll get here and I'll click publish. Now in the past. We only had this as your web jobs feature, which is great if you want to publish to as your web jobs they're fantastic, they start running immediately.

B

But what you'll see that our friends in the tooling team have recently added is being able to publish a worker app to either an ACR instance to create an ACR instance or a docker hub. This is a new feature in 16/3. You had that support for other types of projects, but they recently added it for the worker project, which makes me happy cuz, I like to build a lot of worker apps is dan can attest to for our time together on blazing pizza for build work he's the proletariat.

B

The only other thing I would call out here is if I scroll down so I just want to make sure you remember this moving from asp net to signal to Microsoft so update your your stuff and if you depend on us, feel free to reach out to me. I've actually got a list of all the dependence on asp, net signal and I'll be reaching out to you is.

A

There a way with npm that you can like forward, or you know what I mean deprecated but like link forward to the new one. There.

B

Is I'm glad you asked that question? We had a open issue on github, where we had quite a bit of discussion both from folks in the dotnet community and some folks in the JavaScript community. We've got a link to that in the preview: 7 blog post. So if you have any feedback or you want to contribute to that discussion- feel free a pop out there and do that, but we had some great feedback from some of the JavaScript community on how to properly or improperly deprecated or move, etc, etc.

B

But we, through that entire discussion, it's a way beyond the scope of the show. So the only other thing I want to call out I think I'm allowed to talk about this. I'll go over here to the dotnet site right here: dotnet, Microsoft, comp and also.

C

B

Way down and you'll see here running on preview, seven, so we're actually running the dotnet website on preview 7 in app service, but I do want to call this out because we started this before the folks were able to get everything out to the fabric. You could do this today and with any SDK. If you use Azure DevOps, for instance, is how we actually set up all of our builds we'll see here's the build where we actually pull from the github website and build everything. This first step, which I think mr.

B

handsome one blogged about once you can actually specify which version of the.net SDK you want to use, and it will pull in that SDK to your build agent and build it right out. So you can do that. So if you want to start building on eight or nine or infinity, you know you can do that with with the azure DevOps today, yeah.

A

We do this with the tutorials Shane Boyer set this up, so we have builds going again because we have like, for instance, the app building workshop has like I, don't know, seven different, like steps in it right and each one of those builds and the entire project builds, and we have different branches for different, like we had one for dotnet core to one and now to two and three, oh, and so we have CI, builds going for each of those. Using this exact feature really cool. That's.

B

A great feature: if you want to go ahead and get started with preview, 7 or preview 8, you can do that today. You can see that we're already doing so. We actually had had a lot of fun with it. One of the things that we were able to do, which I was excited about. We had an intern who was going to be on the show today it's my mission to get him on the show before he goes back to school this summer, but we had.

B

There was a funny conversation where we had a lot of IES rewrite rules in web.config I think we had 73 of them, something lately and I'm on a mission to kind of bring all that stuff out of there and just you know get it into. You know dotnet core, so I can run everything on my Mac or Linux or in a container.

B

Mr. Lander and I were doing that together and sorry.

A

Where are all those rules and they.

B

Were in web config and in the.net website, because we had been using I think Oh up to this, when I can't remember what we were on, but what we wanted to do was to kind of bring everything and you know do it with dotnet core. You know idioms. So I talked to two of the gentlemen in in the team room and I said you know how how would I move this over and they said we're the interns that worked on the you I'll rewrite middleware for asp.net core.

B

We can totally show you how to do it. I was excited to say that it probably took me about five minutes to get it installed and deployed. We really literally just moved that XML out of web config, letting them from from a separate file according to exactly what what the docs say it lit right up. It was pretty it's pretty fantastic, so we got that got that push in and it's all running down that core preview. Seven. Now it's on the.net website, pretty cool. That's.

C

B

Yep, so we can do it, you can do it of.

C

Course we would expect nothing left.

B

And then I'm looking through to see if we have nope that's the end of the the blog post, I, don't really have any other content. Do you guys want to talk about anything? Anything else are doing any other demos. I know. Dan's gotta have at least.

C

The release in September go: have some cool show.

B

A

Cool so so you've talked about how to get all the stuff installed um and it's in the blog post here and then. If people have issues or you know, feedback you've got that link down at the bottom of the blog post. So I always want to point that out right, because everyone sees all this cool new stuff part of the reason why we show you this every week. We want you to be able to get involved and to get your features. You know your feature, requests in get your feedback in all that. So oh.

C

Okay, I have a little update. Unfortunately, oh boy.

B

C

Looks like 16/3, everyone is slightly going to be delayed a little bit delayed, so I I don't have an ETA exactly exactly yet when it will go out, but it looks like they did hit an issue on on release. So if you're messing around on ik or three oh I mean you can still install the SDK, you could still use the you know, of course, the full CLI experience.

C

Most things will still work in Visual Studio, with like 16 to preview for or actually I think it's a 16 yeah with a 16 to preview, for which is in the should be in the preview channel. Now there may be some issues that you might hit just because of incompatibilities there, but the most part it should work, but hopefully we'll have a 16-3 preview one out for you shortly. It's a slightly unfortunate, but you know things things sometimes happen so just FYI, if you're not seeing 16 3 preview 1.

C

Yet in the in the preview channel that there's a look like there's been a little bit of a delay and.

B

Keep pinging yes, Dan. We we have a question. Can we get the blood or source code.

C

Is a great question? So if people don't know what blooder is it's a blue, a blue colored butter? No it's a letter! Is this pretty awesome demo that Steve Sanderson did at NDC Oslo, not that long ago, like just a few weeks ago, a month or so ago, and it is a combination of blazer with flutter. So flutter is a UI framework. That's been put out by Google, based on dart for doing mobile, desktop web app applications using a common UI program model and what Steve did in his.

C

He took Glaser's component model and remapped it onto onto flutters component model, so you can use blazer. You know c-sharp the razor syntax to write flutter applications as a demo, which was pretty awesome. It was pretty cool, not a mind-blowing, I, really I think it really sort of highlights how flexible the the Blazer component model really really can be. The code for that is not yet publicly available. I am working on trying to see if we can can and share that code, just to be clear.

C

Blooder, a blazer plus letter is not something that we are shipping or something that you should plan using for any of your applications anytime soon, it's just highlighting a pattern, and you know potential future directions that we might take blazer and in the future. So it's not available. Yet. We are I hope that we can share that code, but we'll let you know if, as soon it is available, you know other things that we we think about with with blazer like blazer. Currently, the main focus is on web applications.

C

We started out with rec running blazer code directly in the browser and web assembly, and then we also paired it with this server hosted model blazer server apps that run server-side over a signal. Our connection we have shown, like writing, desktop apps with with blazer using electron, we're very similar pattern actually to the blazer server model, but where the two processes just server sit right next to each other, you have a dotnet core process and you have an electron process and the Blazer components in the.net core process drive the electron app.

C

So you can write cross-platform, desktop apps using web tech and an blazer and looking for this there's, it's certainly possible to think about like doing mobile scenarios with with blazer as well. In this.

B

Question about that blazer for xamarin forms, yeah.

C

So in in the react world like if you're familiar with react, GS I mean the react. Folks came out with react native, it's a very popular platform for building mobile applications where what they did is they took the you know, basically, your JSX markup and remap that to native control, so you can create native mobile applications written in JavaScript, using the react program model such a thing, which is totally conceivable to do also with blazer same way that Steve mapped blazer components to flutter components or map D the Razr markup. To do flutter components.

C

You can imagine doing very similar mapping to native Android and iOS components with with blazer. So those are direction. We haven't those we're still trying to get the web stuffs done. So we haven't done a lot of explorations in the mobile space. We have had some conversations with the xamarin folks, but you could imagine doing something very similar to what xamarin forms is.

C

Xamarin does basically the same thing, but based on a saml programming model, you can imagine taking the same runtime that xamarin uses instead of using a sam'l based programming model using a blazer based component model, but mapping in the same way that they do to native UI controls. I've also thought about. You could do a hybrid approach, some mobile applications, instead of rendering to native controls they render to like a webview component that lives in the application and that allows you to reuse a lot more of your UI logic.

C

If you already have you know, web UI assets that you'd like to just reuse in your in your mobile application, you can imagine having Blaser components, running on like the salmon model runtime and then rendering to a webview very similar to how you would render to a chromium shell in an electron application. These are all things that we're thinking about, and you know directions that we we'd like to go. But you know one step one step at a time. One.

A

Other thing that came up questions on the chat was about what's new with any framework, there is a new blog post. It came out right at the same time as the other ones did that's linked. So I've updated the URL list for today to include the EF post and then also it's linked in the dotnet teams, blog post.

A

So in some of the top things that they list in preview, 7 or query improvements, so so yeah so definitely check that out and it's been a bit, we should get the EF team back on stand up here. That'd.

B

Be good could be good yeah, oh yeah. The query. Improvements have been a really great improvement to how EF is gonna perform. I. Think you're gonna be happy when you start and trying the new stuff out leaves will really really hard to work on it. So that'd be great cool.

B

A

Right well, I think that wraps up this show. This has been amazing. A lot of excitement, great chat. We had a ton of people showing up today, which is cool as.

C

A

Getting closer to release so so that is great, Thank, You, Brady and Dan. Thank.

C

You everyone have.

A

Fun with seven thanks folks, okay Brady, one of those buttons will ends the the thing and I. Don't know what all the other buttons do. Good luck take.

B

Care have fun everybody I found with maybe seven.