.Net Foundation .Net Community Standups, 17 Jul 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: ASP.NET Community Standup - July 17, 2018 - Take Two in New Studio

Description

Community Standup links for the week: https://www.one-tab.com/page/VlCvKlGWQ2yjEsvkGwwAFA

A

Have a green light: oh there we go we're good. We.

B

A

Did you update the actual site site no.

B

Because I didn't know what to do. I'm like.

A

A

B

A

B

Once you start I think then you can get the link.

B

Very meta, the beginning of our show, is us looking for the embed link. Okay, so no I've got it and I will pass it to you. Does teams work.

A

B

What I did was I googled, dotnet foundation, YouTube I'm, a problem solver I'm.

A

Looking at the video stream, so I'm, assuming if I, can see the stream everyone's saying they can't hear me, my levels are bad again. I can hear myself just fine, so I'm not sure why the levels yeah.

B

Do ok so I just can you people on the chat? Can you hear me.

A

Everyone says they can't hear me.

A

Like I can see the levels or.

B

A

Can? No that's a different, that's John, John's working, fine! Ok! Yes,.

B

Thank you Ray that.

A

Makes debugging hard when I'm looking at the wrong level meter.

B

A

B

A

So I'm quite a lot lower than him and like this is me an inch in a way like I'm, not usually gonna sit here. This close, obviously I, don't usually be back here like this, so we need a bit more gain on that mic. You can hear John loud yes, I quinton can hear me just fine. It just went up. I can eat myself. Flattened! Oh, oh, ok! Maybe that's better yeah like it speaking now in the yellow. So when I yelled.

A

Because there's more than one Mouse in front of me and I use the wrong one, we need to order these, so we can see them together. John. Can you talk me to a test? Hello, I'm talking? Ok, so we seem to be the same. So I could turn my level up now to my John, can you mommy's? Okay,.

B

I'm still talk, I'll talk now.

A

Yeah I know I, can't he I'm hearing myself a lot louder than John. That's the problem. Okay, now I am louder. Damien, excellent yeah, but Phillipe is saying, he's hearing me. It said now it was a four okay. Everyone is disagreeing on how they're hearing either.

B

A

Everyone and I'm- sorry, if you can't hear, is probably because I can hear him fine and these people, some people can okay. So let's go back to the embed link, that's what we were trying to fix so.

B

A

B

It to you in teams ah thank.

A

You very much so, of course, you have to click Share to get the embed link. Oh.

B

A

Now we know how to do that: let's go over to yeah.

B

I'm, just thankful we're getting a few run throughs before we have the the added stress of Hanselman ongoing. Is this 4k? What's going on.

A

Yes, all right, let's delete! That's, let's save all right! Sorry, the website now should show us, and it does. I should be able to click on that and show you that's perfect. I think we're good Wow I think we're good and I should be able to make this go, live. See myself. I can see you I can't see anyone else, but that's fine! That's how it should be. I can show everyone, you there's a wave John. Everyone can see you now and we can see both of us.

A

There's me in the bottom corner and there's John on the big screen and there's back to me. Alright, welcome everybody. You're still a little quiet in my ears, we'll fix that afterwards. So we're done pretty well. This is a different setup to what we had last week. I apologize again for the teething problems, but we have a better setup than we have last week is now actually going through the broadcast machine which last week it was going through my laptop.

A

So we should be in 1080p this time, which is a big improvement and we're still adjusting our audio levels. That's the hardest part of this entire set up, as we have in room audio. We have my laptop, which is running the Skype call the team's call going into the same mixer as the in room audio and then I have the feedback, so I can hear all of it, but we have to kind of adjust. All of that to be roughly the same.

A

Someone's saying my voice is still too low. Others are saying it's fine, I can't hear it John very well, but whatever will figure as long as people can roughly hear me and get the gist of what's going on, I think we're OK John. Do you have community links to show.

B

A

B

Were now presenting.

A

So you can show.

B

A

B

Will do show the desktop. I.

A

B

Screen number one: you have a screen on in your background like bright right now, maybe I've got three monitors.

A

B

A

See you screen just fine excellent.

B

And I will move this little dude over there awesome I like this. It's kind of meta here I've got my first link after I tweeted, the show was going live now. We've got a little ad about the show. That's.

A

B

So um got a couple here on HTML email templates with razor, so Scott has a very comprehensive meaty post going through all kinds of stuff. So the idea here is embedding something into a dotnet standard class library that uses razor to generate emails and send them off so he'll know.

A

B

So this is really cool. This is you know. This is a great sending email sending nice format it. You know, HTML emails is difficult, and so this is. This is really good. This goes through all the stuff base, email templates and all the stuff. As far as you know, the razor you know crazy, creating your like a base layout and shared, and you know specific views and stuff, so so really good stuff there now we've also got one. This is from from Derek and so Derek went through and also wrote something up.

B

This is about sending razor from a console application, so here he's going through explaining how to do that and he he references, Scott's post series as well. This may be useful for you if you've got a short attention span, because this is a much shorter, shorter post and this is focused on sending from within a console application rather than a dotnet standard library, hmm stuff.

B

Okay, so Halil posting on asp, net, core dependency, injection, best practices, tips and tricks. I will confess to you that dependency injection is still continues to be something similar to reg X. For me, where I need to go back and reread through it regularly because I forget something, it just doesn't always stick in my head. So this is a nice kind of explaining. You know bullet point wise, here's a snippet code, here's some best practices, here's stuff to watch out for so he talks through the different.

B

You know: constructor injection, what it's used for property injection. You know you know good practices when to use etc. He talked about service, locator and kind of summarizes. You know times where you wouldn't want to use it talks about service life, time, etc. Then he also talks about resolving services in a method, body and single tenant, scoped, so just kind of a nice refresher good to read through and and describing kind of all the kind of bullet point. You know best practices and stuff just.

A

Want to acknowledge I am seeing some artifacts on your screen, sharing, which do seem like they're, making its way into the stream. Okay, I'm, not sure why it is so it's it does seem to be coming through the team's desktop sharing, like I, think I, said: I, think it's okay, but I just in case people are wondering I I, see it too. So, okay.

B

A

B

Right, okay, so Adam exploring custom middleware, so he kind of walks through basic. You know, sort of the hello world and building to a little bit more complex things with configuration and stuff. So here's some some custom middleware, that's going to just write some stuff out before and after you talked about, you know kind of some some standard steps.

B

These are honestly and he references his up earlier that this is some based on like MVAs and stuff, and this is stuff that we presented on before, but I kind of like how he just kind of walks through this and in a nice kind of smooth manner. So he talks about you know writing before and after the context component, izing, adding custom options, and then you know some steps for that for configuration.

B

One is if you're gonna configure it in just one place for use throughout the entire application, and the other is if you want to configure for you some multiple places, so you want to configure. You may want to use this middleware a few different places in your app and configure it differently each time. So he walks through that. So just kind of a nice nice walk through there, so this is a big one. Seiler dilatory is hosting about the update for the the architecture guides. This is modern web applications with SP net core and Asher.

B

So this is the kind of free ebook. This is a big. You know big meaty thing, and so it's so this is out. This is updated. So that is a significant effort. Knowing how many you know how many pages that is four that you updated.

A

B

Okay, so Brock has um here's something he noticed and I'm I'm, not sure. If you got any comment on this, he says you know watch out for the interaction between between roles and schemes that some things have changed with authorized filters for asp net core to one. So what he has seen is that the roles combined, but the schemes do not so this was something he was not expecting and that it's it looks to be changed from what what was in is peanut core. Oh, so.

A

This is specifically in MVC just reading this, because the other option that controls this seems to be based on the MVC options and it's about combining authorization filters, and this is also yeah. This is something that we that we changed behind the compatibility version flag. So you shouldn't see this change.

A

If you just upgrade your app and don't flip the compatibility version two to one so for folks who haven't watched the show before we talked about this, we introduced this API in MVC in 2.1 to allow us to make what are technically breaking behavior changes in minor releases for things that we felt were just wrong. The things that behave incorrectly that we get feedback about that typically, would be a breaking change to change them.

A

We now put those changes behind a configuration flag so that we can make the change, but then you have full control in your app to decide which behavior it is. So, if you're creating a new app that targets to point one and sets the to one compatibility flag or you follow the migration doc and you follow it all the way to the end, you move a to o app two to one and you opt into the two on behavior. Then yes, because this this compared this, you know this behavior will change.

A

This is one of the seven or eight things that was changed in MVC, okay,.

B

Good- and that is something he points out towards the end and and that's a good reminder- that's that codes there for a reason and finally project and probably better not to just delete it willy-nilly. With that understanding, yeah.

A

Basically, there aren't many cases where we want to make changes like this, that don't align with the typical semver semantics, but you know given the scope of the framework and given the magnitude of major releases, it's not unusual for us to have an area where, once we get more feedback, we realize that the behavior is just wrong either.

A

It was intended to be that way, but we didn't realize it would be bad or there was a flaw in the design that we didn't get enough feedback on during previews that we need to be out of the in control in the next minor. So we have this. You know capability now great.

B

Okay, okay, so this this is cool Sam's posting about the release of asp net core o data, so this is this is walkthrough on creating o data from the server side and then he's just using like postman to kind of query it from the front end. But this is something where you know: people especially I've talked to people that have investments in o data that have been using o data or have tools, front-end tools that are written against a no data backend, and so this this is helpful for for working with that right yeah. This.

A

B

A

Released by the our data team, yep.

B

So this is this walkthrough, you know creating a installing the OData nougat package and then you know it's kind of a basic model, but then he walks through some other things like enabling querying talking about. You know implications of that and- and you know all that kind of stuff and then kind of so here- he's going through and kind of querying from the front end, so cool stuff, okay, so nemi here is writing about getting started with signal, are using asp net core and streaming the data to angular.

B

So so, there's a lot of code here as far as actually kind of binding to it from the from an angular front end this. This is all you know, so decent amount of code walking through creating a stock I believe this goes back away. Is you had a stock ticker app way back when so? This is kind of this? Is.

A

B

Have the stock ticker he's got some things that I'm not sure if you had that before, but there's there's support for toggling market state, so you can have the market as open or closed and once the market opens and the the costs go up and down randomly yeah.

A

No, that was that that's been there since day, one okay go up so there's this that the stock ticker sample got rewritten for the new signal uh core, so I'm, assuming that this is basically an investigation of that code base yeah.

B

And I think now did yours work with angular on the front end. It's.

A

Not this, if this will be a rewrite using angular instead of I, think the new one Brennan on the signal. A-Team rewrote the new one. I thought he did use a new framework. I thought he might have I, don't know, I meant maybe.

B

For you, accidente I use jQuery.

A

Obviously and I think he updated the new one to not use jQuery I, don't know if he used a framework or just do it all with Dom stuff. For my show, oh.

B

All right, so this is a good thing to be aware of emmos posted about dotnet standard v next, and this is public discussion of what goes in that standard v next, so this. This is something where this is I've linked to this, to make it easy to to read, but this is out on the.net standard repo, so you can go well.

A

That that's actually the most fork you're looking at right now, yeah.

B

It is, and the reason I did that was so that I could actually read the you know the scroll through and easily read the the the markdown right, but that well he's kind of posted actually in a public poll request.

A

Oh, you can just hit the V file in the pull request right, yeah.

B

A

All right, fair enough sure.

B

A

It's in a pile right now: it's not actually proposed or merged in a PR for discussion. I guess.

B

All right so Dickies posting about dotnet if I elements, so these are react, react components on the front end and then he's using there. There's an mvvm system, and this and binding using signal are for updating. So you know some good-looking components. They're all react react based there, there's also on the site. If you click through he's, there's some nice kind of samples, including some stuff, like you know, customer forums and admin dashboards and those are all working with that too. Pretty so yeah. It's not.

B

The quality of documentation is really nice here and it's all kind of interactive stuff and relock posted this I thought this was really cool. This is a hero to a, and this is kind of any kind of putting parts together. He wrote a dotnet core global tool that will update you, know the standard xml-based config to JSON based, oh.

A

Interesting yeah.

B

So he's actually going through and parsing. You know your kind of previous, you know whatever it is global, configs or you know whatever kind of config files and then writing them out. He's got special handling in there for app settings and connection strings. Is that.

A

B

A

He handles like I'm trying to think what else you would you would merge like you would migrate.

B

Read those yeah I, guess: that's it! Okay!

B

So so he's going through and reading that you're, you know kind of that's that's things out of the config files and then writing it to hierarchical Jason. Oh.

A

B

So yeah it's it's a nice kind of to see. It looks like both a useful tool and also a kind of cool application of the.

A

Global tool, stuff, yeah, exactly cool.

B

Scott Allen writing up I love these when he goes through, and you know just like seven tips and they're just boom boom boom boom. But these these are great little tips for troubleshooting asp net course. Startup airs. So things like you know, making sure you're seeing the errors. How do you know how to view the stack trace and that kind of stuff?

B

Turning on logging for is and and then of course also, you know, the dotnet CL is- is a great way to to watch those errors.

A

Yeah, that's really good. We actually have a doc about this today as well. That's a little more targeted to diagnosing startup errors when running on things like as a wrap service and those there are very similar set of steps, but it involves also like oh, you might go to the koodoo console and try and run the app from the console in order to get more information.

A

It's also an area that we're continuing to try and do a bunch of work in so in with the ANC M in pron can work where you know we're gonna host the a spoon 8 core app in process in is our hope is that while we have that working already that we can get more in our error information from the runtime and we can also scrape the general output of the application, and so what we do is when NCM tries to start up the application.

A

It buffers the console output during the startup phase and if the process dies or the runtime is fails to be started, we'll capture all that output and then we'll write it to the Windows Event log, along with the normal sort of a NCM, couldn't startup your app. So hopefully, if at least, if you can see the Windows Event log you'll get a lot more detail about.

A

You know why it was the application wouldn't start, and then you don't have to go through the whole configure console redirect output, redirection or you know, logging and run it using dotnet, XE or whatever. You can just go to the event log. If it failed to start and is and it'll tell you, oh, you know your app didn't start because the shared framework you were targeting wasn't installed whatever it is. So yeah.

B

A

We've been continually trying to refine that and there's a I think there's a meet-up this week, actually between the a spirit, core team and the azure app service team to try and drill down on that again and see if we can get to an even higher level like. Ultimately, what we'd love to be able to do is that when you publish your app as soon as it's running on Azure app service, if it fails to start for whatever reason like the portal would have a banner on your site.

A

That literally says your app is failed to start click here to find out. Why, like that's kind of the Holy Grail, that's what we want to get to, but, as folks can probably imagine getting to that type of very real-time experience, where the little delay as possible is a little more complicated than the sounds, and so we're working with that team to try and figure out how you know.

A

How short can we make that feedback loop so that when I publish my app like if you right, mouse click publish from V yesterday, it'll actually tell you right in the output. It says: oh, your app is now publishing is published successfully and then it'll give you a URL of the site of where it published to. It would be great if it could tell you whether the app actually worked right like if there was some type of way to smoke test it or it.

B

A

If there was a startup error and tell you immediately that we like get the feedback loop down, really really low, but then, if you're doing a CI CD deployment, whether it's fire, kudu or VST s or something else you'd. Obviously you need that error somewhere else, so you need to be able to very quickly download. Oh, my apps, not starting.

A

Why is it it'd be great if you just go to the portal and just see that, like a banner kind of what I'd like to say it so anyway, they're working on that, but it's good to some.

B

A

Folks, have you know sort of collated this information together right does.

B

That integrate also what you're, just talking about that experience, would that integrate with like health checks as well. Yes,.

A

I could I mean well start at Bayer is probably not because health rising your app. So if your app doesn't start yeah.

B

A

Gonna do much the.

B

Trick question.

A

B

What Scott you yeah.

A

So health checks is more about, obviously, which is something's being worked on into it's about detecting degradation of health after the app is running, whether it's because an external dependency is stopped, responding or your CPU use has gotten too high, or your memory paging or whatever all your exception rates, gone very high. You have various metrics in your app that you can use to determine.

A

Is my app like okay to be in this cluster or to be you know, blow balance to whatever it might be, depending on your deployment yeah from as simple as yes, I'm, okay or I'm, not okay, to varying grades of like.

B

A

Fine or I'm, okay, but I'm running in a degraded state. So you know you can send me requests but I'm having a couple of issues right now, so yeah.

B

Well, alright, so this one's interesting, this is Mike and he's writing about razor pages, typescript and knockout. So this is a you know: it's it's an interesting post he's walking through if you're, if you're, using knockout. Why.

A

Is that who is he throwing shame it.

B

About using jQuery presentation.

A

B

He went to a presentation and someone said who still uses jQuery.

A

And no one but their hand up he's.

B

Like I, secretly still use jQuery.

A

Well, you know if you go to those websites to track what the top hundred thousand hundred thousand sites use. We can tell these.

B

A

Are still using take query and.

B

I mean it's still, I think I, don't know if food strapped for uses jQuery much but I mean bootstrap. 3 definitely did I mean.

A

Differently does yeah we just picked in the bootstrap full stuff actually for to to I'll talk about that in a minute. Yeah.

B

I mean there should be more respect, I think for jQuery, where it like. A lot of the stuff was spackling over stuff that didn't work well or work the same between browsers but right man. It sure got us through a lot of like well.

A

It also introduced a of really interesting sort of coding paradigms that we hadn't seen in in, like the whole query, selector, syntax or sizzles as it was called and Jake, who turned into a real API like that. That literally came that idea came from jQuery as far as I know where you could just use a CSS selector to get a collection of elements, and then they added the whole sort of chained, fluent programming, style of working on a collection of elements and then chain.

A

You know, chaining calls with disclosures and setting the the the the active this scope to the element being operated on a lot type of stuff. That was like popularized, at least with jQuery right and so.

B

A

Then, having just a nice Swiss Army knife for common utils for like Ajax and event handling- and you know, custom events and data data, you know when you put data or attributes on your.

B

Yeah all that type.

A

Of stuff, you know that really Jake really popularized, that type of type of stuff so like it does what it's designed to do really really well I. Think.

B

If you're building a huge single page app- and it's it's not know, basically, is any.

A

Templating his way, I mean that's. Why knockout came about right because not how to introduce the idea of bindable two-way, binding templates and but was generally used in conjunction with something like jQuery or maybe you would use knockout and underscore, and then they kind.

B

A

Into the idea of full-fledged spar frameworks- and so I mean, but there are many sites that aren't written as sparse, obviously, and they don't need they don't want to use angular, because it's not the right fit for them, they're doing server-side rendering, but they were still like a library that gives them these types of utilities and personally, I. Think jQuery is perfectly fine for that. If you need to do those type of things, it.

B

Wasn't that long ago, I don't know if they've changed it since then, but I was on the duolingo web site and.

A

B

I was like what tech are they using here and it was all jQuery and it was, it was pretty clean. I was, like you know, it's a so yeah good stuff. So so yes, I, might go through writing this up. Talks about you know using typescript knockout and is Pinet and kind of hooking and razor pages and kind of hooking it all together. So very post, yep, okay, so mohamed wrote through this is a quick but good thing to know about.

B

This is query helpers in asp net core, so here he needed to deal with parsing, query, strings and writing query strings and this kind of takes out all the concatenation and is it the first thing, use a question mark otherwise use an ampersand and escape it correctly and all that kind of stuff. So yeah, let's say it's a good thing to know about.

B

This is just basically a link to a survey, but this is about the il linker and when they tweeted about this they included SP net core and so I thought it's. You know worth letting everyone know about this. So this is the you know: getting feedback on building il linker that will be used everywhere, including nice, peanut, core stuff, okay, getting towards the end.

B

Here, we've got Hashem, and here he talked about localization testing using an in-memory string localizer and when I first looked at this I actually read quickly and I was like in-memory string localizer. Let me Google this and I couldn't find any hits and I realized. Oh that's what you're creating here, but what's the idea here and he lists out some use cases. You know some are you know, use if you're not using rosettes. You don't want to.

B

You know you're, not in Visual Studio, also things like for unit testing and then also he talked about some cases which I'm sure he hits regularly, which is demos or experimental, localization api's. But so you know, I could definitely see this for unit testing. Where you're you want to create a bunch of resources. Maybe you know on the fly kind of stuff, so here's he's riding up using an in-memory string localizer how to create it, how to register it, and- and so there you go.

B

The last thing I'm linking to here is something you tweeted about I didn't know. If you wonder.

A

What you're, stealing my thunder, that was the first thing. I was gonna talk about well.

B

Or I'm transitioning to yours very sits a second things.

A

Let's see if I can get this transition, so I'm now picture-in-picture and then I'm gonna flip over to mine and then I'm going to do what am I gonna do oh I know then I'll do this and then I'll do that and now it's transition. But now it's on my screen instead of your screen at that, so now I can drive it. They can't see you, but that's okay. They can't see me other, but that's okay, yeah. So this was something I tweeted about this.

A

Some folks on the.net team have been working on updating this, this landing page that we called it's the marketing site. Right, like we know of customers, you basically just consume all the bits through github and that's fine, but for the vast majority of people they get dotnet Cornell through visual studio updates or they going download it themselves from.

A

You know the marketing site from do TiVo, unity, and so just to prove that I can go up to the address bar I could say: do T dot any T hit enter and it redirects to this site here. So we've been working to try and simplify this site for acquiring sort of the latest pieces and the common pieces. The reality is dotnet core is a is a fairly complicated framework. You can it's. It's made up of lots of different things. That's not just one thing. Obviously like there's the dotnet called runtime.

A

There's the HP net cost shared framework. Earth has done it XE this. Then you get a fallback folder. It includes the SDK or the COI which has Rosalyn and msbuild, and then they were billed for 30. You know 32-bit and 64-bit and different platforms, and so all of those constituent modules you can actually download separately in most cases, but that's generally not what you're gonna want to do. You generally just want to get yeah I'm a developer. Give me the SDK or I'm running a server.

A

I need the runtime right, so I need stuff to build. Apps I need stuff to run app, so it's kind of in that you know the typical thing that you see with any software development platform, and so we've we've got a new download page I, just clicked on the download button. That is revolves around those two things now.

A

This is the home page to download both doc, nickel and dimed net framework, especially all of dotnet, if you're only interested in neck, or you can focus on the left-hand side here and obviously for the for Linux and Mac. It'll only show dotnet core. Now this page will default to whatever platform you're currently on so I'm running on a Windows machine.

A

So when I click download, it shows windows, but you can obviously change that to download alternate platform versions as well, but just know that when you hit this it'll look like whatever is right for your platform. So for Windows we have got me a framework as well, but, as I said, will concentrate on their core. We really want to make sure that you get that we direct you very quickly to the most important parts.

A

So when it comes to branding of dotnet core, really the major and the minor versions are the ones that we want folks to focus on most of the time. Those are the versions that you target, so you say: I am building an app for a spinet core they're called 2.0 or 2.1.

A

That's what gives you various api's and features the servicing or the patch levels are typically delivered in the case of dot, Nicole runtime or the HP Nicole shared framework they're, delivered by installing something machine wide right, generally speaking, whether it be the SDK and then deploying your app again if it's self contained or deploying a new hosting pack or new, a spirit core slash, dot, neck or runtime, and then all your mission, you know all the apps on the machine will get rolled forward under that servicing release.

A

So we don't show that patch version up here, but you can see like just that. It is shown just down here so like it's not like it's completely obscured and we have had a little bit of feedback since this page went live that they. Some folks would like to see this version higher up, but we're going to continue monitoring this we'll look at the uhm, we'll look at like the the analytics on the site and we'll see how folks are going.

A

But, as I said, we've got this new sort of emphasis now on, if you're building an app and there's a little over a little thing here. That tells you a little tooltip that says what that means. You just download the SDK and if you're running an app and the game, little tooltip tells you what that means. Then you download the runtime now this button here and this link down here that talks about the runtime.

A

They are this one here sorry they're focused on giving you the runtime that will run the most kinds of apps, so that includes the a spinet core shared framework. Okay, so there's the dotnet core framework at the bottom, so dotnet core net core app is the TFM which results in Microsoft net core app as a shared framework that you run on and then there's a Microsoft HP net core shared frameworks that run on top of that. Okay and so typically most servers.

A

You want both of those right, because most people are running a spinet core apps in production or on servers, and there are fewer cases where you have a machine that just has dotnet core runtime on it and not the Shedd framework. I mean they do exist, but we don't have those links on the front page anymore, because we've got a lot of folks who are confused about.

A

Oh, why is there a link for dotnet core and a snare core, or they wouldn't see the a spinet calling they just download, they don't Nick or a runtime update, and then wonder why their apps wouldn't run so we've really optimized this site for, like the 90 to 95 percent use case. Okay, if you want to see all the downloads, then you can just click the all two point downloads link right here and that will take you to a page that has everything before I.

A

Do that the other thing to call out is: we've also made the release, notes a little more prominent. So we had feedback during the various patch released that people couldn't find the release. Notes- and so we've made sure that those were these notes here, they are here. The release, notes are now sort of front and center on this main download page now for the other platform so like for mac, it's a developer platform only so that download page is much simpler. There's no dock their framework. Obviously cuz.

A

It's not windows, there's no runtime installs, because you should just be downloading the SDK. That's what you do on a Mac cuz. It's only really for development. So there's just one button: just download the SDK for Linux, it's actually a little more complicated because you removed uh net framework, obviously, but where there are different ways to install depending on your Linux distribution. So a lot of folks use package managers for Linux like apt-get or yum or whatever it might be, depending on your distro.

A

So we have instructions there and how to use package managers to get the SDK again. Building apps get the SDK running out to get the runtime versus using zips like downloading archives, which is quite common as well. In the linux space there isn't the traditional in you know traditional installer approach in the link space. You generally use a package manager or you use an archive. So every page that's a little bit a little bit different, because every platform is a little bit different.

A

But if I click through to these sort of fall down there list for this release, now again it doesn't have the patch. It's just like give me all downloads for the two ones stream right. Then we get this new page, which is reverse chronological, and we've worked really hard on this page to try and make it information, information dense, but still very clean and clear. As to the timeline to all the releases that have been available with, with the focus on the last release at the top right cuz, that's generally, what people are gonna want?

A

They want to get the latest release okay, so this is dotnet core 2.1 again, left-hand column is if you're building apps SDKs right-hand column is if you're running apps. Now this is where it gets a little more complicated right. If you're running an app, there are edge cases where you might just want a very specific runtime update and that's why all these links are here, which is why we generally tell folks to focus on what's on the front page.

A

But this is how you see everything we've got links for each bit nurse, obviously, and then all the os's link sort of merge together into this one list here broken out of these bullet points. We've also introduced these new tags, and so you can see that two one two is the current release, current meaning the latest in the current train. So we have these two trains right, for.net car we have LTS and current.

A

So two one two is the latest of the current train, which means that if you're on the latest bits- and you want to be supported- you have to be running the release that has this purple tag on it right. That is the supported release currently under the current train, and then there's also a green patch, a green tag here that says this includes a security patch. So anytime, we do a release that includes fixes for any CVEs which we sometimes refer to as nsrc, so Microsoft Security, Response, Center I.

A

Believe that really refers to then you'll have this patch as well, so you can scroll down, you can see which ones are these releases contain security fixes now because two one hasn't had many releases. Yet there are many here, but if we go find the two hole equivalent version of this page, because some folks are still on tour because they're still currently supported, then you'll see more of these tags and your product and you'll see LTS tags on the one or versions of this page.

A

If I go find the one ovations I should just be able to URL hack right, so I should just go to go. Let's go to two dollars at a 2.1 I get a 404 Rowan I'm gonna blame other people. Instead of me taking responsibility for doing something wrong. It's because I typed it in wrong, see that's what happens when I'm. Looking at a monitor, that's six feet away from me! Try again! Oh there we go there. We go so now I'm on the oh train.

A

You can see quite a lot more. You know going on here because this has been a longer set of releases. I2O came out what last August I think it was so it's been in 11 months right, so we've had quite a lot of servicing releases, so we can go scroll all the way back in time to the previews. Even so, you've got this one page now that shows you every public release that we did in this train, which I think is super helpful.

A

So you can see that the preview releases and marked as preview and if you hover over those it tells you that you know previews are generally not supported you use and we release them to get feedback, etc, etc, and then you'll see that we've got two or three was a security release to a 3-2 three years is listed twice all because two or three higher. So this is another interesting detail. Let me turn off my PMP, so you can see more of this, so the SDK, sometimes ships separately or ahead of the runtime release.

A

Okay, so the SDK also ships in Visual Studio. So right now, if you're using Visual, Studio 15.7, it includes a version of.net core. It includes net core, oh whatever the latest patch version is and 15:8 will include 2.1, whatever their latest patch version is we're going to move it forward to 2.1, and so sometimes we have to do a new SDK release, because there was a vs release and something like Rozlyn was updated or NuGet was updated or msbuild was updated and those components also ship in vs.

A

So they have to match from a tooling point of view. So sometimes, even though the framework didn't have to update or the runtime didn't have to update, we did have to update the SDK. So you can see here. This was the release when we did two or three and then very shortly afterwards, it was still dotnet core two or three.

A

We didn't have a new runtime, but you can see the SDK version updated, okay and so that it was because of vs and there's this some information that we're looking at adding to this page to make this even clearer so that you can imagine in the future. We're actually gonna have more detail on the left here that says, why did this release happen?

A

What version of vs is it in, and so it would be very clear that this release happened because there was a vs version that this SDK shipped in, and it would tell you what version it is. So you can go. Oh if I have vs fifteen point, you know four or whatever it might be.

A

That was the version that SDK version two one two was in, for example, okay, so this kind of is the decoder ring right, there's a lot of ways, different bits that get shipped and sometimes they ship inside other things, and it can be useful to know when did that happen and what did it align with and that's what this page layout is designed to solve. So I can scroll through here and I.

A

Can see all the releases 2:05 there's the SDK and for some folks may remember, the SDK went through this weird sort of versioning schism where they went from 202 to 1 and then from 2 1 to 2 to 1, 4 and then 2 to 1 100 uh-huh, as we introduced a new version in scheme to try and retcon this versioning, goodness that confused folks and so the rest of the 200 train is on a 2-1 SDK version. But it's less than 200 300 and 200.

A

300 is the version where it aligned again with the runtime with 2.1, and so we can go all the way back up at the top. So we can see that the last servicing release we did of 200, which was 209, which is the one that just came out. It was also a security release because it can contain the same fixes that we shipped into one and that SDK version was 1 102. If I go back to the 1 download page super get a rise time.

A

You'll see that the SDK versions all start with a with 300 and then when 2 comes out, which I might give you a sneak preview of in a minute. In terms of those pages, those SDK version will align, it'll be 2 to 100 the first version, so this was announced a while ago. I think we've talked about it before, but now we're really starting to see it all line up.

A

You know, as of when 2 2 comes out, and but at least now we can historically see what all the release information was for every release and what it aligned with so I'm, hoping like there's a lot of information here, I understand that, and there are versions that run on their own schemes because they have to because they ship in different things, but at least now there's a table that makes it I think a lot clearer than it has been as to what versions shipped with what and one of the lines with so I hope.

A

This makes folks a little. It makes it a little clearer, Hashem Dawson the question where's 204 at jump from 2 or 3 to 2 or 5 yeah. That happened a couple times in the past versions, were skipped or unified for reasons I'm not gonna, say there were good reasons. We hope not to do that. Again. We did one in 208 where asp net revved but dotnet core didn't and that just really confused everybody.

A

So from now on these things all ship together, they should always have versions that align according to some rules that don't change, and so we shouldn't see those gaps, hopefully moving on like reality, as we've learned a lot from trying to build a product like this, with lots of different layers that are sometimes version independently different products, and this is where we've come to right now.

A

As someone pointed out, angular went from version to version 4, because I had a very similar problem where they had different parts of the stack that was shipping in different Cadence's. That's their version together differently and that just caused confusion. They move back to sort of doing a line versioning so yeah anyway, but.

B

It's a good interview. Question you could say, have you used, you know dotnet core 204 and then.

A

Yeah exactly that one didn't exist. Well, you can say: do you use not NIC or to one they go which to one, do you mean t1, 200 SDK? Or do you mean to one? So the reality is, as I said, the first page is designed around making this. You know you generally don't have to worry about that part day-to-day. You generally just have to know I'm targeting net core 2.0 or 2.1 or 1.1 or 2.2. That's the. What gives you features.

A

The patch version is obviously important in order to make sure that you're running on the latest servicing releases. You have the latest fixes and the easiest way to do that is once it's in Visual Studio. Let's all your visual studio updates, if you are running ahead of where Visual Studio is because we haven't merged it in yet like where we are right now, then you just install the SDK.

A

That's the developer bit and you just come here and you download the latest SDK and you install it and then for your servers, you download the the appropriate runtime pack, you know the or installer or if it's on Linux, you get it from your package manager and if some windows, you click this button and it gives you the window, server, dot, net hosting bundle, I think it's called, and that's that covers lean done in a 10, the 9 and a 10 cases and then for the edge cases.

A

Obviously, you need to know a little bit more about what exactly you've done to compose your application and then what it is. You need to run on the target if you're doing self-contained deployment, which I mentioned briefly, that's all done at publish time. So that's all driven from the SDK, ok and then as off to 1. What happens is the SDK when you publish a to one application self-contained, it will find the latest patched version that the SDK knew about, and then it will publish with that version.

A

So to ensure that you get the latest fixes. You can control this behavior by the way. If you really care about it, you want to state your versions explicitly, and you don't want to get any of this kind of you know safe by default role for behavior, then you can turn it off, but we default to that to ensure that people are generally secure by default when they perform their normal actions yeah. So that's all that I alluded to there being two to stuff.

A

There's a couple things where we're building the two one: three servicing right now. So, as I said, the latest servicing release was two one. Two down here. You can see it's the latest patch version of two one: that's going to come out in August sometime by this time next week, or maybe a little bit later, I hope to have links to share with folks who want to try that out early a little bit like we did the last time round, so you'll be able to go to a github page.

A

In fact, if I go in like spunk around right now, if I go to dotnet I think I have to go to core. If I go down, I'm.

B

Really curious, as you're looking that up did we have like how many people are actually use, how many people test it out those early release, some.

A

Okay, we didn't have great stats, like I mean cuz, their links were just posted on a github page right, that's right and I tweeted it but I know some folks try because they replied, but you know we know this time around it'll be more like using Knightley's in fact, it'll basically be using Knightley's and which are gonna clean up the acquisition experience for getting them and make sure it's clean.

A

So yeah I mean it's. We know some folks use Knightley's right. We want to make it easier for folks to use denied, leaves and be able to do it cleanly and uninstall cleanly or make sure they land on the right version when the real one comes out, and so that's what we're gonna we're working over in the next weeks before we share these links, but in the meantime this is kind of what it looks like right now. You can see here there's a link under dotnet core releases.

A

It says download the latest SDK, that's two one, but there's daily links, so you can see daily preview builds and daily servicing bills. So preview builds means the next feature release. So this would be 2.2 in this case. They are very useful right now, I, don't think we actually have I think we would like.

A

Literally this morning they were saying we were hoping to have our first candidate build for that today, and our current plan is to get our first sort of easy-to-use preview out in early August, which that's like three weeks away servicing if I click on servicing builds. You can see here that there are various trains right, so this this this page isn't up today, it's being up to date, updated right now, 2 1, 3, X X. That's the SDK release right there, as we just discussed on that page ahead.

A

All the the matrix of information, the next servicing release will actually take place after the next vs update, and so it's going to be 2, 1, 4, X X, because that last version of the SDK versions, whenever anything changes right, whether it's a runtime update cause of a patch or a feature update, because a new release of V Escamilla came out. This is when this number changes so because it's a feature eliska's, 15 eights, coming out soon.

A

This will go to 2 1, 4 and I'm, assuming 2 1 400 will be the one in 15 8 and that will contain 2 1/2 of the runtime I believe and then 2 1 401 will be the first servicing release and it will contain 2 1 3 of the runtime. Ok and again, all that information would be available on that release page that I showed you before so within the next day or so.

A

We hope there will be another bullet here, which is take me to the daily builds for the 2, 1, 4, xx releases and then you'd be able to like I said next week. I'll be able to point you here and you'll be able to go and try a daily build of the next servicing release. There's a lot of fixes in 2, 1-3 and so we'd love to get folks to try it out early in a controlled fashion. So they can give us some feedback if there's anything that they consider blocking.

A

We think we're done, but we need to get some verification before we release it next month, and so that's what we're working towards right now, yeah! So for 2, as I said, we're met where we're targeting right now that the to preview builds that what we're gonna do for 2 is we'll do 3, previews I, think I said this previously I didn't give any dates, though we're hoping about August 7th for preview. 1 is kind of what we're penciled in right now and from the a span outside.

A

We actually hope to land the beginning of a few of the things we're working on. So we hope there'll be a health checks, implementation that people can play with in the first preview there'll be changes to the API. You know all the improvements to the API conventions experience the API controller stuff with the analyzers to help you do that correctly, so you'll be able to then plug in swashbuckle or n swag, or something else that reads the API metadata to produce your swagger document, and that will just be you know much richer.

A

So our open API documents without you having to write any more code, which is wonderful. What else do we have? We have a signal, a Java client that is almost functional, so that we should be able to see something there in preview, one that you could try out I'm, probably forgetting something: we've started: the investigation on the authorization, server work, I'm, not sure, they'll, be much to look at in the preview one timeframe.

A

What else is there? What else was in our one announcement? I could just go and look, and they did you do if I go to announcements right announcements to announcement. Is he okay schedule?

A

I look I actually have the schedule there look at that in the months anyway, if you guys in the services we talked about that open EHR generation, talk about that I'll dispatcher, which is the new global routing system, so I believe that will be in preview on as well we're just arguing over what we should call it right now, because a lot of folks don't like the dispatcher name, um so that would that should be available in preview. One.

A

The only thing that's open is whether you'll be able to set up MBC to use it in preview. I'm, not sure whether that will be ready for preview one or not all the repple I think there'll be a preview of the repple in preview one. So you can this new global tool experience that lets.

A

You sort of you know code against an active API and get like nice commands in the command line like LS my API, and send test queries and all that type of stuff from the command line, which is pretty cool, not sure we're going to have much in the API client generation. We're trying to introduce this new idea of a service reference in him in msbuild, so you actually see it in your project file.

A

Like your project reference, you know, package reference framework, reference, you'd, have service reference and that's what you point in a swagger doc or you point and another project that produces a swagger doc and then you would plug in a code generation a tool that knows how to look at that information and produce your client, so that cogeneration told could be n swag.

A

It could be order rest from Microsoft or you could write your own one and so we're looking at that and we'll see how much of that we land in preview, 1 or or if anything otherwise, they'll be something in preview. I spoke about, L throws Asian, so it should be summation to be 2 stuff landing. The beginnings of a should be anyway. It's nowhere near complete yet, but the beginning of that should be available in preview 1.

A

The imp Rakhine cm a support will be in preview 1, but you'll need to wait for the first preview of the following vs update before you get the vs experience, because it requires changes to the is Express hosting model with the project model and that and that was not gonna make into fifteen eight he'll be in the preview of the next race. But that won't be too far after that just a couple of weeks and that's it that covers everything. I think we were talking about good signal as a sorry yeah. So that's all coming.

B

Hisham asked if you can talk about the new route pattern: I, don't.

A

Know what that's referring to sorry? What's that the new route pattern.

B

A

Panthers been introduced, I, don't know what that is. Sorry, no all right. That's introduced, if that's a type I'm, just not aware of what it is. It's it's too low-level for me to know what I haven't seen. Yet, if anyone else has any questions, I'll Maksim here is asking about, is in propio, that's the ANC em in proc stuff. So the hope is my understanding is that's functional and working, and so that will be in the first preview. It just that to get it working as part of f5 and vs.

A

It requires four years update, so that'll be in the first preview of the next vs, which will be very shortly after we release, and you know, towards the end of August or something so yeah so that'll be there as well I'm.

B

One just kind of minor question the download page I was used to and and maybe it's not relevant anymore, but I used to look there also for docker instructions. Oh.

A

Darker stuff, yeah, that's a good point. Let me go back and have a look, so that would be well that's interesting, I. Actually, don't so I guess we don't put. We don't actually point to the docker stuff from here. I mean.

B

There's plenty in the darks right, no.

A

I mean obviously most people go to docker hub right, so like it's all on on Brown official docker hub feed, that's a good point! No, it would probably it probably warrants a link if nothing else. You know just a link off to the docker hub from here for the images like both for framework and core and it's true of Windows, Linux and Mac, and so yeah. That's good feedback.

A

Yeah, there's nothing yeah, okay, we'll make sure that we get that fixed. That's that's fair point: cool cool.

B

A

See other questions.

B

A

B

Her I only the.

A

Audio works, fine on the stream. Now at least that's what golden heirs are saying, but if people want to just write at the end now say in the chat, whether the audio is working for them well or not, because I'd like to make sure that it certainly you're quiet in my headphones I'd like to be able to fix that at least and then we could because I turned you down here, but maybe that was the wrong thing. I should have kept you up and then I should could have just turned you down in the stream.

A

Then I could have at least heard you at the right volume. So I think it's a couple of things with the audio that we need to figure out. Oh there is a question: is there going to be a setting to switch in vs to switch between is in praça da de prague for the NCM module from brian?

A

Actually that setting is in your project, so you do that on a project a project basis. So our intent folks are saying the audio was great for them good. So the intent is that new projects to two projects will default to in proc one way or another, whether it's something that's in the template or whether it's you know inferred based on the TFM, your your ironing whatever and you can migrate, because because the in proc requires a new server in your application right, so you have to actually be targeting to to get in proxy port.

A

So that's if that's not clear, so you'll need to ensure that you're actually running on to your app targets and then you should get in proc. You can always go back to add a proc. If you want to there's a flag that lets you change the hosting mode, but the default when you're on is intended to be in proc. So anyway, the short answer is yes: you'll be able to change it, but it's per project rather than in just vs. In general, Oh someone asked about bootstrap. Sorry, I didn't mention anything.

A

I forgot all about it. Yeah in we are adding we're basically moving the templates to bootstrap, so I was that was actually in my settle link. So I was going to show you, so we we're taking this opportunity to simplify the template as well, so the application template the one that has bootstrap rather than the template that we have today, which has like you know an about page and a contact page and a home page with a carousel and all that stuff on it. We're just going to simplify it all. So we can wait.

A

We've chosen this template is the basis as in this sample, which is like white on white with a little shadow, but it won't have any of this content. Basically just says you know, welcome to your new app and then, rather than this stacked footer down here, it's going to use the traditional sticky footer, which is this one here all right. So this 40 here that always goes at the bottom of the page.

A

If there's not enough content to push it down there, otherwise it just Scrolls, underneath everything, oh sorry gets pushed to the end of the content. That's what we're doing for our sort of default page. So the reality is it'll be bootstrap for it'll be simpler than it is today and I think it looks a little cleaner than it does today list. It looks a little bit more modern.

A

The template itself isn't where the majority of the work is most of the work is actually in updating the scaffolding system and the the new identity packages that bring all the UI with them. You were the older, wiser UI inside, so you get your login page and your management page without having to have it all in your app.

A

They all obviously have to be updated to support bootstrap for as well and so I believe that, where we're aiming to have at least the template and this and the the project template and the identity packages updated with bootstrap for support in preview one, but the scaffolding support may lag behind and not land until preview too. So that's the current plan as a vet.

A

I've got all of the questions here. Just to finish up, Raja was asking any plan to revise the localization. Api is no there's no plan to do that right now. It's just not in scope. 2.2 was a smaller release. We focus on a set of things and localization api's or changes was not one of them. We basically prioritize based on where we got a bunch of feedback, so yeah Andres is pointing out. Yes, dotnet new still contains bootstrap 37, and that's why we are doing the work now to move to bootstrap for all right.

A

I think that's a show. Oh.

B

So if just for completeness there was a ischium just tweeted the thing about the route pattern he was asking about. Oh.

A

A

Context that will magically make me know what it is. I, don't.

B

Know it's a pull request from Ryan I have.

A

No, all right, no I'm, sorry I'm, not aware ask Ryan what that is.

B

A

Plan was to try and get the whole MVC team on to this show right, you're.

B

Right so I'm out on vacation next week. Otherwise, although.

A

I'm, your friend all right, well, maybe I'll, try and want to show early next week, assuming I haven't, got a conflict and I'll see what I can t up for the next year. We have never Tuesday morning show in a few weeks actually I think you're handsome ends back next week, he's at oz con this week, but yeah we'll see if we can get handsome in an eye on early next week for the other time zone and we'll see what we can tee up. Okay, cool. Let me see if I can make this live.

A

Dzo is the video I, don't think so it's kind of work, I, really I, don't know what I did. What's this oh I didn't work at all I resize, something else.

A

Okay, all right we might just have to give up but I, don't know what I just did I just resized the wrong thing. Where is it? Oh there? It is okay, see if this works nope still the wrong thing, no hope all right. We're gonna have to work on the dramatics email. Last week it worked pretty well, but that was on my machine, so we're going to have to figure out how to do it on this machine. So we will just sign off and we'll see folks next week.

A

You know what, though, before we sign off sorry and I have to show everyone your face, because I haven't seen, you look, look there's both of us on the screen. Now they can see both of us see you everybody, but.

B

I can't see you I'm just.

A

It's all good trust me.