.Net Foundation .Net Community Standups, 2 Jul 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: ASP.NET Community Standup - July 2nd 2019 - Meet the ASP.NET Docs Team!

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-02

A

All right hooray, we're live. This is this is an exciting show. Today we have a cast of thousands here, we're on with the docs team that writes the docs for asp.net.

A

So so, thanks to all you folks for jumping on and and it's exciting too, because this is a distributed team, and so we have people from all over the place, so I'm going to jump into the community links and then I'll, let you introduce the team, introduce himself and and then kind of show off what's what's in box and what developers should know about it so Tom can you switch over to my screen and I will do this? The sharing of the desktop.

A

And here we go now here we go and let me know when you can see this.

A

Yeah, okay, do you see it? Yes, there.

B

A

All right, so we first of all from Dominic we have. This is kind of cool. This is a take on access, token management for asp, net core and also introducing idle asp net core. So is you know, they've been doing a lot of work with things like token management and working with asp, net core clients, and so actually introducing this identity model asp net core allows you to in one line retrieve a token, so this is actually doing a few things.

A

It uses an extensible storage mechanism for the tokens it can check for a token expiration and refresh if necessary, and then you can actually retrieve the token back to the caller. So this is a new project that they're announcing but exciting, well, cool. All right. This is really cool. This is Shahid has been doing these mega series.

A

So here this is his 26, so he's through the alphabet on his through the alphabet, serious a through Z on asp net core, and so this is this one is on zero downtime web apps with asp net core, and I'm just going to flip over to make sure see. If we have anybody saying they can't hear anything, alright, it seems like we're: okay, okay, so zero downtime asp net core.

A

So some of the things he he looks at is some stuff like using staging slots, and you know like deploying using those staging slots using also traffic manager for availability and then some other things, my laptop's working hard to keep up here, so I'm, actually not in my home office today and so I'm on my laptop and and my laptop is having fun with video and everything. So anyhow, he goes through.

A

You know: CI CD, like I, said deployment slots which is a must have or for you know, zero downtime and then migrations and then finally another feature that we've talked about recently, which is feature plagues, and so this is. This can be really useful for doing things like having a fee not requiring a new deployment to turn a feature on or off. So this I've use this in a lot of applications.

A

Where we've, you know, done kind of a quiet deployment of a feature and then just toggle it on when it's time when it's actually ready to go, live, oh cool, all right, baby, Grady gaster with configuring, a server-side blazer app with Azure app configuration, so some neat things here, working on multi-org authentication. So here he shows setting up as your ad and along with azure ad, some of the neat stuff with integration, for instance the app configuration and I configuration integration.

A

So so you know built in with the azure app configuration you get packaged then some other things in here showing off waiting for my screen to refresh here, dynamic reloading. So that's also that's also pretty cool. So it kind of wraps up with that neat stuff. Okay, NDC Osler, 2019 videos have started going up so at the end of this I include all the links and I'm, including this link to the entire playlist.

A

As of now, I only saw two ASP met, related ones that had gone up and those are first of all, Kay Scott Allen, with his advanced Azure app services, so I always loved his a sure. Deep dives- and this is going through a lot of features and kind of in-depth as your app service stuff and then another one is.

A

This is from another member of the identity, server team, so Brock Allen, going through securing web api's with JavaScript and spa apps, so great stuff and again watch that playlist, because there are other talks from NDC, Oslo I know like Damion, Edwards and David Fowler and there's several either Wednesday is peanut related, so keep an eye out for those all right. Heather downing writing on top five DevOps automation tools, dotnet developers should know so a lot of really good stuff here.

A

First explaining you know why you should invest in DevOps tooling, you know, don't just push to production or even get pushed employ. It's it's useful to you know, understand like see, ICB and and different tools available, so so going through. Those there's also some things in here, like sequel database versioning on different sequel database tools, so nice roll-up of that and then code analysis, and you know just kind of wrapping up with you know how to learn more and why it's a key skill.

A

So great kind of overview, post all right to tweets from David Fowler he's basically blogging via tweet now, but they're really good ones. So this is a new feature in asp net core 300 support for w3c trace context. So the way this works is by adding just one line activity default, ID format and setting it to w3c.

A

Then this these headers are inserted. So there's there's two that are included the span ID and trace ID. So what this allows you to do is trace things all the way through a request and see them on the client so allows for kind of much more in-depth tracing one other one from David Fowler. So he wanted to go through and make a tiny microservice.

A

So he got to 22 lines of code and posted it as a gist, and so this is it here, he's got his is CS proj and just a few lines of code, and this is a fully async micro service. So I thought that was pretty neat and these are all in in this list that I'll be posting, so this will be in the show, notes and I'll tweet it out and and put it in the chats and I am done with my links.

A

So let's hop on over I will stop sharing and and let's, let's meet the team. So would you folks mind introducing yourselves.

C

Sure, let's start John, so my name is Scott Eddy I've, just another Scott at Microsoft, lesser Scott, working on the ASP, not asp.net core Docs with the folks on this call, then, with the team now for about two years.

C

I'll toss it over to.

D

Cam now hey I'm, cam, Soper I'm, also on the asp.net Doc's team specializing in our Microsoft learning content and some Azure SDK content. I've been on this team for about five years, I've been at Microsoft for about seven had based out of Kansas City Missouri.

B

I'm Wade, Pickett and I've been at Microsoft for about 14 years now and new is a Content developer for asp.net core kirlyam working on some ms learned modules for razor pages and.

E

I'm Tom, Dykstra and I've been on the a speed and a team for off and on for 11 years measure for a while.

A

Great great okay, so I had asked if, when you I think Scott were you gonna give just kind of a quick look at docs for people that aren't as familiar with them. Yeah.

C

Why don't we start there I'll share my screen.

C

And let me know if you can see it I see you're.

B

C

Cool so I guess where we'll start is just talk about the dock, set that all of us on the call are spending the majority of our time in and that's what you see here on the screen. This is what we would refer to as the conceptual dock set for the asp.net core product. One thing, I guess, I'll start off with that. A lot of folks often miss, but it's very important is up in the corner of the page.

C

We have this version, selector and so you'll notice that you know if you're interested in docks for the latest preview version 3.0, you could navigate there and you'll probably notice that the table of contents changes based on the version. That's selected from the picker, so I'll change that again back to two two, and you see sure enough, there was a little bit of a shuffle there in the table of contents.

C

As far as contributions to our docks go, that's probably the next most common thing we hear about. You know how how do I get started? You know, maybe there's a glaring mistake on this page here. How do you go about fixing that? Well, you know if it's something as simple as maybe the word thaw appears twice.

C

We see that happen a lot it's easier than you might think you could actually go up to the top of the page and there's an edit icon here, if you click that this is the simplest way to contribute, takes you right into our github repository and all of our Docs that we were looking at on.

C

The rendered page are open source out here in this repository, so it's just github.com, slash asp net, slash asp, net core Docs and from here what you can do is click this pencil icon to edit the file and just fix whatever mistake, it is so you know, maybe maybe there was some mistake up here.

C

Maybe instead of you, can we want this to be you can't terrible example, but assume you're, making some simple change like that, and what you can do from that point. Is you could preview your changes by clicking that tab? You get a nice color code at DIF here and, if I toggle back to the edit file tab, we have the opportunity down here at the bottom. To just include a very simple description. You know what is it that I'm changing here.

D

C

Maybe I'm just changing can ii can't, and it's here where you would have the opportunity to you know, create a pull request for this. Now your options are gonna, be a little different here. I have commit access to our master branch. You would not see that first radio button at least I would hope, not click the commit Changes button and what would happen at that point is under our pull request tab.

C

We would see your pull request listed there and.

B

You all can see these two. If you want to see what everybody's submitting comments, conversations that are going on with any of these issues live, you want to join the discussion. It's all right here, yep.

C

So that's kind of the simple contribution workflow now.

C

Let's say you want to submit maybe an entire dock for a feature that's coming out in the three oh release, or maybe you want to add a couple of paragraphs to a dock, to clarify something the workflow there is different and what we would actually recommend in that case is go back out to the home page of our github repository if you scroll down and look at the contents of the readme file here, what you're gonna see is a link to to what we call the contributing guide.

C

Now, if you click that this is gonna, tell you, okay, how do you make a more complex submission to our repository?

C

One of the tools that you're going to see mentioned in here is something called the Docs authoring pack, which is an extension that's available for visual studio code. Definitely recommend doing that and you can think of that extension is really like a kitchen sink of an extension, a monolithic extension that brings along other extensions for the ride. One of those extensions is a really nice markdown, linter called markdown lint. You get basic spell-checking capabilities as well as some templates that you can start with, if say, for example, you're authoring, a brand new article.

C

So again, that's called the docs authoring pack that is available out in the extensions marketplace, and here it is here and just to make sure that contributors find out about this extension. You know, maybe they don't see this contributors guide, what we've actually done, I'm gonna flip over to vs code.

C

Can you guys see vs code on my screen.

B

C

Let me try sharing a little differently here.

C

Screen one all right now: can you see it yep cool, so one of the things we've done is visual studio code actually has a way to recommend extensions within a work workspace, and so what we've done is you'll notice, dot, vias code folder out here in our repo we've created this extensions that JSON file and what you're seeing here is it saying hey when someone comes here? If they do not have this Doc's authoring pack extension installed, let's recommend that to them.

C

That's really the purpose of the file that you're seeing here, and so you know what that might look like. Let me go out here and I will actually uninstall that.

C

All right clothes, vs code, I'm, actually gonna launch the docs now from the command shell. So you know vs code is our recommended tool for working with the docs. It's just a first class markdown editing experience.

C

So what you'll notice now down here in the corner? We get this toast notification that says this workspace has extension recommendations. Okay, let's see those. What are those recommendations? I'm sure enough? Docs authoring pack is a recommended extension and so from that point just click install and boom. You have the extension, because you know we recognize that not everyone is going to go out and read our contributors guide, so we'll hopefully catch you in this way. If you don't read that guide once you have this Doc's authoring pack extension installed the next place.

C

You'd want to look for. A significant contribution here is to go to our asp net core folder in the root of this workspace folder, and what you're gonna see here is really a folder for each collection of features within asp net core that we are responsible for documenting and so, for example, if you go out to let's go out to our docs.

C

So docs asp.net is the vanity URL you can use to get to our docks. Let go out here and notice if you click get started'. For example, you can kind of get a clue as to where to look in the repo by looking at the URL up here, so asp net /, kohler or slash getting started.

C

If we go to our docks, there's a getting started, folder chances are. The dock is found there sure enough here it is right here, index markdown file and what you're seeing here now is the raw markdown representation of the rendered page. That I was just looking at out on Docs that Microsoft comm, so your typical structure for a markdown file is gonna. Look a lot like what you see here up at the top of each markdown file in our doc, set you're gonna see a bunch of metadata which to an external contributor is meaningless.

C

That is fine. That's that's! What us lovely folks here are good for helping you with. We will help you figure out that the rest of it is just built by working with our team to create a content outline. So you have an idea for a doc that you want to write. Ok, let's first, have you create a github issue and we will collaborate with you to build out. You know sort of an outline for this doc.

C

What that should look like, and that's really how we arrive at the headings in the markdown here so like unlevel, sorry line 10, that's where you see a level 1 editing, that's just the heading for this entire doc that we're looking at you'll notice other headings within here. Like here's, a level 2 heading, there's another one and again our team would help you come up with you know. What should those headings be? Do they conform to our style guide that we maintain.

B

As you're doing your outline think a little bit about who your audience is if you're picturing, that this is for folks that are brand new to asp.net, core or they've, been around asp.net core for a long time, maybe they're not even new, to the particular collection of features that you're going to talk about that, there's something in particular, now they're put together that you're covering or a very specific advanced scenario.

B

So if you, let us know what your goal is and who your audience is that can help us kind of narrow down the outline for what you're, covering also we can keep in mind if we've got something else in the works going on that, maybe you could collaborate with that's already going on yep.

C

Yeah I think that's the big thing. What Wade was just describing. We want to make sure that you're not working on something that maybe someone on our team is already working on.

C

You know no need to duplicate the efforts, if, if you have knowledge of something that we are currently working on, let's collaborate because we're going to end up with a better quality document. In the end, we realize that we have a very strong vibrant community out there and we really like to leverage them wherever possible, because.

B

The reality is.

C

That I mean the reality is we're a very small team.

B

And then there's so many ways you can contribute to I'm sorry to interrupt you there's good, oh so, when we're gonna, when we or anybody the communities creating a new topic will suggest an outline of what we're gonna cover. You know the approach and scope audience and you can be involved right right there in the discussion. You'll see the issue pop up. You know if you're interested in in that area get in the discussion about well, you know it does. That seem like the right outline are recovering the right scope approach.

B

There is there a different code? Example, you think it would work better and then, once the topic is in in draft form you you can help with reviews of reviewing that topic and so anywhere along the during the process that it's great to jump in provide feedback. We also have projects listed up there. You can actually see what projects were working on. You can see milestones you can see. What's going on for any particular sprint, we do our sprints or monthly just each month.

B

So all of July is a sprint, for example just for simplicity sake, but you can see what's going on and if you're interested in a berry good. Let us know.

B

C

I just pulled up what Wade was talking about with the github projects we like to be very transparent about what we're working on you know so here, if you come out to the projects tab in our github repository you're gonna see exactly what paid each of our sprints, so June 2019, you can click in there and you see. Okay, you know, we've still got to update this one, but you know what were we planning to do in that sprint? What will we address next in that next up column?

C

What's in progress and what has been merged to master and published to live? You'll notice that same structure for each of our sprints? The other thing we like to do out here, which we still have to do for our July sprint, is identify. What are the high level goals to tackle in that sprint, and so for the June sprint, one of the big items was getting out new content for the asp net core 300 previous preview, six release. That's that's what you see listed here.

C

Another interesting thing, though, that you see there is Microsoft learn. This is something that many of us have been spending a significant amount of time on, so it's not just the conceptual doc set that I was showing at the beginning of this. We also spend a fair amount of time as of late in the Microsoft Learn platform.

C

I actually have that tab open over here.

C

So if you were to go to, let's say our docs landing page I'm going to point this out, because it's easy to to miss this up at the top there's this banner introducing a new approach to learning and if you click start learning. This is how you find this Microsoft Learn platform and we have a whole bunch of content out there. I want to say almost 400 courses or what we call modules now and it's categorized by persona.

C

So you you identify ok, what is my role as a student I'm, a developer for example, so you would select that from the drop-down and over here under products, let's get to the good stuff ASP neck core. This is where you're gonna notice that we're starting to build out a Learning Path of modules, cam and myself have produced two of the modules that you see here feel free to jump in cam.

C

If there's anything you wanted to point out here, we have an introductory Web API module that consists of eight units, so you could think of a unit as really a page or a step within the course.

C

We've also got an EF core 200 level course out there. So the thought is, we would have an entire Learning Path out here. That would consist of about seven to eight of these modules when it's done. The really cool thing with the Microsoft Learn platform is the gamification aspect that they've introduced so say, for example, I decide to take this create a web api course.

C

If you complete this course, get all the way through the exercises and the reading material and complete the knowledge check. What you earn. Is this awesome dotnet bot badge? That's your achievement badge as proof that you successfully completed this module once our Learning Path is out there. There would be another achievement badge that you would earn for completing all of the modules within that path, sort of think of it as the the trophy that you get at the end. Hey.

D

Scott I've got my I've got my profile page up or I can show my achievements really quick. Yeah.

C

Let's I'm gonna stop sharing my screen and then you share yours sure thing.

D

Let me know when you've got it all.

A

D

um Yeah this Scott was talking about the gamification, so they actually it's a lot like your gamer score on Xbox or Playstation, where you, you earn XP per unit that you complete and it contributes to a level and you level up as you go.

D

But when you finish the modules like Scott said you get these nifty, these nifty badges that you can that we feature the dot map bots on our asp.net badges kind of the the mascot one other thing that I'm going to show while we're here Scott showed the first page for our web api module I've actually got our EF core module in progress over here and the the thing that should hopefully jump out to you right away is that these learned modules have the capability of being interactive right.

D

So it's not just we're going to tell you to go. Do something and you go up and do it in Visual Studio. We actually have a text editor in the browser here, where we can here I'll jump down to the last last step on this. This one where we can perform the steps with actual code and oh I should probably say before I, build and get that instant feedback to see if it built successfully.

B

You can also use that to add new nude files in there. So if you're going to add a class, for example, it's pretty pretty robust.

A

So this is a hundred percent in the browser. Then.

B

C

B

All groaning out there is your yep.

C

What we wanted to do was create a frictionless learning environment, so this is in a boon to VM running up an azure. Many of the CL is that we would use, as dotnet developers are already installed there. So the azure CLI the.net CLI and then you've got a bunch of commands that you would use for other various purposes like curl curl is installed out there.

C

You know a bunch that I can't think of right now, but really great for just kicking the tires. You know if you're a asp net core developer and you really want to explore what is this a sure thing all about it's a great way to learn.

C

You know sign up for a free accounts, there's really no obligation for you here, fire up the the course that cam was showing off there and just you know, tinker in the cloud. Shell and I'm gonna.

D

Actually show that again really quick um the.

D

Like Scott said, the one of the great things about this environment is that there's a a resources available to us, so as a dependency for for this module, we actually set up an azure sequel database. Let me try to remember out here we go here's the verified that no, we haven't done those steps. Yet when it go back, we can got a got. An alias set up here in Linux were in the bash prompt here where we can just send sequel queries to our Azure sequel database.

D

Now it's an empty database, so there's no tables but we're hitting a live a database. That's not not even it's, not even provision to my Azure account its provisioned as gratis as part of this learn environment.

E

Can mention levels? What does different levels do bragging.

D

A

Hey Tom, yeah I, don't know if you see it that down in the lower left corner, there's a thing with a magnifying glass. Yes, and if you click on that it'll go away, it's a no, not not yeah down there. Let me see I'm yeah.

A

So there's like the and I I, don't know if I'm, seeing on the time delay or whatever, but we like down in the bottom left. It has that like graph with the magnifying glass thing and- and that goes away when you click on it- yeah, okay, cool, it's not going up. Oh all right, then. So there was a there.

C

Was a question in the chat here? I want to make sure we get to the question was so what if I already deploy and use Azure do I get badges?

C

Unfortunately, no I hate to be the bearer of bad news, but you would have to complete our modules here to earn those badges. Oh.

A

There was another question going in YouTube discussion going on in Luke's been answering to but question on. How do you like, since the docs are version dependent? How do I see just what's different between two versions? You know so like, for instance, between asp.net Core, 2, 2 and 3. Oh.

C

So as of right now, the way we manage the differences is we I'll actually share my screen here to show how that's working.

C

So one thing I didn't mention when I was showing off the mark down here in vs code, is that we actually have custom markdown extensions that we use. This is an example. What I've highlighted that's a custom? Markdown extension that's been created for Docs that Microsoft comm. The reason why I mentioned custom markdown extensions is that's actually how we are versioning our content. So let's look for an example here. If I go to search, we use what we call inline monikers.

C

So here is an example in our environments, dock and what you're seeing I'm gonna highlight just to make it easier to see everything. I have highlighted the content within those you know triple colon markers will appear only when asp net core to two or greater have been selected from the version selector. So you can sort of think of this as like web programming, where you're you're toggling the display of a div div tag. That's really what's going on here.

C

So when this is rendered, docks is saying: if someone has selected to 2 or 3 o preview from our version selector, the text I've highlighted here should be displayed. So that's how we manage our version differences now, as the dock set matures and the product matures for that matter. We may come to a point where this versioning approach becomes unmanageable and we might have to take a different version approach. So our docks infrastructure team has a couple of other approaches. We can take as an alternative to this inline versioning strategy.

C

One of those approaches involves duplication of content, which we were hoping to avoid, which is why we haven't gone down that path. Quite yet, with that approach you would do. Is you'd really have one folder perversion in the product, so in other words, we would have a two-two folder with the entire dock, set a 300 folder with the entire dock set, and so you can start to see where that would get thick real ugly in a hurry.

C

So I hope that answers the question in.

E

At the top and the metadata you can show that.

C

Yeah thanks Tom I forgot that so line 5, which I've highlighted there. What this is saying is hey this environments, dock that I'm looking at here should only be made available in the table of contents. If 2, 1 or greater has been selected from the version picker and.

B

This is an item that that we can help you out with, if you can, if you're contributing in- and all you need to, let us know is this is the version you intended it for it. So when you're testing it for and we can help you out with them, it's.

E

All kinda causes confusion because things disappeared from the TOC and because of the version.

B

C

Speaking of the TOC, you might wonder: well, where is that stored in the repo? Well, it's actually, if you look in the asp net core folder, there's a TOC yeah mol file.

C

If we, if we had audio I'm sure there would be groaning right now over.

D

C

Did before I groaned.

D

C

It's it's yeah Mille, and the reason why I point you at the yellow file here is you're, not gonna, see any any kind of versioning handled in the TOC.

C

It's all within that individual markdown file, so in other words, if I were to search for that environments, markdown file in here there would not be looks like it's this one here notice, there's nothing here. That says display this only four to one or later, within that dock, that you would find that information.

C

So this UID value here fundamentals, / environments- this is think of it as like a gooood, it's the unique identifier for the dock. So this text, this is really a key value pair. This text is the key. The value is just pointing to that unique dock, so fundamental / environment, which means, if I go to my fundamentals- folder environments, it's this UID here on line 9! That's what that value is.

A

Okay, so another question that Hashem asked via a via Twitter was support for localization. Any kind of you.

D

A

On ongoing or future support for localization.

B

As far as localize contributions, yeah or okay, yeah, okay, that's okay- that is a very good question on I. Can give you a little bit of background on on generally how things are localized, but I, don't think I'm the person to answer we're contributing that way. Just now I, so there's some live people that will actually touch the docks when they're being localized, but a good share of it is is essentially.

B

Machine, so the the contribution system we used to have folks would then contribute on the other end of that after the dock was already created, but not created to begin with to start with. So if they wanted to update it, for example, they had a system that I honestly don't know I can't say how it works at the moment. Is there anybody smart to date on that one, or is that one we're gonna have to come back with cuz I know it changed I, don't know how it is right now, yeah.

C

You would know better than me: wait. Oh.

B

C

B

That I, that I, don't know I'm sorry, it has changed, I'm, not sure exactly how it's working right. Now you will. The localized files are in a repo and generally they'll do a the runner localization automatically once we have our content and every once in a while and take them in batches content that that has already been translated once for phrases, they'll rely on a phrase database of translated pieces which will be dropped in and then occasionally people are reviewing, but I I can't tell you beyond that. So that sounds like that's one.

B

We need to provide a presentation have and have something ready to go to show you next time. Perhaps serology I don't know. I can.

C

Show where the localized repos are on github, you know how to find those so I'll share my screen again. Yeah.

B

I'm not sure if folks are allowed to contribute directly in those or or not I, honestly, don't know.

C

Yeah I believe they can. These should be public repos, so within the asp net organization on github, if you just search for asp net core dot docs, that's the the english version of the doc set that we've been looking at, but below that you'll notice. There's 13 other search results here, representing different languages that we translate into those repos are found here. So if you're interested take a peek, we do occasionally get pull requests from the community in those repos. mmm Okay,.

A

So another question is a lot of these. A lot of these tutorials and Doc's have some pretty in-depth code samples as well and but they're kind of been one giant repo right. So if I want to get to a code sample is, is the guidance to kind of clone the whole repo and grab that folder or what? What do you do? It's.

E

Been a long-standing problem that is recently sleeping ends. Okay, there.

C

Isn't it sorry there isn't an issue underway right now, internally, it's being piloted, and that is aimed at improving that problem. That's being described, I, don't know how it would improve, but it will that's been a long-standing issue. We've been hearing about for at least the past two to three years, but.

A

Okay, but this like going past that problem, then I forget because I've been also monitoring the chat. Did you show the repo? Did you actually show some of those sample projects because I think that's a good resource. A lot of people don't know about yeah.

C

Let me share my screen here and I can show you the convention we use in our repo for sample apps. We.

E

Might also show when they have a lot of different snippets and preprocessor directives, that you can switch the.

C

Logging app yeah, okay, yeah I'm, less familiar with that one, but let me find a good example to start with okay, so here's a great example if I were to expand the fundamentals folder in the root here under asp net core and then go to our di dock dependency, injection you're, going to notice in the root here, there's a dependency injection markdown file and for samples that correspond to that dock. We typically create a folder with the same name without the markdown file extension.

C

Obviously, but it's within there that you would find a samples folder, and in this case we have two different sample: apps that go with that doc: a one dot X, meaning asp net core one dot X and a 2 dot X. Now when 3oh is released, chances are we'll, have a 3 X folder out here and that's how we that's, how we've been creating samples and organizing them in this doc set.

C

Now. Is there something in here that you wanted to point out tom yeah.

E

A lot of them, they have different scenarios that they want to portray, and you need to change the code.

E

By using preprocessor directives, yeah.

C

I I can't think of an exact location of one of those but yeah.

B

C

So, let's look into logging index index samples notice. The same pattern has followed here: we've got a samples folder one dot, X 2 dot, X folder within.

E

C

Yes, there we go line. 1 is what Tom's talking about I believe right.

E

So each one of those is a different scenario that you can try out so.

A

I think this is really helpful and something that you know when people are asking me for samples or a lot of time when I'm showing off a new feature that they're, you know it's just freshly in the docs. This is usually one of the best sources to find some actual good working code. That's very feature related, you know, so it's instead of hey here's, the neat app I threw together it say: here's how to use this specific logging feature or something like that. So one.

C

Other thing you're going to notice in a lot of our sample apps is heavy use of Regents. Well, you know, well, you know, there's a lot of debates in the community over whether regions are good or not. This is actually a great use case for regions.

C

So, typically, what we do is we'll pre, Frick prefix region names with something like snippet underscore, followed by a brief description of what that code is, and this is how we import specific code snippets into our Docs, so in this case this region, starting on line 23 ending on line 32, some doc out there.

C

So our logging doc it looks like, is most likely importing this code snippet, and so, if I search for that region, name.

C

We'll see how it's.

A

Being used so that solves the problem of keeping the docs and the sample code in sync. So.

C

You don't get one yeah, that's another strategy, otherwise.

E

You bring it in by line number in line numbers change too, pretty pretty frequently.

C

Well, so yeah, if you were to search out here, it's something like name equals in our or even better snippet.

C

This is our strategy for importing code snippets into Docs, so we have what's known as dev Lang's when we import these and I'm, not sure why my search isn't working.

C

Let's try one more thing here and.

C

There we go so I mentioned something called dev lang. Dvla ng, dev lang refers to this language identifier that follows code. So what you're seeing here in line 609, for example? This is where we import a code snippet into a doc, and this just happens to be a razor view file. It looks like a blazer razor file extension but notice here on line 609 the use of that region.

C

Name: query string, name equals snippet, underscore blazer rocks and it's this dev lying here that is enabling syntax highlighting for that razor file type so that when you look at the code snippet on the rendered web page, the syntax, highlighting that you that you see should be very similar to what you would get in Visual Studio.

C

There's all kinds of those out here.

A

Let me see a question on and now's a good time if you're watching live now is a good time to get any questions into the team. So there's a question Camacho asking how to combine relevant relevant Docs that cross different platforms, for instance office, dachshund, asp, net box. Is it just kind of? Is there a standard for like? Do you put references, you know at the bottom, or do you just link what they enter and I'm, not sure? If that you know I, don't know if offices and I'm guessing something like a sure.

A

Something like a sure ad, and you know an asp net is something I've run into more yeah.

C

We see this a lot with visual studio, for example, the docker tools for visual studio is a great example, so we've got docker container is asian docks in the asp net cord dock set, but we also want the user to find the visual studio tooling, docks that relate to Azure. So we might link to that typically down at the bottom of the dock and an additional resources section.

A

C

Yeah one other approach we've taken is in our table of contents. We will sometimes link out to other dock sets for other products like Visual, Studio or John's example, azure ad ad b2c, anything that we think is super relevant to the customer. Reading the doc set. We want to make sure they can easily find that.

A

A

So one other thing is, you know: we've been focusing a lot on the mechanics and the workflow. Are there any so I've kind of stumbled across some some areas on the docks that I think are really great like, for instance, the guidance that you have on security and performance are really solid.

A

So is there anything you want to show off, like top docks that you that you would like developers to know more about and and if men come to mind, those are two that I love.

C

I would struggle to to pinpoint just one or two because I think they're all pretty awesome.

B

Yeah great answer: okay, you.

C

Guys anything that comes to mind.

D

C

D

Of them I'm pretty proud of the learn, work that we showed off earlier.

B

Yeah I've been olu to give you an environment, that's already set up and ready to go and just start learning right away. That's that's it's nice to finally have that so to be able to give that to people, so they can just get on their browser and go and.

C

So that's I, guess that's another example kind of going back to the previous question. We do actually learn link to the learn docs from the table of contents. We were looking at so I'll share my screen again here. It's sort of point out so looking at the table of contents, you're gonna notice, two categories of tutorials, just the plain old tutorials- is our classic non interactive tutorial, Tom Wade! You know all of us have invested a significant amount of time here.

C

Those have been around much longer they're sort of our tried-and-true go-to places to learn that the tech that you're interested in and then the Microsoft learned stuff- and these are obviously the more interactive form of our tutorials one.

B

Of my favorite is, is Tom's EF series and there's been a lot of people that have been involved in and helping to improve those over time, but I in particular, I like like that one is the top one that I like folks to go. Take a peek at Luke.

D

And the chat is calling out the Blazer preview Docs, oh yeah. Yes,.

B

C

This is a great opportunity to show off the version selector, because right now, if you were to go digging around for the Blazer Doc's, you would not find them, and the reason is too too is the default version that is selected when you land on this page, so again, pay close attention to that version. Select three Oh preview and there's a filter up here.

C

If I search, blazer chances are I would find whatever I'm looking for by going that route, and you can see sure enough, there is actually a blazer tutorial out there that you could take a look at.

A

So well, a few people have said that the Doc's are amazing, so I need to make sure you're, seeing all that people are loving it. A few people have said that they wish that it ranked higher in Google results or that they just go in search directly in the docs. Is there stuff that you do to try and show up hiring in Google results, or is that just kind of you write good content and I hope that floats that off yeah.

B

We do a so we'll do a sweep for SEO on occasion. Search engine optimization probably should be doing it more often we do, but some of the problems will have long-standing. Is we have some content out, throw this great, but it's been out there for so long building up search juice that will put out something new right, and then we got to deal with that. So our own stuff, there's also been some changes.

B

Lately, I noticed where things like Wikipedia, which is also great but we'll we'll take a front seat over the top of contents out there, because they have some specific questions that are answered in that format. That's being offered, for example, through Google. Now we really need to change things around to address that better.

B

So there's some work to be done. There.

A

So another question on the chat and you showed the learn stuff, which is, which is amazing and it's interactive, there's also questions about. Try, dotnet integration and I know that's in parts of the docs but I it's harder to do with ASP netbox right.

B

Yeah, it is so we have. We have a series- that's out there with c-sharp for learning, if you're getting going with c-sharp that are awesome by Bill, Wagner and also lots of other folks were involved, helping to get that going, but it's a great way to go and that you can immediately just start typing in code right there as you're, going through the tutorial and it'll compile and run, and so that's a pretty awesome way to go. But we do we have anything for us beyond that.

B

Yeah I know, Rick was working on some I, don't think we have any published. Yet we do want to do that though, so we don't I was.

C

Just actually talking to Maria about this earlier today, so I can take this one, so we don't currently have support in our asp net core docs for TriNet. The reason is so try. Dotnet is currently based on client-side execution, using blazer and web assembly model.

C

For that reason, I guess that's that's one of the biggest limitations right now why we can't use asp net core with try dotnet it used to be that tried at net used a server-side execution model with Azure container instances and in that world we could have used it with asp net core for various reasons. They they shifted away from that model. I think cost-reduction might have been. One of those lack of interest was probably another well.

C

What we have now is we're sort of in this place where, if you had a need to use, try dotnet with anything asp net core, you could do that. However, it would require using a dotnet core global tool for tried net, and that would be a local Doc's experience that you would have at that point. It wouldn't be running up in the browser mm-hmm.

B

Okay, if you do a search for dotnet, do tea any tea and try you'll you'll find a blog up there by marina gaga, as it's provided in your an introduction to it, and she'll also link out to some docs that are using it.

B

But it's pretty cool I love using it that there's the there's an introduction to c-sharp series, it's up on Docs Microsoft comm, and if you check that out, you'll see tried out an ad in action and definitely a really nice way to start picking up a new language where you're you're coding- and you can see right there in the tutorial self. You can start fooling with the code and get results and see what's happening with it. We also have some examples of it up in the API reference.

B

There's some there's something like string, for example, where people just want to see what the output it's gonna look like. You know, I want to fool with what you got for an example. A little bit I want to see what's happening with it, and that was a great place to use it. There was a some up there for that. For that API I guess so.

C

Sweet you mentioned API reference and I just remembered. We haven't shown that. Let me share my screen. So folks know what we're referring to here. Yeah.

B

For the other, twenty thousand topics right.

C

So again, you know looking at the asp net core doc set down at the bottom of the TOC you're gonna see this API ref link if you click there now. This is against an alternative way of sort of looking at the internals of the api's within asp net core. If you so you're, not inside a visual studio, choosing go to definition. You want to view that information from the web page. Well, here's how you would do it asp net core is where we are now, but you'll notice.

C

We've got API rough pages for really all of our developer products out there, so dotnet core. A lot of the people on the call right now might be interested in that. Well, you can look at that information as well, and you can see that you know we currently have available the latest preview. Six AP is in the three old release. We really like to keep this updated as much as possible, but you can dive into say the asp net core HTTP namespace and just get a sense of well.

C

What's in that namespace looks like we've got. You know some interfaces out here. I form collection, we can look at the properties and methods within in a lot of this I believe is generated by the code comments within asp net core correct me. If I'm wrong, Wade yeah.

B

No, they are so if, if the developer, rod provides triple slash comments, those are brought in here initially depends on the API being generated at Microsoft, but it's just essentially how it works. Yeah.

A

Very cool well we're right at about an hour, so I think we've, we've shown quite a bit of stuff and I think this has been great I. Think really. This is long overdue and we should have had you on before and and I'd like to.

A

You know make this more of a regular thing where you know if there are big updates from the team or big new features, love for the community to be more aware of them, so you showed at the beginning how people can get involved and can communicate with you where's-where's kind of you know the top thing: should people just go out to the docs repo or go go and edit people have questions? How do they reach you? I.

C

Think the the best place to start is go to our github repository. So again, that's github.com, slash asp net to slash asp, net core dot, docs go out there and you know open an issue if you want to start a conversation with the team about something. If it's not a Doc's issue, maybe it's a product issue. Another good github repo is asp net, slash asp, net core, you go out there and you get the product team instead of the docs team. Mm-Hmm.

A

My understanding to like I'll talk to people and they say well, I'm I'm worried about putting an issue in the wrong repo and from talking to most of the teams, they'll say just file the issue and we'll move it to the right repo. If we need to yeah.

B

We just I hear you, so don't don't worry about that we'll take care of if.

E

It's a question on a specific article: there's a blame if the bottom of the article that creates a issue it's connected to, that article, cool.

A

So right within the article you click on the bottom.

E

There's feedback for product or page, if you click on the page button, it'll create a github issue connected to that is treated a bit that particular article right.

A

Okay, well, I think we're we're set to wrap up there. Unless you have anything else, you'd like to add I will.

B

Have to follow up on the localization question, that's one! We didn't answer so I'll make sure we're prepared with that one. Next time. Sorry, we don't. We don't have that that one sure.

C

I guess the one last thing I would have is I wanted to show off what Tom was just describing, not sure how I forgot to show that. So, thank you, Tom.

C

Let me just go back to our Doc's asp net core and if we scroll down to the bottom of one of our docs, say about asp net core you'll notice, this feedback link at the top. What tom was describing was this github integration. So in this send feedback about box here you can click this this page button and that will actually allow you to open a github issue specifically for this doc and so you'll see below this submit feedback box. There are currently three other open issues for this doc.

C

So this is a really great way to come out here and see if you know maybe you've you're struggling to figure something out well chances are. Somebody is already file the github issue for the same problem, maybe they're struggling with that same issue. This is a really great place to look.

B

Right because you can see there where there's a discussion going on for those items and lots of folks can jump in.

A

Alright, well so we'll we'll post the the links in the show notes anything that you'd like to you know you can you can also watch the comments or the so if you'd like to and otherwise so you know, join us every Tuesday for the asp net community stand-up and on Thursdays we have the additional dotnet community stand-ups on the other platforms as well. So you know everything from mobile and cloud language tools, etc. So, thanks a lot, I think I think we're set to wrap up there.

A

So Tom you as the one person in Channel, 9 studios, you're the person that needs to end the broadcast and we'll do something right now: okay,.

B

All right thanks.