| Topic | Presenter(s) | Summary | Duration | Tags | Certification Quiz | Captions |
| ------------------------------ | ------------- | ----------------------------------------------------------------------------------- | -------- | ------------------------------------------------------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| ASP.Net Core 3 & Angular 9 | Chris Reddick | Chapter 1 of the book (link below) which will be discussed during Friday Trainings. | 23:12 | #ASP.Net, #ClarityTrainings, #DevTrainings, #FridayTrainings #Core3, #Angular9 | N/A | ASP.Net_Core_Angular_9_Chapter 1_AutoGeneratedCaption.txt |https://www.amazon.com/ASP-NET-Core-Angular-stack-development-ebook/dp/B083TTLXCB00:00:02.070 --> 00:00:06.928 - Alright, so let's see here, um, so this is the book, uh, that we 00:00:06.928 --> 00:00:11.439 - were talking about. You can see this is a pretty new book, and 00:00:11.439 --> 00:00:13.174 - it's got some really good 00:00:13.174 --> 00:00:17.312 - content. It's very hands-on and, uh, just really kind of 00:00:17.312 --> 00:00:21.250 - compelling. Uhm, the Kindle book doesn't cost very much and we're 00:00:21.250 --> 00:00:25.188 - happy to get the Kindle Book for anyone who's interested in 00:00:25.188 --> 00:00:28.768 - engaging on it and reading it. It's really, really interesting. 00:00:28.768 --> 00:00:33.422 - You can, for those of you that are unaware, you can use the 00:00:33.422 --> 00:00:38.076 - Kindle Cloud Reader so you can read. You don't have to have a 00:00:38.076 --> 00:00:42.014 - physical Kindle device if you use Kindle, you can use a 00:00:42.014 --> 00:00:44.162 - browser or they have mobile apps 00:00:44.162 --> 00:00:49.618 - for. Android and iOS as well. So anyway, uh, the the book itself 00:00:49.618 --> 00:00:55.065 - is pretty. It's pretty short. Uhm, I want to say it's like 500 00:00:55.065 --> 00:00:59.674 - pages. And as you guys know for a development book, that's 00:00:59.674 --> 00:01:04.702 - relatively short. I know the C book we were working on last 00:01:04.702 --> 00:01:09.730 - year was like OK, so it's 732 pages, but it's still pretty 00:01:09.730 --> 00:01:14.318 - short. When we were doing last year was like 2000 pages. I want 00:01:14.318 --> 00:01:18.790 - to say um, so this book. I'll just kind of quickly go over 00:01:18.790 --> 00:01:20.854 - what I mean. It covered today. 00:01:21.630 --> 00:01:26.713 - Um, this book has a lot of content. I'm I'm just going to 00:01:26.713 --> 00:01:31.405 - briefly skim over this chapter one, and then I'm gonna go over 00:01:31.405 --> 00:01:35.706 - just kind of an outline of this little application that they 00:01:35.706 --> 00:01:40.789 - build and that you work on in these first few chapters. And so 00:01:40.789 --> 00:01:44.699 - just from a general perspective, what they're covering in the 00:01:44.699 --> 00:01:48.609 - first chapter is pretty interesting, so this book in the 00:01:48.609 --> 00:01:52.519 - first chapter is actually pretty interesting. It talks about the 00:01:52.519 --> 00:01:56.103 - history. Of net core and angular, and specifically 00:01:56.103 --> 00:02:00.144 - the latest versions of angular. It kind of gives 00:02:00.144 --> 00:02:03.736 - you some background information so you can go 00:02:03.736 --> 00:02:09.573 - and dig in and kind of get all of the right the right 00:02:09.573 --> 00:02:13.614 - sides and other supporting software. They also have a 00:02:13.614 --> 00:02:18.553 - really nice GitHub, so if you want I can share this 00:02:18.553 --> 00:02:22.594 - to the channel so that you guys have it. 00:02:23.730 --> 00:02:28.280 - But basically in fact, let me just go ahead and do that right 00:02:28.280 --> 00:02:32.300 - now. And you may have already typed it in. If you're 00:02:32.300 --> 00:02:35.953 - watching that, uhm, but let me see if I can post this to 00:02:35.953 --> 00:02:37.077 - the channel really fast. 00:02:38.340 --> 00:02:42.848 - And I would encourage you to go take a look at. This is pretty 00:02:42.848 --> 00:02:45.424 - interesting. So basically they're just. They're just kind 00:02:45.424 --> 00:02:49.288 - of enhancing a kind of off the shelf.net core and angular app, 00:02:49.288 --> 00:02:52.830 - and one of the things that I thought was pretty interesting. 00:02:53.590 --> 00:02:57.500 - This particular book kind of outlines all the background of 00:02:57.500 --> 00:03:02.583 - net core and angular, but one of the things that I found really 00:03:02.583 --> 00:03:04.538 - compelling was the fact that. 00:03:05.070 --> 00:03:10.757 - With.net core, one of the things that they heavily integrated was 00:03:10.757 --> 00:03:12.308 - angular and react. 00:03:12.810 --> 00:03:18.592 - And Uhm, I'm sure for those of you that are pretty savvy on the 00:03:18.592 --> 00:03:23.548 - front end and just in general, most people have heard of react, 00:03:23.548 --> 00:03:27.678 - react and angular. Kind of the two big frameworks that 00:03:27.678 --> 00:03:32.634 - Microsoft kind of built a lot of. And just in general they 00:03:32.634 --> 00:03:37.590 - made the platform really kind of receptive to be able to create 00:03:37.590 --> 00:03:40.894 - different applications that are, you know, JavaScript frameworks. 00:03:40.894 --> 00:03:42.546 - They can integrate with 00:03:42.546 --> 00:03:43.930 - asp.netor.net core. General. 00:03:44.670 --> 00:03:49.506 - And so Long story short, uhm, angular is really kind of a 00:03:49.506 --> 00:03:53.536 - first class citizen in many regards. Within this kind of 00:03:53.536 --> 00:03:57.566 - Microsoft ecosystem, if you will, there's a lot of tight 00:03:57.566 --> 00:04:01.193 - integration between Microsoft and Google. Believe it or not, 00:04:01.193 --> 00:04:04.820 - because they're Microsoft made typescript and Google is heavily 00:04:04.820 --> 00:04:09.253 - leveraged typescript. Really, since as kind of a a part of 00:04:09.253 --> 00:04:12.477 - their core development process as of angular 2. 00:04:13.090 --> 00:04:17.170 - And so, anyway, um, just kind of from a really, really high 00:04:17.170 --> 00:04:21.590 - level. Uhm, if you kind of dive into the angular side of this. 00:04:21.590 --> 00:04:24.990 - So this is kind of outlines thehistoryof.net core and then 00:04:24.990 --> 00:04:29.410 - angular, and I found it to be quite helpful. So this is going 00:04:29.410 --> 00:04:33.150 - over dot net core and some of the changes and differences 00:04:33.150 --> 00:04:36.890 - between the different versions. And then it does the same for 00:04:36.890 --> 00:04:42.308 - angular. And it just kind of goes over some of the basics of 00:04:42.308 --> 00:04:47.170 - angular JS. So for a lot of the team you know we're using 00:04:47.170 --> 00:04:51.658 - angular JS on the Seth platform currently and this kind of gives 00:04:51.658 --> 00:04:56.894 - a very high level of some of the key tenants. One of the primary 00:04:56.894 --> 00:05:00.634 - of which was the dependency injection, which angular it says 00:05:00.634 --> 00:05:04.748 - it's saying is it was the first client side framework to 00:05:04.748 --> 00:05:08.488 - implement that, which is a huge advantage overall and just 00:05:08.488 --> 00:05:09.610 - overall in general. 00:05:09.670 --> 00:05:14.866 - With typescript added to it, it was really attractive to a lot 00:05:14.866 --> 00:05:19.196 - of C sharp developers because having that kind of capability 00:05:19.196 --> 00:05:23.526 - to have the strongly typed and Intellisense type of interaction 00:05:23.526 --> 00:05:27.856 - is really what C sharp developers are used to an. 00:05:28.750 --> 00:05:30.725 - That was something that was 00:05:30.725 --> 00:05:37.130 - easily adopted. And then just in general, um is, as most everyone 00:05:37.130 --> 00:05:41.495 - knows, angular two was essentially a rewrite of angular 00:05:41.495 --> 00:05:46.830 - JS, and so you can see it's literally saying a complete 00:05:46.830 --> 00:05:52.650 - rewrite and it was based on ecmascript 6, and if you're not 00:05:52.650 --> 00:05:57.500 - familiar with Ecma script, I think it stands for European 00:05:57.500 --> 00:05:59.925 - Computer Manufacturers Association, and they 00:05:59.925 --> 00:06:02.350 - essentially have kind of the 00:06:02.350 --> 00:06:09.014 - floor. And are the kind of the Premier group that defines a lot 00:06:09.014 --> 00:06:14.134 - of just kind of the protocols and specifications for, among 00:06:14.134 --> 00:06:19.254 - other things, JavaScript and so that Ecma script is essentially 00:06:19.254 --> 00:06:24.374 - become heavily adopted in a standard in general. And so 00:06:24.374 --> 00:06:30.518 - anyway with angular to some big big pieces In addition to the 00:06:30.518 --> 00:06:32.566 - complete rewrite the general 00:06:32.566 --> 00:06:36.675 - concept. Here you can see. Again typescript was really heavily 00:06:36.675 --> 00:06:40.230 - adopted, uman, informally adopted. I should say uhm. And 00:06:40.230 --> 00:06:45.365 - then there were some other key components as we go to work on 00:06:45.365 --> 00:06:49.710 - angular 9, you'll see that the server side rendering is pretty 00:06:49.710 --> 00:06:53.265 - interesting, so you actually have the ability with this 00:06:53.265 --> 00:06:58.005 - server side rendering as of angular two and beyond to set up 00:06:58.005 --> 00:07:02.745 - a node server that sits in the background and it's going to 00:07:02.745 --> 00:07:04.720 - serve up from the server. 00:07:04.750 --> 00:07:10.080 - Uh, in in a sensually interpret that angular code a min pump it 00:07:10.080 --> 00:07:15.820 - into the HTML as a server side load and then as the actual page 00:07:15.820 --> 00:07:19.510 - loads, then with the angular actually executing that server 00:07:19.510 --> 00:07:24.020 - side generated code gets replaced and so it's kind of an 00:07:24.020 --> 00:07:28.530 - interesting approach if you want to read about. It's definitely a 00:07:28.530 --> 00:07:33.450 - unique way to handle it, but that really helps with kind of 00:07:33.450 --> 00:07:35.090 - performance and page rendering. 00:07:35.150 --> 00:07:40.454 - And organic SCO and things like that which angular has has had a 00:07:40.454 --> 00:07:45.350 - lot of challenges with. Believe it or not I was found it 00:07:45.350 --> 00:07:49.430 - interesting that angular was written by Google. I mean, it 00:07:49.430 --> 00:07:53.102 - was essentially written by Google Engineers, but it wasn't 00:07:53.102 --> 00:07:57.182 - and still largely without. This is not very organic SEO 00:07:57.182 --> 00:08:02.078 - friendly, so you have to do things like setting up a caching 00:08:02.078 --> 00:08:06.974 - model for angular JS. And so if you're not familiar with this, 00:08:06.974 --> 00:08:09.014 - we use a caching system. 00:08:09.040 --> 00:08:12.811 - That let's us essentially represent all of the angular 00:08:12.811 --> 00:08:17.839 - content into cache files and the tool that we use typically is 00:08:17.839 --> 00:08:22.867 - called pre render dot IO. But going forward we won't need to 00:08:22.867 --> 00:08:27.895 - do that with the newer version of angular. We can use the 00:08:27.895 --> 00:08:32.504 - server side rendering and then the CLI is another really big 00:08:32.504 --> 00:08:38.970 - deal. Uhm, this is a really nice tool set and it's just continue 00:08:38.970 --> 00:08:43.920 - to get better with the newer versions of angular and then 00:08:43.920 --> 00:08:47.970 - generally components. This concept in general is kind of 00:08:47.970 --> 00:08:50.670 - the core of angular two and 00:08:50.670 --> 00:08:56.132 - beyond. And then, um, just kind of more as a trivia thing than 00:08:56.132 --> 00:08:59.842 - anything. But you can actually see that they skipped angular 00:08:59.842 --> 00:09:03.552 - three, and this was because they are using this semantic 00:09:03.552 --> 00:09:07.633 - versioning and they wanted to kind of line all the versions 00:09:07.633 --> 00:09:09.859 - up, and they already had a. 00:09:09.870 --> 00:09:14.083 - Basically a version 3 for the router, so they just started 00:09:14.083 --> 00:09:18.296 - everything at version four. When they started doing this kind of 00:09:18.296 --> 00:09:23.275 - versioning and updates so that they are all in the same kind of 00:09:23.275 --> 00:09:28.637 - version. If you will and I won't go into too much detail on these 00:09:28.637 --> 00:09:32.084 - specific versions, but there were there were some pretty 00:09:32.084 --> 00:09:36.297 - major updates that came out and basically angular 7 and then 00:09:36.297 --> 00:09:40.510 - some pretty major updates that came out with some of the 00:09:40.510 --> 00:09:44.830 - concepts here. An angular 9 as well that are really really 00:09:44.830 --> 00:09:49.120 - helpful for us an and so ultimately the bottom line is 00:09:49.120 --> 00:09:53.410 - net. Core and angular are very well supported in the Microsoft 00:09:53.410 --> 00:09:57.700 - ecosystem and then just in general in the in the JavaScript 00:09:57.700 --> 00:10:01.990 - framework ecosystem and this book is kind of giving you some 00:10:01.990 --> 00:10:06.280 - history on that and some granular detail and then it just 00:10:06.280 --> 00:10:10.960 - kind of talks in general about things that are helpful for us 00:10:10.960 --> 00:10:15.490 - to know. Um, and I'm not sure if everyone's familiar with the 00:10:15.490 --> 00:10:18.450 - term spa or single page application, but that's 00:10:18.450 --> 00:10:22.150 - basically the core of what angular was kind of designed 00:10:22.150 --> 00:10:26.220 - for, and the concept is that there are really as you're 00:10:26.220 --> 00:10:29.180 - interacting with the application, you don't have to 00:10:29.180 --> 00:10:33.990 - do any post backs to the server during the course of the entire 00:10:33.990 --> 00:10:37.690 - interaction with the application is everyone knows with our E 00:10:37.690 --> 00:10:41.760 - Commerce platform we do still do postbacks even though we have 00:10:41.760 --> 00:10:46.030 - angular. Uhm, you know it within our entire application, but we 00:10:46.030 --> 00:10:49.477 - do have sections of our application like the dashboard 00:10:49.477 --> 00:10:54.073 - page that leverage this kind of spa capability, and so that was 00:10:54.073 --> 00:10:58.669 - kind of a key concept with angular in general. But you also 00:10:58.669 --> 00:11:03.265 - have some new terms that I'm not sure if everyone is familiar 00:11:03.265 --> 00:11:04.414 - with. Progressive web 00:11:04.414 --> 00:11:09.794 - application TWA. It essentially allows you to from an 00:11:09.794 --> 00:11:13.658 - application development perspective, adopt kind of core 00:11:13.658 --> 00:11:19.730 - pieces that allow a application to do things that typically a 00:11:19.730 --> 00:11:25.250 - mobile application would do, so you can essentially see from 00:11:25.250 --> 00:11:26.906 - this highlighted section. 00:11:28.100 --> 00:11:33.677 - This is kind of a summary. Uhm, so it basically allows. 00:11:35.310 --> 00:11:40.051 - Using kind of typical web based development tools, HTML, CSS and 00:11:40.051 --> 00:11:43.930 - JavaScript allows us to do things like push notifications, 00:11:43.930 --> 00:11:47.809 - offline mode, permission based hardware access, etc. And soapy 00:11:47.809 --> 00:11:51.688 - WA. Whenever you see progressive web application, it's definitely 00:11:51.688 --> 00:11:56.429 - something that we can kind of turn on if you will. 00:11:56.450 --> 00:11:59.810 - Interacting with angular and it can do some really powerful 00:11:59.810 --> 00:12:03.842 - things with regards to, you know with regards to a mobile device 00:12:03.842 --> 00:12:05.186 - which is really nice. 00:12:05.720 --> 00:12:09.245 - Uhm, and then just overall, 00:12:09.245 --> 00:12:14.884 - uhm? The kind of the next piece is just kind of talking about 00:12:14.884 --> 00:12:19.460 - this project, which I will show next, so let me kind of show. 00:12:20.260 --> 00:12:23.764 - I'm gonna show my PowerShell. I'm going to kind of jump around 00:12:23.764 --> 00:12:27.852 - the screens 'cause I'm on a 4K monitor and it's kind of hard to 00:12:27.852 --> 00:12:32.524 - see I think. So let me just jump to this one so one of the things 00:12:32.524 --> 00:12:36.028 - that I found really compelling and this is true of the angular 00:12:36.028 --> 00:12:38.072 - CLI. This is the dot net core. 00:12:38.880 --> 00:12:44.119 - A side of that, but basically you can just go into a folder 00:12:44.119 --> 00:12:49.761 - and you can a sensually make a new project and this one is the 00:12:49.761 --> 00:12:53.026 - angular template. Uhmbutyoucansay.net new and then 00:12:53.026 --> 00:12:58.295 - there are several different kind of off the shelf templates uhm? 00:12:58.840 --> 00:13:02.980 - And then essentially give it a name, give the the project name 00:13:02.980 --> 00:13:07.465 - and it'll generate this project for you. And so I just want to 00:13:07.465 --> 00:13:11.260 - kind of briefly go over that just because I think it's 00:13:11.260 --> 00:13:15.479 - helpful. One of the things that I found myself kind of dealing 00:13:15.479 --> 00:13:19.366 - whenever I'm looking at any new technology as I kind of at first 00:13:19.366 --> 00:13:21.459 - can tend to feel a little bit 00:13:21.459 --> 00:13:27.031 - overwhelmed. And I just want you to know literally. I went and 00:13:27.031 --> 00:13:29.186 - typed the.net new angular health 00:13:29.186 --> 00:13:32.890 - check. And then it generated these files for me. 00:13:33.850 --> 00:13:37.470 - An eye opened this CSS praj Anne now will go 00:13:37.470 --> 00:13:39.280 - look at the CSS praj. 00:13:40.540 --> 00:13:47.065 - So let me do that and I should be able to stay on this Visual 00:13:47.065 --> 00:13:50.980 - Studio for awhile. So it basically generated this, this 00:13:50.980 --> 00:13:56.200 - solution and the project within and it's got both my web APIs 00:13:56.200 --> 00:14:02.725 - and then it also has my angular app so you can see my my web 00:14:02.725 --> 00:14:09.685 - APIs and then it has a few pages here and then. It also has my my 00:14:09.685 --> 00:14:10.990 - angular app within. 00:14:11.580 --> 00:14:16.875 - And so this is a really nice way to just kind of play around, and 00:14:16.875 --> 00:14:20.405 - there's nothing like playing around as a software engineer to 00:14:20.405 --> 00:14:23.935 - just kind of get yourself comfortable. One of the things 00:14:23.935 --> 00:14:28.524 - that the book does in the first, the first parts of the second 00:14:28.524 --> 00:14:33.113 - chapter, is it just kind of goes through all the files and says 00:14:33.113 --> 00:14:38.055 - what they do. One of the things for those of you who are pretty 00:14:38.055 --> 00:14:42.291 - new to net core is this concept of bootstrapping is kind of. 00:14:42.300 --> 00:14:46.308 - Different uhm, and I think most of the team is pretty familiar 00:14:46.308 --> 00:14:50.316 - with this, but in general the idea of bootstrapping and how it 00:14:50.316 --> 00:14:53.990 - works and just you know the concept in general, it's really 00:14:53.990 --> 00:14:59.000 - helpful to kind of go look at it in the flesh if you will and 00:14:59.000 --> 00:15:02.340 - just kind of see how it's physically operating and then 00:15:02.340 --> 00:15:06.348 - the changes to the config files. It's also really helpful to be 00:15:06.348 --> 00:15:11.024 - able to just kind of physically see that and so this is a great 00:15:11.024 --> 00:15:13.028 - example. For those of you who 00:15:13.028 --> 00:15:17.141 - subconsciously. Might be like me and it might be just a little 00:15:17.141 --> 00:15:21.233 - bit intimidating to think about. Oh, it's dot net core, it's, you 00:15:21.233 --> 00:15:25.325 - know, angular 9 wood that's scary. Just go play with it. Um, 00:15:25.325 --> 00:15:29.417 - you can literally make this in about 5 minutes, maybe even two 00:15:29.417 --> 00:15:33.850 - minutes, and I will tell you the first time you build it, it's 00:15:33.850 --> 00:15:38.283 - gonna go restore the. It's going to do the MPM restore of those 00:15:38.283 --> 00:15:42.375 - packages and that does take. I think it took about 15 minutes 00:15:42.375 --> 00:15:43.398 - on my machine. 00:15:43.400 --> 00:15:49.186 - It's just downloading like 400 Megs of node module files. Uhm, 00:15:49.186 --> 00:15:55.498 - but then after that I got my little health check app. Hey. 00:15:55.510 --> 00:15:59.735 - Yeah it is it. Oh well, you turned off the screen, but was 00:15:59.735 --> 00:16:04.285 - it just me or did a Gray box appear over most of that for 00:16:04.285 --> 00:16:07.860 - everyone else too? Yeah, I totally agree. Box as well. I 00:16:07.860 --> 00:16:11.435 - was trying to say earlier. Oh, I'm sorry I was afraid. 00:16:11.480 --> 00:16:15.180 - Yeah, that's a lot better. Relax, OK, cool, thanks for 00:16:15.180 --> 00:16:19.620 - saying something. Yeah, so this is the little app that it builds 00:16:19.620 --> 00:16:23.320 - and this is literally just straight out of this template, 00:16:23.320 --> 00:16:28.130 - but I. I thought there was some helpful thing. So um, for front 00:16:28.130 --> 00:16:31.830 - end development team members, this was kind of cool because 00:16:31.830 --> 00:16:35.160 - this is essentially an angular component and it's interacting 00:16:35.160 --> 00:16:39.970 - with the Web API. So you can kind of see physically how to 00:16:39.970 --> 00:16:41.820 - set all of that up. 00:16:41.840 --> 00:16:46.232 - An it's really simple, of course, so it's not going to be 00:16:46.232 --> 00:16:50.624 - an architectural guide, but it will give you kind of a best 00:16:50.624 --> 00:16:54.284 - practice on just like basic setup and kind of confidence 00:16:54.284 --> 00:16:58.310 - level so you can understand the underpinning pieces and how they 00:16:58.310 --> 00:17:03.358 - work. So and then the fetch data. This is just kind of a 00:17:03.358 --> 00:17:07.472 - pure uhm. You know, pure API call that's going out and 00:17:07.472 --> 00:17:11.960 - getting this kind of random set of data. And then again it's 00:17:11.960 --> 00:17:17.196 - pulling it into a component so it can show it in the page. And 00:17:17.196 --> 00:17:21.684 - so these are some really simple things. But the point is that 00:17:21.684 --> 00:17:26.172 - from a technical perspective I'm sure we all know like the first 00:17:26.172 --> 00:17:29.538 - thing about any any technology stack or something that. 00:17:29.580 --> 00:17:33.023 - You know that we're trying to build is kind of understanding 00:17:33.023 --> 00:17:36.153 - how everything fits together, and so this this book, basically 00:17:36.153 --> 00:17:39.909 - in Chapter 2, which I'll be going into in detail next week. 00:17:39.909 --> 00:17:44.291 - It really starts to get into the weeds on that, and the plan is 00:17:44.291 --> 00:17:48.360 - not to spend a huge huge amount of time going over this each 00:17:48.360 --> 00:17:52.429 - week, just kind of a summary so that you can catch some things, 00:17:52.429 --> 00:17:56.185 - and then if you want, you can certainly engage in reading on 00:17:56.185 --> 00:17:59.941 - the book directly, and you can also participate in this kind of 00:17:59.941 --> 00:18:04.866 - schedule. So the plan is to go through one chapter a week, and, 00:18:04.866 --> 00:18:09.780 - um, I think this first chapter takes like maybe 15 to 20. I 00:18:09.780 --> 00:18:12.048 - would say like 45 minutes to 00:18:12.048 --> 00:18:16.366 - read. And so if you did want to go ahead and join the bandwagon 00:18:16.366 --> 00:18:19.688 - and keep moving with me each week, uhm, you're welcome to 00:18:19.688 --> 00:18:23.312 - request that Kindle Book you would just need to reach out to 00:18:23.312 --> 00:18:26.936 - either, you know your manager or you can directly ping me and 00:18:26.936 --> 00:18:28.748 - I'll send you that the Kindle 00:18:28.748 --> 00:18:33.560 - Book as well. So let me see if you guys have any questions 00:18:33.560 --> 00:18:37.655 - before I kind of see the floor here. Pretty basic stuff I think 00:18:37.655 --> 00:18:41.435 - so, but I'll kind of go into some of these detailed examples 00:18:41.435 --> 00:18:45.845 - next. We can kind of talk about some of them that I think will 00:18:45.845 --> 00:18:49.940 - be interesting to the group. I'm happy to send out a hard copy, 00:18:49.940 --> 00:18:53.090 - please. Yeah, whatever format you guys prefer, very happy too. 00:18:53.090 --> 00:18:56.555 - So if you guys don't mind just because I struggle with 00:18:56.555 --> 00:19:00.020 - remembering on the phone, if you'll just send me a direct 00:19:00.020 --> 00:19:04.400 - message on teams. If you want a paperback or Kindle, Um Ann, and 00:19:04.400 --> 00:19:08.781 - you can just teams me and I'll set that up probably today. And 00:19:08.781 --> 00:19:12.488 - if you are doing a paperback, I just appreciate you confirming 00:19:12.488 --> 00:19:16.195 - your mailing address too. So there you go. So that's chapter 00:19:16.195 --> 00:19:20.576 - one and I'll be covering chapter 2 next week. An again. Feel free 00:19:20.576 --> 00:19:22.598 - if you guys have any questions, 00:19:22.598 --> 00:19:25.410 - otherwise will. Switch to the next topic.