| Topic | Presenter | Summary | Duration | Tags | Quiz | Captions |
| ----------------------------------------------- | ------------------------ | --------------------------------------------------------------------------------------------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------- | -------- |
| Exploring the Application from the ASP.Net Book | Chris Black/Igor Ivancic | In this portion of the dev training, the group tested the application from Chapter 7 of the ASP.Net Core 3 & Angular 9 Book | 1:00:12 | #DevTraining, #fridayTraining, #ASP.Net, #Core3, #Angular9 | Dev Training - 09/04/2020 | |00:00:02.350 --> 00:00:06.432 - OK, Alright cool, so I'm going to make a new pull request and 00:00:06.432 --> 00:00:10.828 - basically what this is going to do is like if you make a change 00:00:10.828 --> 00:00:14.910 - like on a client site and just inadvertently like fix a bug in 00:00:14.910 --> 00:00:18.992 - core or you come up with like a cool feature or something like 00:00:18.992 --> 00:00:22.446 - that that you think should be brought into core. That's all 00:00:22.446 --> 00:00:26.214 - this is going to be so you can say whatever your branches 00:00:26.214 --> 00:00:29.040 - obviously into your other branch. Pretty standard here and 00:00:29.040 --> 00:00:31.238 - then you just go ahead and put 00:00:31.238 --> 00:00:34.340 - in your title. Typical description you know what you're 00:00:34.340 --> 00:00:37.530 - fixing, what you're doing there, and then link your work items 00:00:37.530 --> 00:00:38.980 - and all that good stuff. 00:00:40.370 --> 00:00:43.862 - Some Scroll down to the end and then you'll have this tags 00:00:43.862 --> 00:00:47.063 - section and this is the section that I'm talking about. So 00:00:47.063 --> 00:00:50.264 - basically you can flag a pull request with the changes that 00:00:50.264 --> 00:00:54.629 - you make and you can put like if you think it's going to be a 00:00:54.629 --> 00:00:57.830 - core candidate you can put in your description what should be 00:00:57.830 --> 00:01:01.322 - reviewed and kind of pulled in and kind of be pretty explicit 00:01:01.322 --> 00:01:04.814 - about what you're referring to as far as the code goes, and 00:01:04.814 --> 00:01:08.015 - then you could expect some follow up from somebody like on 00:01:08.015 --> 00:01:09.761 - the core team like James or 00:01:09.761 --> 00:01:12.965 - Patrick are. You know anybody like that? To kind of clarify 00:01:12.965 --> 00:01:16.410 - what you're what you're wanting to add in. If it's not just like 00:01:16.410 --> 00:01:19.060 - a couple files and you know something that immediately pops 00:01:19.060 --> 00:01:20.120 - out is making sense. 00:01:21.520 --> 00:01:24.347 - So just a heads up there. You might, you know, get 00:01:24.347 --> 00:01:27.174 - asked a few questions as to what exactly was going on. 00:01:28.770 --> 00:01:31.230 - Excuse me and then down here. 00:01:32.430 --> 00:01:35.260 - You can just select core candidate. I think we're going 00:01:35.260 --> 00:01:38.656 - to use this one this court in space candidate. There's a camel 00:01:38.656 --> 00:01:42.335 - case, one in here as well. I think this is the one we're 00:01:42.335 --> 00:01:45.448 - moving forward, but I know this is confusing, so we probably 00:01:45.448 --> 00:01:49.693 - just need to update this one to not be here. But for now it will 00:01:49.693 --> 00:01:52.806 - just be core candidate and it will have this nice little 00:01:52.806 --> 00:01:55.919 - pretty Azure tag. And then whenever I create the PR this 00:01:55.919 --> 00:01:59.598 - will. You know we can filter RP Rs. Your completed PR is based 00:01:59.598 --> 00:02:01.579 - off of this tag. So core team 00:02:01.579 --> 00:02:05.638 - members like James. Can you roll through him and bring some fixes 00:02:05.638 --> 00:02:10.768 - in so this is like like I said, just a way to like easilly bring 00:02:10.768 --> 00:02:14.872 - in bug fixes or features into core so you know there's doesn't 00:02:14.872 --> 00:02:18.976 - make sense to. Basically you know go back in like you know, 00:02:18.976 --> 00:02:22.738 - fix a bug if you've already fixed it per client because 00:02:22.738 --> 00:02:26.158 - essentially the clients paid for it because you were just 00:02:26.158 --> 00:02:30.262 - inadvertently doing it anyway and so we kind of get a freebie 00:02:30.262 --> 00:02:32.656 - on our side just from you fixing 00:02:32.656 --> 00:02:36.331 - that bug. Or you making that feature so if a client and I 00:02:36.331 --> 00:02:39.845 - mean that's a big part of our code base that I know some of 00:02:39.845 --> 00:02:42.857 - you were newer, but how we've kind of built our codebase over 00:02:42.857 --> 00:02:45.869 - the years is, and you may have already, you know, kind of 00:02:45.869 --> 00:02:49.132 - realized this on your own, but you know a client will kind of 00:02:49.132 --> 00:02:52.897 - come up with a cool feature like the you know. I think JT is kind 00:02:52.897 --> 00:02:55.658 - of re using a search feature that we built previously for 00:02:55.658 --> 00:02:58.921 - another client and will just kind of bake it into core and we 00:02:58.921 --> 00:03:02.435 - might have to update it if we don't use it in several years or 00:03:02.435 --> 00:03:05.196 - something like that, but at least will have like the core 00:03:05.196 --> 00:03:06.953 - concept in the core code to kind 00:03:06.953 --> 00:03:11.392 - of. Twist and tweak to make fit. You know our current product, 00:03:11.392 --> 00:03:15.112 - but that's essentially it. And does anybody have any questions 00:03:15.112 --> 00:03:19.948 - as to what's going on here? Any comments or anything or ideas? I 00:03:19.948 --> 00:03:24.412 - would just emphasize that a lot of times you might be surprised 00:03:24.412 --> 00:03:28.132 - even if there's like something that you just slightly modified 00:03:28.132 --> 00:03:32.968 - or it's very client specific. If you're able to tag it. An just 00:03:32.968 --> 00:03:35.944 - kind of be able to give us a 00:03:35.944 --> 00:03:40.676 - heads up. The the main thing that I would say is this is 00:03:40.676 --> 00:03:44.042 - meant as a communication method as opposed to like a tactical 00:03:44.042 --> 00:03:48.326 - thing where we can take code out and use it right away. It's more 00:03:48.326 --> 00:03:51.998 - meant to say hey, there's this thing that could be better on 00:03:51.998 --> 00:03:55.364 - the E Commerce platform and it also applies to other areas, 00:03:55.364 --> 00:03:58.424 - like if you if you're doing something with the deployment 00:03:58.424 --> 00:04:02.708 - tool in your like man, this has this bug and I really need to 00:04:02.708 --> 00:04:07.298 - fix it, so I'm just going to do it right now, but I think it 00:04:07.298 --> 00:04:08.828 - should be pulled back in. 00:04:09.760 --> 00:04:13.130 - That might be applicable I think. For connect the same 00:04:13.130 --> 00:04:16.837 - thing applies connect you guys are doing that are working on 00:04:16.837 --> 00:04:20.881 - the connector you guys are doing a lot of different types of 00:04:20.881 --> 00:04:24.251 - projects and you're going to run into different protocols that 00:04:24.251 --> 00:04:28.295 - were working with and you know specific issues with how we need 00:04:28.295 --> 00:04:29.980 - to construct and kind of. 00:04:30.830 --> 00:04:33.300 - Implement the connector to deal 00:04:33.300 --> 00:04:38.450 - with that. And so I would think that those would also be 00:04:38.450 --> 00:04:42.010 - really good areas when you're working on them on those 00:04:42.010 --> 00:04:45.570 - connector projects to mark them. So anyway, I just want 00:04:45.570 --> 00:04:48.774 - to encourage you to be relatively over communicate if 00:04:48.774 --> 00:04:52.690 - on this and overly tagging versus under we don't want to 00:04:52.690 --> 00:04:54.114 - tag literally every PR. 00:04:56.050 --> 00:04:58.965 - But if you feel like you can reasonably point out too. 00:05:00.000 --> 00:05:03.380 - Most likely Garrett to start with will be kind of 00:05:03.380 --> 00:05:07.098 - coordinating with you. It maybe one or two other people, but 00:05:07.098 --> 00:05:10.140 - he'll be going in and cataloguing all these core 00:05:10.140 --> 00:05:13.520 - candidates and then chatting with the team member or members 00:05:13.520 --> 00:05:17.914 - who worked on it and just asking them to kind of, you know, 00:05:17.914 --> 00:05:21.294 - provide some more detail on what it was about this. 00:05:22.640 --> 00:05:26.854 - So another thing you may want to do is just whenever you do, put 00:05:26.854 --> 00:05:30.466 - a core candidate tag in there, you may want to just drop 00:05:30.466 --> 00:05:33.476 - yourself some notes. You can certainly put more detail into 00:05:33.476 --> 00:05:37.389 - your commit notes if you want, and say you know in your commit 00:05:37.389 --> 00:05:40.700 - notes. Here's what I'm thinking for the core candidate part. So 00:05:40.700 --> 00:05:44.613 - as a standard, I don't think it would be a bad idea. CD. 00:05:45.580 --> 00:05:50.088 - So just if you are going to do a core candidate and you think 00:05:50.088 --> 00:05:54.155 - about it. Nothing in the world if you don't, but if 00:05:54.155 --> 00:05:57.620 - you think about it in your commit notes, you could just 00:05:57.620 --> 00:06:00.455 - say core candidate Colon and then give a little 00:06:00.455 --> 00:06:02.975 - description of what you're thinking could be included, 00:06:02.975 --> 00:06:05.810 - and we're not looking for perfection here. We're just 00:06:05.810 --> 00:06:08.960 - trying to get a little bit better organization an as 00:06:08.960 --> 00:06:12.110 - they say, you know, use the sawdust. Don't just leave 00:06:12.110 --> 00:06:15.575 - chunks of wood and saw this laying around. Let's use 'em 00:06:15.575 --> 00:06:19.040 - can turn into particle board and use that to build some 00:06:19.040 --> 00:06:20.300 - really nice IKEA furniture. 00:06:22.530 --> 00:06:26.050 - Comments, comments in the code right around where you think 00:06:26.050 --> 00:06:29.570 - your your your core candidate code was too. Maybe or 00:06:29.570 --> 00:06:32.738 - something? Yeah, that's true too. That's a great point. 00:06:34.090 --> 00:06:38.724 - So yeah, in and I think as we kind of go through this, you 00:06:38.724 --> 00:06:42.365 - know you've heard the saying Don't let perfect be the enemy 00:06:42.365 --> 00:06:46.999 - of good. And so let's let's get started on it and you should see 00:06:46.999 --> 00:06:50.309 - some more iteration on this over the next several months. 00:06:51.730 --> 00:06:55.030 - Anne Anne more formality around it, but the goal is to, 00:06:55.030 --> 00:06:58.630 - you know, kind of release the speed break and keep the speed 00:06:58.630 --> 00:07:02.530 - break off. 'cause I know that you guys are busy and you know 00:07:02.530 --> 00:07:05.830 - we don't want to encumber you with even more, but you're 00:07:05.830 --> 00:07:08.530 - sitting there thinking alot of times like this sucks. 00:07:10.150 --> 00:07:13.803 - Or this is dumb why is this like this and that's what I 00:07:13.803 --> 00:07:17.175 - want to fix. That's what I think we all want to make 00:07:17.175 --> 00:07:19.142 - better, so OK back over to UCD. 00:07:21.840 --> 00:07:24.210 - Let's me see B. Uh. 00:07:25.890 --> 00:07:28.774 - So what we're going to do is jump into our app, and I think 00:07:28.774 --> 00:07:30.628 - CR I missed the Tuesday training, but basically what 00:07:30.628 --> 00:07:33.306 - we're going to do is just bring it up and kind of play 00:07:33.306 --> 00:07:35.984 - with it and get it up and running and try to bake in 00:07:35.984 --> 00:07:37.220 - some new features. Is that right? 00:07:38.620 --> 00:07:42.208 - Yeah, and I was thinking that we could kind of play around with 00:07:42.208 --> 00:07:45.796 - it together as a group, and yeah, so let's go ahead and dive 00:07:45.796 --> 00:07:48.832 - in. See, it sounds like everyone wants against their get their 00:07:48.832 --> 00:07:52.420 - hands dirty here now let me just kind of confirm what the group 00:07:52.420 --> 00:07:55.456 - do. You guys have access to the GitHub we shared that 00:07:55.456 --> 00:07:58.768 - previously, but do you have access to that? You want us to 00:07:58.768 --> 00:08:02.080 - resend it so you can make sure you've got the files locally 00:08:02.080 --> 00:08:05.944 - with the hands-on piece we want to get into. I want to say we're 00:08:05.944 --> 00:08:07.600 - on Chapter 7 if that's correct 00:08:07.600 --> 00:08:12.989 - CD. So when you say by sharing file, was it the upsetting 00:08:12.989 --> 00:08:17.417 - Jason or was it something else? Yeah, that was it and it 00:08:17.417 --> 00:08:20.738 - has the connection string in it to the database. 00:08:22.630 --> 00:08:26.335 - So I posted the link to the GitHub in the in the chat 00:08:26.335 --> 00:08:30.040 - here. So you should just be able to pull it and then the 00:08:30.040 --> 00:08:32.890 - only thing like we were talking about last week and 00:08:32.890 --> 00:08:36.025 - kind of what you were just went over is just basically 00:08:36.025 --> 00:08:38.590 - changing the connection string to what CR posted previously 00:08:38.590 --> 00:08:42.295 - and you should just be able to connect to the database on SQL 00:08:42.295 --> 00:08:46.000 - be so you don't have to do a migration or make a database 00:08:46.000 --> 00:08:47.140 - or anything like that. 00:08:49.770 --> 00:08:52.902 - In I will stay as well. I'm since everybody doesn't have the 00:08:52.902 --> 00:08:56.034 - book. For those of you that do, this might be something that 00:08:56.034 --> 00:08:59.166 - you've already covered, but all you have to do, or whenever you 00:08:59.166 --> 00:09:02.298 - open the solution in Visual Studio code to get the front end 00:09:02.298 --> 00:09:05.430 - around. It's not separate and they kind of covered in the book 00:09:05.430 --> 00:09:08.823 - and we kind of covered it a little bit at the beginning, but 00:09:08.823 --> 00:09:12.477 - all you have to do is just hit the Big Green play button in 00:09:12.477 --> 00:09:15.609 - Visual Studio and that will go ahead and start your your front 00:09:15.609 --> 00:09:19.002 - end as well, and then it should open it in your default browser 00:09:19.002 --> 00:09:24.438 - if not. I don't think it's 4200 like angular apps usually are. I 00:09:24.438 --> 00:09:28.618 - think it's something else. I could be mistaken though, but 00:09:28.618 --> 00:09:34.888 - it'll it'll be in ZAP. It spins up like an ISA local IIS so it 00:09:34.888 --> 00:09:36.978 - just picks it random port. 00:09:38.390 --> 00:09:42.537 - And just as another note here, if you guys would, once you have 00:09:42.537 --> 00:09:46.365 - your local stood up when you raise your hand in the channel 00:09:46.365 --> 00:09:51.161 - and teams. And just let us know once we get four or five of the 00:09:51.161 --> 00:09:54.365 - team members who have their local spun up, then will kind of 00:09:54.365 --> 00:09:55.433 - start digging in here. 00:09:56.320 --> 00:09:56.800 - Ann 00:09:57.830 --> 00:09:59.230 - and if you have any questions or 00:09:59.230 --> 00:10:02.574 - you run into issue. Is why you're getting it spun out. If 00:10:02.574 --> 00:10:06.270 - you would go ahead and post those to the channel and the 00:10:06.270 --> 00:10:09.966 - more detail you can give on the error or the issue would 00:10:09.966 --> 00:10:13.354 - be preferred, but that will kind of get the whole team 00:10:13.354 --> 00:10:16.742 - responding and then you know if it's something that we can, 00:10:16.742 --> 00:10:19.206 - we'll just address it by talking about it. 00:10:21.250 --> 00:10:24.004 - Yeah, we're doing Chapter 7 right? Yes, Chapter 7. 00:10:26.440 --> 00:10:30.092 - Thanks and worst case scenario, we can also screen, share and 00:10:30.092 --> 00:10:31.420 - debug is a group. 00:10:32.290 --> 00:10:36.546 - And do you think it if you want to volunteer, I think it would 00:10:36.546 --> 00:10:39.890 - be great if someone wanted to actually drive other than Chris 00:10:39.890 --> 00:10:43.842 - awry, and we can kind of talk through some changes that we can 00:10:43.842 --> 00:10:49.178 - make. An if if you guys have any you know specific ideas, feel 00:10:49.178 --> 00:10:53.585 - free to throw him out there, but we could do some small things 00:10:53.585 --> 00:10:57.992 - like changing the you know the way that it kind of like does 00:10:57.992 --> 00:11:01.043 - autocomplete or looks up records. Maybe add some fields. 00:11:01.043 --> 00:11:05.111 - Would be interesting, that might be a helpful exercise to add a 00:11:05.111 --> 00:11:08.162 - few fields. We could add additional database tables and 00:11:08.162 --> 00:11:11.891 - kind of extend the schema and see how to do that. 00:11:12.580 --> 00:11:15.343 - And kind of go through that whole process. Maybe 00:11:15.343 --> 00:11:16.878 - add like people 2 cities. 00:11:18.320 --> 00:11:22.300 - Or maybe like subdivisions or neighborhoods. You know, I don't 00:11:22.300 --> 00:11:25.484 - know. There's something like that might be instructional. 00:11:26.110 --> 00:11:28.140 - But if you guys have other suggestions, feel free to 00:11:28.140 --> 00:11:28.749 - throw out there. 00:11:32.160 --> 00:11:33.270 - OK, Great Heather. 00:11:34.410 --> 00:11:37.466 - And also Patrick good job. Thank you guys. 00:11:38.910 --> 00:11:42.306 - Are you guys getting when you click on the cities are getting 00:11:42.306 --> 00:11:45.208 - data? I'm getting constantly loading. 00:11:47.500 --> 00:11:51.335 - Why don't you show your screen you are thank you, Ann. If you 00:11:51.335 --> 00:11:54.580 - have a question like you're running into an issue, I guess 00:11:54.580 --> 00:11:58.120 - the raising of the hand is kind of Binary, but if you 00:11:58.120 --> 00:12:01.660 - have a question just posted to the channel you would OK. And 00:12:01.660 --> 00:12:04.905 - with that I think we have enough team members who have 00:12:04.905 --> 00:12:05.790 - gotten it working. 00:12:08.430 --> 00:12:10.620 - Oh, behind scissors working KB. 00:12:11.190 --> 00:12:14.872 - Yes, OK, yeah. I think we. I think we have enough of a quorum 00:12:14.872 --> 00:12:18.028 - that we can go ahead and dive in an if you would. 00:12:18.940 --> 00:12:22.108 - Once you do get your local working, just go ahead and put 00:12:22.108 --> 00:12:25.804 - your hand up and keep it up and at some point in the next, 00:12:25.804 --> 00:12:28.972 - let's say 5 to 10 minutes will go ahead and put everybody's 00:12:28.972 --> 00:12:31.612 - hands down and using for the traditional thing of asking 00:12:31.612 --> 00:12:31.876 - questions. 00:12:33.190 --> 00:12:37.026 - OK, So what do you guys think? Do we want to go ahead and 00:12:37.026 --> 00:12:39.766 - like add another entity and another component and kind of 00:12:39.766 --> 00:12:43.328 - go through that whole process? Or do we want to kind of play 00:12:43.328 --> 00:12:44.698 - with one that's already there? 00:12:47.730 --> 00:12:48.768 - Can we speak? 00:12:50.090 --> 00:12:50.400 - Way. 00:12:51.980 --> 00:12:55.990 - I I personally would like to make another entity that's 00:12:55.990 --> 00:13:00.802 - combined of let's say person there and then we had four. In 00:13:00.802 --> 00:13:05.614 - case to cities and countries, or like where the person is from. 00:13:05.614 --> 00:13:09.624 - Yeah, OK, cool. What is everyone else here? Here alternate 00:13:09.624 --> 00:13:10.827 - suggestions option a. 00:13:11.640 --> 00:13:13.968 - Your temper here OK? 00:13:14.550 --> 00:13:18.708 - OK cool alright so speak now if you have an alternate 00:13:18.708 --> 00:13:22.110 - suggestion. Otherwise we'll go ahead with that. Sounds fun. 00:13:22.820 --> 00:13:27.154 - OK, now who would like to volunteer to show their screen? 00:13:27.154 --> 00:13:32.276 - You don't? You know you're not going to be perfect. None of us 00:13:32.276 --> 00:13:37.398 - are. We're all human. OK, so I will volentold one of you guys 00:13:37.398 --> 00:13:42.520 - who has your hand raised. Let me know if you are willing to 00:13:42.520 --> 00:13:46.854 - volunteer yourself, but I'd love for someone to drive us. Who 00:13:46.854 --> 00:13:48.430 - would be so willing. 00:13:49.670 --> 00:13:54.213 - I can do it if nobody. OK, great thanks, your hero 00:13:54.213 --> 00:13:56.278 - Igor, you are a hero. 00:13:58.240 --> 00:14:03.098 - OK, So what I will do is start from the database. Yeah we need 00:14:03.098 --> 00:14:05.180 - to create a person data table. 00:14:05.820 --> 00:14:10.970 - And maybe make a copy of an existing existing one. 00:14:11.570 --> 00:14:14.396 - I'm just are these. Yeah these 00:14:14.396 --> 00:14:19.570 - are the. No, these are DTO's, but where are the should be 00:14:19.570 --> 00:14:20.998 - inside models I think. 00:14:23.400 --> 00:14:23.860 - Oh yeah. 00:14:25.400 --> 00:14:27.468 - These were has the. 00:14:28.670 --> 00:14:30.410 - Foreign key to. 00:14:31.160 --> 00:14:34.200 - Are there related I wasn't 00:14:34.200 --> 00:14:38.096 - looking properties? So this is great. Just hearing Igor 00:14:38.096 --> 00:14:41.432 - think about this. He's trying to figure out how can I take 00:14:41.432 --> 00:14:43.934 - something that's already there and copy it. And the 00:14:43.934 --> 00:14:46.714 - big thing he's focusing on is the foreign key relationship. 00:14:48.400 --> 00:14:54.088 - Probably country has a foreign key to city because it has lists 00:14:54.088 --> 00:14:55.984 - of cities on it. 00:14:56.940 --> 00:15:00.540 - And just as a reminder for everyone, this is entity 00:15:00.540 --> 00:15:04.500 - framework code first, and it's basically using the C Sharp code 00:15:04.500 --> 00:15:08.460 - to generate the tables and then interact with the tables. So 00:15:08.460 --> 00:15:13.500 - that's why he's going to add a table via the C Sharp code. Just 00:15:13.500 --> 00:15:15.300 - a friendly reminder for anyone. 00:15:16.270 --> 00:15:22.195 - Yeah, but I'm not sure of is we should have a field. If I'm not 00:15:22.195 --> 00:15:24.170 - mistaken that says foreign key. 00:15:25.110 --> 00:15:30.643 - Yeah, the way that this works. This is actually using that 00:15:30.643 --> 00:15:36.679 - public virtual on Line 70. Yeah, and then it's using if you. 00:15:38.230 --> 00:15:40.138 - You then look at the city 00:15:40.138 --> 00:15:44.185 - itself. You should see a country. I think it's The 00:15:44.185 --> 00:15:48.325 - Country ID. Yeah, there you go and there's the foreign key. So 00:15:48.325 --> 00:15:52.465 - foreign keys from the city to the country. Hahaha OK, OK, So 00:15:52.465 --> 00:15:56.950 - what we need? We probably need to start off. This is the model 00:15:56.950 --> 00:16:01.090 - that we need. We probably want to create a person that's going 00:16:01.090 --> 00:16:06.443 - to have. Boring key looking to the city if we wanna say that 00:16:06.443 --> 00:16:08.561 - person is from a certain city. 00:16:10.520 --> 00:16:12.299 - Am I correct? 00:16:13.520 --> 00:16:18.070 - So what I would do? Do we want to create new or just copy 00:16:18.070 --> 00:16:20.345 - paste? Or do you wanna want me 00:16:20.345 --> 00:16:24.984 - to? They want me to copy with me. I would probably copy and 00:16:24.984 --> 00:16:26.394 - paste from the city, yeah? 00:16:27.850 --> 00:16:32.197 - Happy face and then I would rename it to. 00:16:36.330 --> 00:16:36.990 - Person. 00:16:43.290 --> 00:16:44.670 - And then I would. 00:16:47.580 --> 00:16:52.057 - Name everything that needs to be renamed and the person is 00:16:52.057 --> 00:16:53.278 - probably gonna have. 00:16:55.250 --> 00:16:57.340 - Ah. Different. 00:16:58.350 --> 00:17:01.730 - Type of fields. So it's gonna help name then we 00:17:01.730 --> 00:17:03.420 - can do a last name. 00:17:12.670 --> 00:17:13.240 - Ah. 00:17:14.940 --> 00:17:19.802 - Person doesn't have any eyes. I think we should say like 00:17:19.802 --> 00:17:21.570 - nickname an maybe like. 00:17:22.850 --> 00:17:24.020 - Coding skill level. 00:17:25.040 --> 00:17:27.440 - That way we can put our team members names in here and 00:17:27.440 --> 00:17:28.440 - make fun of each other. 00:17:29.700 --> 00:17:30.840 - Veronica thinks it's funny. 00:17:32.470 --> 00:17:33.289 - It's pretty funny. 00:17:34.770 --> 00:17:35.769 - Why you doing? 00:17:40.350 --> 00:17:41.180 - K. 00:17:45.630 --> 00:17:47.018 - These are just the. 00:17:50.160 --> 00:17:52.180 - The accounts that left. 00:17:53.420 --> 00:17:55.926 - Then we're left from the other people. 00:17:57.940 --> 00:17:59.030 - Gather file. 00:18:00.720 --> 00:18:01.320 - Do you have? 00:18:04.280 --> 00:18:06.880 - OK, this one not mapped. 00:18:08.490 --> 00:18:10.350 - Property 2 cities. 00:18:12.510 --> 00:18:17.640 - Did you start count OK? This one I'm not. So if you want we could 00:18:17.640 --> 00:18:22.086 - do total person persons I guess, or people I think I would name 00:18:22.086 --> 00:18:25.506 - it persons just for consistency. I don't know. That's an 00:18:25.506 --> 00:18:26.874 - interesting question for any. 00:18:27.700 --> 00:18:28.390 - Technical. 00:18:29.840 --> 00:18:32.588 - Count of the people perceiving, yeah. 00:18:34.290 --> 00:18:35.160 - I'm serious. 00:18:36.660 --> 00:18:41.520 - A table that needed you know a singular moose and also then 00:18:41.520 --> 00:18:44.780 - plural moose. Oarfish, how would you do? 00:18:48.940 --> 00:18:49.639 - No, thank you. 00:18:53.120 --> 00:18:58.850 - Turn series, but cities was bought a list of there. 00:19:00.760 --> 00:19:01.080 - It's. 00:19:02.680 --> 00:19:03.130 - Here. 00:19:04.430 --> 00:19:04.810 - This. 00:19:29.280 --> 00:19:29.970 - Where is. 00:19:33.410 --> 00:19:37.790 - Where is the IT should have this is private member, isn't it? 00:19:40.800 --> 00:19:42.048 - Not seeing it. 00:19:46.770 --> 00:19:49.566 - Does anybody see anything hidden here? 00:19:50.910 --> 00:19:51.330 - See what? 00:19:53.100 --> 00:19:55.388 - This field Heights here. 00:20:12.750 --> 00:20:16.281 - What do we want? We want coding level as well as 00:20:16.281 --> 00:20:17.565 - that what we said. 00:20:20.670 --> 00:20:22.806 - What do we want coding level to be? 00:20:26.720 --> 00:20:30.620 - It should be an enum and then have some silly levels in there 00:20:30.620 --> 00:20:32.420 - so no one gets feelings hurt. 00:20:34.370 --> 00:20:36.596 - Then we have to create the event. 00:20:38.470 --> 00:20:40.360 - Are we gonna put it here? 00:20:42.790 --> 00:20:43.370 - Movies. 00:20:46.850 --> 00:20:48.730 - Being this 00:20:50.640 --> 00:20:51.840 - public enum. 00:20:55.980 --> 00:21:02.475 - Almost. What's the what I usually do is I go online and 00:21:02.475 --> 00:21:03.840 - search for definition. 00:21:06.380 --> 00:21:07.150 - After 2. 00:21:08.760 --> 00:21:11.736 - Does anybody wanna assist or I'm just gonna? 00:21:46.170 --> 00:21:48.770 - And for the team in the background, are you guys 00:21:48.770 --> 00:21:51.630 - able to do this at the same time or try to? 00:21:54.100 --> 00:21:56.737 - It might be very instructional if you want to. 00:21:58.190 --> 00:22:01.973 - I think we can share this code file once it's working too, but. 00:22:03.620 --> 00:22:06.100 - I would highly advise or just doing yourself because there's 00:22:06.100 --> 00:22:08.580 - nothing like stabbing 'cause if somebody else stubs their toes 00:22:08.580 --> 00:22:11.804 - and that you kind of watch it. You don't really learn as much 00:22:11.804 --> 00:22:13.540 - as if you don't stub your own 00:22:13.540 --> 00:22:16.396 - toes. 'cause I think that's the that's the way that 00:22:16.396 --> 00:22:17.292 - works for me anyway. 00:22:19.450 --> 00:22:22.882 - I'm not just yet, I'm trying to. I'm in Chapter 7 and my 00:22:22.882 --> 00:22:26.314 - app started, but I don't have a lot of the stuff that Igor 00:22:26.314 --> 00:22:28.690 - is showing, so I'm trying to figure that out. 00:22:33.820 --> 00:22:35.310 - Do you need me to?00:22:37.780 --> 00:22:38.990 - Explain something. 00:22:40.460 --> 00:22:44.352 - Or no, I don't think so. I mean, I'm just like missing. Like a 00:22:44.352 --> 00:22:45.464 - lot of things like. 00:22:47.160 --> 00:22:51.840 - But I'm not sure why I'm but I'm just trying to look at it now, 00:22:51.840 --> 00:22:53.088 - but now I don't. 00:22:53.720 --> 00:22:55.118 - Think you need to repeat anything. 00:23:03.220 --> 00:23:09.556 - K So what do we want to have value says Umes 00:23:09.556 --> 00:23:13.588 - recording levels she RA he man skeletor. 00:23:15.210 --> 00:23:16.970 - I'm gonna I'm gonna say. 00:23:18.630 --> 00:23:23.950 - Do you want to do that? We can that snarf. Thank you. Yes, I 00:23:23.950 --> 00:23:27.750 - was thinking we could go with like bronze, silver, gold, 00:23:27.750 --> 00:23:32.310 - platinum and then I think you also have to have like eagle 00:23:32.310 --> 00:23:34.210 - face as like the ultimate. 00:23:37.700 --> 00:23:41.451 - Or one of the words that James or Jesse just said, 00:23:41.451 --> 00:23:42.133 - Because Yeah. 00:23:44.460 --> 00:23:47.484 - And he man, or what was it? 00:23:48.950 --> 00:23:49.350 - Ah. 00:23:51.160 --> 00:23:55.430 - Is this how you spell? There is a dash and then a capital R. 00:23:57.380 --> 00:23:59.170 - All Jabberwocky. 00:24:02.970 --> 00:24:07.793 - Yeah, it's not gonna let you have that dash. It thinks it's a 00:24:07.793 --> 00:24:08.906 - subtraction operator underscore. 00:24:10.760 --> 00:24:11.860 - I'd let you do underscore. 00:24:13.900 --> 00:24:14.810 - Good enough. 00:24:17.610 --> 00:24:21.948 - OK, So what do we have here? Coding levels? 00:24:24.210 --> 00:24:25.989 - Actually this is. 00:24:28.410 --> 00:24:33.582 - Oh, shoot the enum be here because this is entity I think 00:24:33.582 --> 00:24:38.754 - we should not have this as an entity or am I wrong? 00:24:40.700 --> 00:24:44.648 - Yes, you asked SQL support enums doesn't it? I mean it converts 00:24:44.648 --> 00:24:48.925 - it to an int. Yeah, it's gonna say it's just an integer, so. 00:24:51.490 --> 00:24:54.118 - That works for me, though if you want it to be aesthetic 00:24:54.118 --> 00:24:56.746 - enum that is never changed, then you would keep it as an 00:24:56.746 --> 00:24:59.593 - enum. If you want it to be a value that's going to change 00:24:59.593 --> 00:25:01.783 - overtime and add records to database so that people can 00:25:01.783 --> 00:25:04.630 - link to it that way, then you need a separate entity for it. 00:25:05.680 --> 00:25:09.895 - OK, but if this is going to be static then I can leave it like 00:25:09.895 --> 00:25:12.986 - this. Yeah, that's what you said. Yeah, OK, you have a 00:25:12.986 --> 00:25:16.077 - capital E on your coding levels enum type. Thank you for 00:25:16.077 --> 00:25:19.449 - pointing that out. I was going to say something and you have 00:25:19.449 --> 00:25:22.259 - your coding level as a field instead of a property. 00:25:24.590 --> 00:25:30.026 - And then that list that should that should be in this class 00:25:30.026 --> 00:25:34.103 - file. That should be a virtual just of city. 00:25:35.500 --> 00:25:37.678 - Some notes in the chat if you want to see it. 00:25:39.830 --> 00:25:43.358 - What was the second thing you said after capital Y? You said 00:25:43.358 --> 00:25:46.592 - something else. You have enough field right now instead of a 00:25:46.592 --> 00:25:49.986 - property. About where it's a re actually. 00:25:51.670 --> 00:25:55.102 - Level a variable. Yeah, there you go. You have it as a 00:25:55.102 --> 00:25:57.676 - field because you don't have a getter and Setter. 00:25:59.290 --> 00:26:03.658 - Should be a property, yeah? Also another thing to note is Gold is 00:26:03.658 --> 00:26:07.690 - now worth quite a bit more than platinum, so it should probably 00:26:07.690 --> 00:26:08.698 - be above platinum. 00:26:10.130 --> 00:26:12.968 - That's amazing, is that true? What? 00:26:14.510 --> 00:26:17.513 - I just love how your brain works, but it's still awesome. 00:26:20.470 --> 00:26:24.166 - Question did you? Did you just already know that or did you? 00:26:24.166 --> 00:26:28.170 - Did you decide to look up the price of gold and platinum just 00:26:28.170 --> 00:26:32.482 - to verify? No, I have a closet full of gold bars that I'm. 00:26:33.910 --> 00:26:37.180 - My friend, actually Brennan, I think. 00:26:38.710 --> 00:26:41.636 - House, yeah what's what's your address again? 00:26:45.380 --> 00:26:48.877 - Are you armed or no, and then the list as people online 60 00:26:48.877 --> 00:26:49.953 - should just be people. 00:26:51.050 --> 00:26:55.780 - Yeah, more person rather armed with a big socks that fulfil 00:26:55.780 --> 00:27:00.080 - bars. It's really heavy. OK Alright, fair enough, like a 00:27:00.080 --> 00:27:03.640 - flail. What did you say about the list of person? 00:27:05.390 --> 00:27:06.890 - It should be just a person 00:27:06.890 --> 00:27:11.085 - instead of a list. And I think that we want to get rid of the 00:27:11.085 --> 00:27:12.375 - Jason ignore on it as well. 00:27:15.280 --> 00:27:19.141 - If it is it supposed to be person person or is 00:27:19.141 --> 00:27:21.949 - it person people? I think person person OK. 00:27:23.720 --> 00:27:28.268 - I'm sorry you know what that's supposed to be city city 'cause 00:27:28.268 --> 00:27:32.437 - we're trying to get our reference to the city object. So 00:27:32.437 --> 00:27:36.985 - line 60 should be or 59 cities. Cities that are person person. 00:27:42.940 --> 00:27:47.388 - Shouldn't we have foreign key pointing to the? 00:27:49.770 --> 00:27:54.318 - As we had in the city, wasn't Siri pointing? Don't we need 00:27:54.318 --> 00:27:58.258 - this? There I go to navigation properties. 00:28:01.620 --> 00:28:04.940 - What did you say? Navigation properties 00:28:06.500 --> 00:28:08.330 - 56956 00:28:12.490 --> 00:28:15.766 - I'm just trying to do the same thing on the person, but it's 00:28:15.766 --> 00:28:18.538 - gonna be city city instead of country, country on the person. 00:28:20.040 --> 00:28:20.510 - Right? 00:28:22.290 --> 00:28:27.568 - We need to keep pointing from person to the city, not to the 00:28:27.568 --> 00:28:32.034 - country, but to the city. Becausw person will be apart of. 00:28:32.034 --> 00:28:36.906 - Yeah, we basically need CD ID foreign key to city and then. 00:28:37.670 --> 00:28:38.680 - City city 00:28:41.260 --> 00:28:43.168 - don't say that three times fast. 00:28:45.180 --> 00:28:47.700 - Where did they put this in the? 00:28:50.260 --> 00:28:51.919 - Region region, region. 00:28:53.120 --> 00:28:54.660 - In the normal properties. 00:29:05.800 --> 00:29:06.370 - Siri 00:29:10.090 --> 00:29:10.580 - Superman. 00:29:17.100 --> 00:29:23.040 - What is this country thing? Does anybody know what is this one? 00:29:23.040 --> 00:29:25.020 - Was this one needed? 00:29:31.950 --> 00:29:33.118 - Go to your person. 00:29:34.470 --> 00:29:37.863 - It's giving us the object whenever we're doing like 00:29:37.863 --> 00:29:38.617 - the Intellisense. 00:29:39.960 --> 00:29:42.004 - Instead of just having the ID value. 00:29:45.920 --> 00:29:47.360 - So on 60. 00:29:48.710 --> 00:29:51.010 - Actually you have it there, so again, yeah, just city 00:29:51.010 --> 00:29:51.470 - city there. 00:29:52.600 --> 00:29:55.750 - And then get rid of the navigation property that's. 00:29:56.470 --> 00:29:57.769 - Studies on 60. 00:30:08.220 --> 00:30:11.278 - And then you have a two people thing here that's referencing 00:30:11.278 --> 00:30:12.390 - something that doesn't exist. 00:30:14.020 --> 00:30:18.388 - OK, both boys, so I thought that this was supposed to be some 00:30:18.388 --> 00:30:21.748 - kind of counter. How many people are in the city? 00:30:22.560 --> 00:30:25.189 - Which would be on the city record, not on the person 00:30:25.189 --> 00:30:25.428 - record. 00:30:27.960 --> 00:30:31.733 - We're trying to do a count of the people for the 00:30:31.733 --> 00:30:32.419 - people entity. 00:30:33.590 --> 00:30:37.906 - So just roll over the people and see what the issue is. Is 00:30:37.906 --> 00:30:40.562 - probably some access modifier issues that that people 00:30:40.562 --> 00:30:43.550 - properties inside the city class that you're looking at 00:30:43.550 --> 00:30:44.546 - the person class. 00:30:50.430 --> 00:30:53.478 - Still where she if we want that count? 00:30:54.930 --> 00:30:57.920 - I think James is saying change it to person, right? 00:30:58.550 --> 00:30:59.160 - No. 00:31:00.370 --> 00:31:02.878 - And there I think it's misspelled, isn't it? Or am I 00:31:02.878 --> 00:31:05.158 - just so we're inside the person class? If you're trying 00:31:05.158 --> 00:31:08.122 - to count how many people are in the city, you need to be 00:31:08.122 --> 00:31:09.490 - doing this on the city glass. 00:31:14.170 --> 00:31:16.780 - So go to like pull up your city class. 00:31:18.290 --> 00:31:22.360 - Yes you can. You can you elaborate little about this 00:31:22.360 --> 00:31:25.616 - client side properties? What is this referring to? 00:31:26.680 --> 00:31:31.300 - We're just trying to get the account into the client side 00:31:31.300 --> 00:31:36.340 - so that you don't have to like call to the database for 00:31:36.340 --> 00:31:37.180 - record counts. 00:31:38.670 --> 00:31:41.666 - And I think that the way that the book talks about it. This is 00:31:41.666 --> 00:31:42.950 - like a way to do it. 00:31:45.190 --> 00:31:48.110 - So that it's not actually putting the column on the 00:31:48.110 --> 00:31:51.322 - database table, but it's giving you access to it in the 00:31:51.322 --> 00:31:53.658 - model, and it's not necessarily the cleanest way 00:31:53.658 --> 00:31:57.746 - in the world, but it's a way to put it in there, and James 00:31:57.746 --> 00:32:00.374 - is right, it looks like whenever you copied, I'm 00:32:00.374 --> 00:32:03.294 - guessing you copied from the country instead of the city. 00:32:03.294 --> 00:32:04.170 - So yeah, exactly. 00:32:07.160 --> 00:32:07.910 - Here. 00:32:09.800 --> 00:32:14.528 - OK, now city needs a a list of people person called people. 00:32:28.470 --> 00:32:30.690 - And it needs to be a public virtual with a 00:32:30.690 --> 00:32:31.356 - getter and Setter. 00:32:48.390 --> 00:32:53.590 - So now on the on the list of the cities we will get the count of 00:32:53.590 --> 00:32:55.540 - the people in the city, OK? 00:32:57.970 --> 00:32:58.220 - Yeah. 00:33:00.710 --> 00:33:01.470 - Send this. 00:33:03.480 --> 00:33:06.960 - Do I need to? Is everybody else following? Do I need to? 00:33:08.410 --> 00:33:11.100 - Go through anything again I. 00:33:12.610 --> 00:33:17.020 - I have an error in my city dot CS somewhere. I'm sorry I was 00:33:17.020 --> 00:33:18.280 - just messing with somebody. 00:33:20.120 --> 00:33:21.128 - I don't have everything. 00:33:22.370 --> 00:33:27.186 - So city, the only change that we did in the city, we grab the 00:33:27.186 --> 00:33:30.970 - region, client side properties and you can get it from the. 00:33:32.470 --> 00:33:34.171 - Where did you get it from? From 00:33:34.171 --> 00:33:36.775 - the country? Where did we did we 00:33:36.775 --> 00:33:39.830 - start from? And actually it was. 00:33:45.930 --> 00:33:50.088 - So we we started copying Siri, right? 00:33:52.690 --> 00:33:57.050 - Oh no, we started copying country. OK, we started copying 00:33:57.050 --> 00:34:00.974 - country. So from the country we got this code. 00:34:01.930 --> 00:34:05.557 - How many cities in our in the country? And then it makes sense 00:34:05.557 --> 00:34:08.905 - that we are counting how many people are there in the city? 00:34:08.905 --> 00:34:12.532 - And I I would just as a side note, if you're starting from 00:34:12.532 --> 00:34:15.322 - scratch, I would recommend copying the city level if you 00:34:15.322 --> 00:34:18.670 - haven't already made a copy. I know you've already got it built 00:34:18.670 --> 00:34:21.460 - out eager and you figured it out, but other people. 00:34:28.060 --> 00:34:31.220 - I'm just gonna wait a little to see if everybody's. 00:34:33.390 --> 00:34:34.569 - On the same. 00:34:35.670 --> 00:34:36.510 - Check. 00:34:37.630 --> 00:34:38.140 - Thanks. 00:34:39.570 --> 00:34:43.035 - And if you can, if you're able to compile yours and 00:34:43.035 --> 00:34:45.870 - verify that it works and updates the database, that 00:34:45.870 --> 00:34:49.335 - would be really helpful. And then we can. You could share 00:34:49.335 --> 00:34:51.225 - this code file to the group. 00:34:53.150 --> 00:34:54.160 - OK, honey. 00:34:55.760 --> 00:34:56.920 - Building the. 00:34:58.080 --> 00:34:58.830 - Project. 00:35:02.860 --> 00:35:06.045 - Oh my error was that I didn't have an end region, that's it. 00:35:10.120 --> 00:35:13.108 - I was actually something I wanted to ask about. I know that 00:35:13.108 --> 00:35:16.096 - we took that typically is done in like large code files, but 00:35:16.096 --> 00:35:19.333 - why would we add a region in such a small code file like 00:35:19.333 --> 00:35:20.578 - what's the purpose of that? 00:35:23.410 --> 00:35:27.492 - Consistency and it makes it a little easier to see you know if 00:35:27.492 --> 00:35:30.946 - every file was organized for all the navigation properties in the 00:35:30.946 --> 00:35:34.714 - same spot in every file. It's easier to compare and update and 00:35:34.714 --> 00:35:38.482 - ensure that other people aren't doing code in the same file and 00:35:38.482 --> 00:35:40.052 - putting stuff in the other 00:35:40.052 --> 00:35:44.520 - places. It's less likely to happen wrong order, I guess. My 00:35:44.520 --> 00:35:48.360 - question my might even be more basic than that, like So what? 00:35:48.360 --> 00:35:52.187 - What's this #like? You know region thing that we just 00:35:52.187 --> 00:35:54.675 - like incorporating Twitter in here like you know. 00:35:56.190 --> 00:35:57.720 - You can collapse a region. 00:35:58.520 --> 00:36:04.307 - Hello OK. And it's nice way group like things together yes, 00:36:04.307 --> 00:36:07.425 - oh. Oh, that's cool. OK, that's 00:36:07.425 --> 00:36:09.518 - really cool. I did not know 00:36:09.518 --> 00:36:10.780 - that. Meet. 00:36:12.240 --> 00:36:17.532 - OK, my build went through what we need to do is add 00:36:17.532 --> 00:36:21.060 - migration and guessing and then update the database. 00:36:22.470 --> 00:36:22.990 - Go. 00:36:26.170 --> 00:36:28.170 - Let me know if you want me. I'll 00:36:28.170 --> 00:36:33.287 - need to share city. I need to share these three files and were 00:36:33.287 --> 00:36:36.824 - World Series CS project file because we added series. 00:36:37.480 --> 00:36:41.380 - Let me know if you want me to share those four files 00:36:41.380 --> 00:36:42.680 - or can everybody build. 00:36:44.870 --> 00:36:46.870 - Absolutely OK. 00:36:51.560 --> 00:36:54.510 - Apparently you can do regions in JavaScript, but it's just 00:36:54.510 --> 00:36:55.690 - a VS code plugin. 00:36:58.820 --> 00:37:00.120 - Which is almost cool. 00:37:11.030 --> 00:37:12.800 - Picture make what I'm gonna do. 00:37:14.830 --> 00:37:17.610 - Hopefully yes. 20 picks up regions, 'cause That's a pretty 00:37:17.610 --> 00:37:20.946 - cool feature and we like to steal stuff from C. Sharp and. 00:37:55.840 --> 00:37:58.164 - OK, so I've sent in the chat. 00:37:59.110 --> 00:37:59.780 - File. 00:38:01.080 --> 00:38:03.000 - Uh, it has. 00:38:04.210 --> 00:38:08.540 - Yes, project file. So what happened is this whenever you 00:38:08.540 --> 00:38:13.736 - add file to the project, your CSS Troy Project file which you 00:38:13.736 --> 00:38:18.499 - can access either through on the disk follow you can double 00:38:18.499 --> 00:38:25.400 - click. Uh, here you can see the list of all the files that 00:38:25.400 --> 00:38:28.220 - have been included, or am I? 00:38:29.700 --> 00:38:31.700 - Is it not here James? 00:38:34.580 --> 00:38:39.717 - Shouldn't project file list of all the files that are included? 00:38:47.000 --> 00:38:48.729 - You have to have saved it first. 00:38:51.430 --> 00:38:54.160 - So if you've added the file, then you need to 00:38:54.160 --> 00:38:55.525 - hit like I save all. 00:38:58.900 --> 00:39:00.304 - And then it should be able to show up. 00:39:01.920 --> 00:39:03.000 - In the project file. 00:39:04.470 --> 00:39:08.826 - Any file that's weird, it's not showing. Normally you don't open 00:39:08.826 --> 00:39:12.390 - a project file without unloading it, unless it's something 00:39:12.390 --> 00:39:13.578 - allowed in.net core. 00:39:15.150 --> 00:39:16.650 - Like unload the project first. 00:39:18.360 --> 00:39:19.865 - Let me just see if I could. 00:39:20.990 --> 00:39:22.650 - See here in there. 00:39:25.730 --> 00:39:27.836 - But it's going to probably show the same thing. 00:39:30.520 --> 00:39:31.170 - Is this? 00:39:33.850 --> 00:39:34.300 - Siri 00:39:36.420 --> 00:39:39.126 - unload the project. That's all I need to do. I don't 00:39:39.126 --> 00:39:40.110 - need to close the. 00:39:42.750 --> 00:39:43.370 - Solution. 00:39:48.560 --> 00:39:50.138 - Let me just close the solution. 00:40:49.350 --> 00:40:50.450 - Blood happened. 00:41:43.210 --> 00:41:47.120 - Yeah, something is as far as I know CSS profile 00:41:47.120 --> 00:41:51.421 - should have a list of all the files in the project. 00:41:51.421 --> 00:41:53.376 - I mean not correct James. 00:41:58.780 --> 00:42:03.076 - I I don't know how that's that's dependent on the project type 00:42:03.076 --> 00:42:06.298 - and I don't know what brought.net core is doing 00:42:06.298 --> 00:42:10.416 - differently. They could have an autofilter that's just trying to 00:42:10.416 --> 00:42:13.332 - pull in all the files automatically. So what's the 00:42:13.332 --> 00:42:14.628 - problem? Sorry, not asking. 00:42:16.150 --> 00:42:19.384 - You open the CS project file because I remember in the 00:42:19.384 --> 00:42:22.324 - previous in the dot NET Framework CSS profile would have 00:42:22.324 --> 00:42:27.028 - a list of all the for the files. And why do you need to file the 00:42:27.028 --> 00:42:30.556 - list of the files inside the project file? Like what are you 00:42:30.556 --> 00:42:34.378 - trying to do with it? I wanted to share the file with everybody 00:42:34.378 --> 00:42:35.848 - so that if somebody adds. 00:42:36.520 --> 00:42:40.156 - My code, like a new class called person and if the project 00:42:40.156 --> 00:42:44.095 - doesn't have it as a list of the files, it will probably well, 00:42:44.095 --> 00:42:47.428 - you wouldn't. You wouldn't want to have them like manually add 00:42:47.428 --> 00:42:51.670 - that the CS prod file you would want them to go to the Visual 00:42:51.670 --> 00:42:55.306 - Studio and then show all files and then right click the file 00:42:55.306 --> 00:42:56.821 - and say include file OK. 00:43:02.340 --> 00:43:07.378 - So in case you've taken those three, actually 4 files, what 00:43:07.378 --> 00:43:10.126 - you actually need is just three 00:43:10.126 --> 00:43:13.940 - files. And then you might not see. I'm not sure. Maybe 00:43:13.940 --> 00:43:15.056 - you will not see. 00:43:16.180 --> 00:43:18.118 - The one that we created person. 00:43:20.120 --> 00:43:23.963 - From city state. Why am I getting all these 00:43:23.963 --> 00:43:25.244 - errors? What happened? 00:43:30.890 --> 00:43:34.210 - So yeah, you would click on the file. 00:43:39.200 --> 00:43:41.027 - Let me just check what happened here. 00:43:42.110 --> 00:43:43.040 - This person. 00:43:54.430 --> 00:43:56.310 - It's probably. 00:44:00.660 --> 00:44:01.960 - Nice nice. 00:44:09.140 --> 00:44:12.310 - It's a country. Where is it really first in front? 00:44:13.650 --> 00:44:14.180 - Um? 00:44:16.410 --> 00:44:21.600 - OK, so. No, I understand what happens, so dot dot net core 00:44:21.600 --> 00:44:24.543 - automatically loads everything that you have in your project. 00:44:24.543 --> 00:44:26.832 - So what happened in my case? Let 00:44:26.832 --> 00:44:32.107 - me explain. I created and. Why am I getting this error? So I 00:44:32.107 --> 00:44:36.965 - wanted to create for you a copy of my let's go into data. I 00:44:36.965 --> 00:44:41.129 - created a copy of the older models and I added CS project 00:44:41.129 --> 00:44:45.640 - file in it because I thought that you will need it but you 00:44:45.640 --> 00:44:49.804 - won't need it because that's the way that all dot NET Framework 00:44:49.804 --> 00:44:54.662 - worked. It has CSS profile and you need it was the list of all 00:44:54.662 --> 00:44:58.132 - the files that are going to be included in the 00:44:58.132 --> 00:45:00.116 - projectapparently.net. Or automatically loads everything 00:45:00.116 --> 00:45:04.450 - that you have in your folder structure? And why am I 00:45:04.450 --> 00:45:08.784 - receiving errors now? Because I hope it models and made models 00:45:08.784 --> 00:45:10.754 - copy and now I have. 00:45:11.540 --> 00:45:15.430 - Two of them and getting probably errors because of that. 00:45:16.900 --> 00:45:18.720 - Because it was saying. 00:45:19.910 --> 00:45:21.230 - That I have. 00:45:23.080 --> 00:45:27.436 - Class person already OK? Yeah that fix the issue. As you can 00:45:27.436 --> 00:45:32.852 - see. So all you wanna do is get those two models that we've 00:45:32.852 --> 00:45:37.124 - changed. We added person. So you want to copy paste person from 00:45:37.124 --> 00:45:40.208 - the. 7 zip that I've added into 00:45:40.208 --> 00:45:45.130 - the chat. And you want Siri as well, because we've made change 00:45:45.130 --> 00:45:49.156 - to the city. Just copy paste those two files in the. 00:45:49.900 --> 00:45:51.028 - For their models. 00:45:52.840 --> 00:45:57.352 - In your project and you'll be on the same track as. I 00:45:57.352 --> 00:45:58.856 - think you eager for. 00:46:00.410 --> 00:46:01.430 - Process of doing that. 00:46:04.020 --> 00:46:09.504 - No problem, so next step. When we finished with that we you 00:46:09.504 --> 00:46:14.074 - definitely wanna build it and see if everything is OK. 00:46:14.860 --> 00:46:18.388 - It should be if those are young 2 files that you've changed. 00:46:21.590 --> 00:46:28.322 - And since those are the entities that will be used to. 00:46:28.910 --> 00:46:34.630 - Modify our database. We need to add migration. Now that we've 00:46:34.630 --> 00:46:36.190 - changed the database. 00:46:36.800 --> 00:46:41.608 - Changed the schema in the.net for the database. 00:46:43.650 --> 00:46:45.939 - So how do we do that we? 00:46:47.500 --> 00:46:49.630 - I'm gonna wait is everybody? 00:46:50.500 --> 00:46:53.206 - OK, if we continue because this is the part that we 00:46:53.206 --> 00:46:54.190 - need to do together. 00:46:55.720 --> 00:46:58.970 - Yeah, let's get a raising of the hands if you're ready to move 00:46:58.970 --> 00:47:00.920 - on. Brendan. 00:47:03.190 --> 00:47:05.518 - Can we move on? I know that you know all of this. 00:47:06.600 --> 00:47:07.400 - Allow it. 00:47:08.540 --> 00:47:09.060 - OK. 00:47:13.160 --> 00:47:14.959 - OK, so you can consider my hand. 00:47:16.780 --> 00:47:18.440 - Yeah, engine. 00:47:19.820 --> 00:47:23.804 - OK, so next thing we need to assume I'm not following along. 00:47:25.950 --> 00:47:29.457 - You're a following if you're making mistakes. 00:47:31.010 --> 00:47:35.378 - Next thing we need to do, you will click on the tools. 00:47:36.300 --> 00:47:40.940 - And you want your new get package manager console. So 00:47:40.940 --> 00:47:45.116 - tools, nougat package manager console. When it expands, click 00:47:45.116 --> 00:47:48.364 - on the console and you will get 00:47:48.364 --> 00:47:54.008 - this console. And here we want to add migration and. 00:47:55.050 --> 00:47:56.358 - There might be. 00:47:57.040 --> 00:48:02.185 - You probably have both entity framework sixand.net, 00:48:02.185 --> 00:48:05.860 - so is it James E.net? 00:48:08.240 --> 00:48:09.980 - Thanks, lash. 00:48:11.120 --> 00:48:12.060 - Ah. 00:48:19.250 --> 00:48:20.159 - What is the? 00:48:23.950 --> 00:48:26.590 - As far as I know, it doesn't give you Intellisense in that. 00:48:29.650 --> 00:48:31.768 - Since when I mean this always. 00:48:32.620 --> 00:48:36.930 - Game intelligence, OK, I think it's dot net the word. 00:48:38.050 --> 00:48:39.550 - And then we do. 00:48:42.420 --> 00:48:43.810 - Migration. 00:48:44.900 --> 00:48:46.760 - And then we would say. 00:48:47.840 --> 00:48:48.520 - Ah. 00:48:49.870 --> 00:48:51.150 - And being. 00:48:54.360 --> 00:48:58.949 - We are giving a name to our migration. I'm gonna try it. We 00:48:58.949 --> 00:49:00.008 - need to set. 00:49:03.850 --> 00:49:04.360 - Snow. 00:49:07.260 --> 00:49:10.308 - Chapter 7 World Series is our. 00:49:11.620 --> 00:49:13.438 - Default project OK. 00:49:14.140 --> 00:49:18.859 - And that is where, yeah, we have only one project that is very 00:49:18.859 --> 00:49:22.852 - dull. Entity DB context and everything is OK. Let's try and 00:49:22.852 --> 00:49:27.571 - see what we get module.net could not be loaded. So what is the 00:49:27.571 --> 00:49:29.023 - word gets in here? 00:49:29.680 --> 00:49:34.040 - Yeah, isn't it? I'm gonna try it without. 00:49:35.560 --> 00:49:38.980 - I it's just that. Or you can type in entity 00:49:38.980 --> 00:49:41.716 - framework, backslash and it works too either way. 00:49:42.780 --> 00:49:47.148 - Yeah, but then it might activate the one that's not dot net core. 00:49:47.148 --> 00:49:48.492 - Let's see what happens. 00:49:49.540 --> 00:49:52.933 - Yeah, we had this issue with mine as well and we had to 00:49:52.933 --> 00:49:55.282 - kind of use the standard like Jesse the same. 00:49:56.980 --> 00:50:00.320 - Hi, so without it usually gives a warning that you. 00:50:00.390 --> 00:50:04.446 - We have 2, two of them installed that it that you need. 00:50:05.790 --> 00:50:10.015 - But the default that it runs is the dot net core one, OK? 00:50:11.330 --> 00:50:13.460 - Then add migration and just been 00:50:13.460 --> 00:50:16.818 - name should. Give you should create the migration 00:50:16.818 --> 00:50:18.210 - which you can find. 00:50:20.250 --> 00:50:20.790 - Green 00:50:22.350 --> 00:50:25.470 - should we type the entity framework, backslash first 00:50:25.470 --> 00:50:26.250 - or no? 00:50:28.400 --> 00:50:34.020 - Minecraft. Doing that, I didn't have to. I just put add 00:50:34.020 --> 00:50:37.476 - migration at hyphen migration and that work for mine. 00:50:40.170 --> 00:50:44.740 - Yeah yeah, default willbe.net core. That's why you don't have 00:50:44.740 --> 00:50:46.568 - to explicitly name it. 00:50:47.270 --> 00:50:50.714 - But I don't get it why it's taking so long as anyone's 00:50:50.714 --> 00:50:51.288 - gone through. 00:50:52.670 --> 00:50:56.212 - Did anyone else had to do it? My mind went instantly, 00:50:56.212 --> 00:50:59.432 - builds, builds, see. It was like instant, yeah, and that's 00:50:59.432 --> 00:51:03.296 - how it should be. I don't know what's wrong with mine. So 00:51:03.296 --> 00:51:06.838 - yeah, if you go to the folder folder migrations you should 00:51:06.838 --> 00:51:08.448 - find that one adding people. 00:51:11.170 --> 00:51:13.730 - Well, my computer froze apparently. 00:51:15.730 --> 00:51:21.252 - OK, somebody will have to take over. Yeah nothing is working 00:51:21.252 --> 00:51:26.568 - for me. I'll maybe get always restart Visual Studio, maybe 00:51:26.568 --> 00:51:28.798 - stop and restart that process. 00:51:38.750 --> 00:51:41.120 - Who I like, your style. You're just gonna kill it. 00:51:42.590 --> 00:51:43.790 - That's what I always do. 00:51:45.660 --> 00:51:49.139 - Beach. Remind me not to mess with you. 00:51:51.830 --> 00:51:56.338 - You know when you kill it, when you exit and then it takes 10 00:51:56.338 --> 00:51:59.880 - more seconds. So something is happening. Which one it is now 00:51:59.880 --> 00:52:02.820 - that's the problem. OK, mixers. 00:52:03.400 --> 00:52:06.388 - I haven't done any work from that connect, rather00:52:06.388 --> 00:52:07.716 - want to save this. 00:52:25.740 --> 00:52:29.447 - And it should be only one running. What we have had 00:52:29.447 --> 00:52:29.784 - mixers. 00:52:30.840 --> 00:52:32.790 - No, I haven't done anything. 00:52:55.040 --> 00:52:57.740 - Well, since I haven't done any work on them, I can kill 00:52:57.740 --> 00:52:58.640 - that one as well. 00:53:22.810 --> 00:53:23.150 - No. 00:53:37.050 --> 00:53:38.920 - Dear. Wait? 00:53:42.810 --> 00:53:43.690 - What happened? 00:53:45.220 --> 00:53:48.379 - In an error. So I'm going to restart my Visual Studio and see 00:53:48.379 --> 00:53:52.834 - if that works. You're getting an error on build or 00:53:52.834 --> 00:53:55.718 - on add migration on add immigration migration. 00:53:57.280 --> 00:54:00.448 - What it is? I posted images. 00:54:02.850 --> 00:54:04.198 - So mine was fired. 00:54:07.160 --> 00:54:08.050 - Syllables. 00:54:17.040 --> 00:54:20.820 - Add migration adding people. 00:54:21.630 --> 00:54:23.748 - Module entity framework. 00:54:29.740 --> 00:54:33.068 - As if you don't have dot net core. 00:54:37.660 --> 00:54:39.000 - But how would he? 00:54:39.940 --> 00:54:42.932 - Build the project and you could have built the project right. 00:54:44.320 --> 00:54:47.330 - Non Visual Studio Twenty 2017 or 2019? 00:54:50.150 --> 00:54:52.360 - Probably 2019. 00:54:53.960 --> 00:54:57.164 - It just gave me. I could have launched it with 2017. It 00:54:57.164 --> 00:54:59.834 - worked, but I couldn't have done some of this stuff. 00:55:00.450 --> 00:55:00.890 - Oh 00:55:03.660 --> 00:55:07.830 - so right click the icon if you have it pinned or if you have an 00:55:07.830 --> 00:55:10.888 - open then but the right click and then you'll see which. 00:55:12.470 --> 00:55:13.130 - 20 00:55:22.530 --> 00:55:24.840 - I think you need to. 00:55:26.530 --> 00:55:30.553 - Well, did you try running import module entity framework? 00:55:32.030 --> 00:55:35.352 - Like it said, I'm not sure. Maybe you don't have it. 00:55:38.940 --> 00:55:40.929 - Correct framework installed. 00:55:42.590 --> 00:55:46.297 - But then again, you wouldn't be able to build the project. 00:55:47.450 --> 00:55:49.526 - Who's running a minute ago so? 00:55:50.990 --> 00:55:53.942 - I don't know what's happening at my computer. 00:55:53.942 --> 00:55:55.049 - OK, finally stabilized. 00:55:56.740 --> 00:55:57.470 - Or not. 00:55:58.770 --> 00:56:00.000 - Running anything, I don't know 00:56:00.000 --> 00:56:05.346 - why it's so. Dot net its decay does not supporttargeting.net. 00:56:06.190 --> 00:56:07.620 - 43.1 00:56:08.680 --> 00:56:12.208 - Oh, you might not have the SDK. Yeah, that's what I thought. 00:56:14.020 --> 00:56:18.716 - To go online and searchfor.net core 3.1 SDK 00:56:18.716 --> 00:56:21.651 - and just install it OK. 00:56:27.940 --> 00:56:30.957 - Let's see I haven't added the migration. 00:56:32.730 --> 00:56:35.310 - I need to redo my work. 00:56:38.270 --> 00:56:39.410 - 2 minutes. 00:56:47.500 --> 00:56:49.092 - Alright, now I'm getting 00:56:49.092 --> 00:56:53.680 - intelligence. Weird that I haven't gotten the first time 00:56:53.680 --> 00:56:55.015 - anyways, and migration. 00:56:58.940 --> 00:57:02.150 - You got running tasks. If you look at the stuff, 00:57:02.150 --> 00:57:05.681 - never mind. They went away on the very bottom left of 00:57:05.681 --> 00:57:08.249 - Visual Studio. Little Blue kind of rectangle thing. 00:57:09.820 --> 00:57:13.993 - That said, you had a running test a second ago. Up there it 00:57:13.993 --> 00:57:18.487 - goes again if you click on it and tell you what it's doing. My 00:57:18.487 --> 00:57:21.697 - problem is that everything froze again that something is running, 00:57:21.697 --> 00:57:25.549 - probably creating migration, but I have no idea why. As you can 00:57:25.549 --> 00:57:27.475 - see, I'm clicking. I'm trying to 00:57:27.475 --> 00:57:29.898 - scroll. It froze again. 00:57:30.510 --> 00:57:33.590 - I don't know what's up, just wondering if maybe you could. 00:57:33.590 --> 00:57:36.950 - Yeah, I guess it's not working, but would be just see what 00:57:36.950 --> 00:57:38.070 - Visual Studio thinks it's 00:57:38.070 --> 00:57:41.215 - currently doing. Yeah, the problem is that I can't 00:57:41.215 --> 00:57:43.415 - even click on that as well. Yeah, yeah. 00:57:44.690 --> 00:57:48.510 - You try a control break that usually like stops whatever 00:57:48.510 --> 00:57:53.094 - Visual Studio is doing, an see if it like cancels the build 00:57:53.094 --> 00:57:54.622 - that's trying to do. 00:57:57.260 --> 00:57:59.500 - Not working. 00:58:01.510 --> 00:58:04.502 - It's like the only thing I ever used to break key 00:58:04.502 --> 00:58:05.590 - on the keyboard for. 00:58:07.820 --> 00:58:12.770 - Control alt break. I really remote desktop and it it it 00:58:12.770 --> 00:58:15.920 - like Minimizes the remote desktop window button. 00:58:17.510 --> 00:58:18.230 - Did nobody. 00:58:19.920 --> 00:58:22.349 - I don't know if if it's the 00:58:22.349 --> 00:58:25.030 - teams there. Chris, we check your chat. 00:58:26.420 --> 00:58:27.150 - Which Chris. 00:58:28.380 --> 00:58:30.280 - There's like 4 CR. 00:58:31.720 --> 00:58:32.170 - Instant. 00:58:34.260 --> 00:58:36.700 - I mean, you know it wasn't you though, right KB? 00:58:38.630 --> 00:58:39.490 - No. 00:58:42.190 --> 00:58:45.060 - I'm wondering if this could be an issue with the 00:58:45.060 --> 00:58:47.930 - database. I know they're like log files that it will 00:58:47.930 --> 00:58:49.652 - generate that we can look at. 00:58:51.360 --> 00:58:54.864 - And then I'm guessing we can change, you know settings to be 00:58:54.864 --> 00:58:58.952 - able to see that, but if it was me, I would just since someone 00:58:58.952 --> 00:59:02.164 - else may have already modified it, I'm just wondering if maybe 00:59:02.164 --> 00:59:04.208 - we don't even need to add the 00:59:04.208 --> 00:59:08.290 - migration now. And you can filter that list of 00:59:08.290 --> 00:59:12.090 - databases and just filter it on. I think it's T&G. 00:59:13.460 --> 00:59:16.541 - The end result we click on the database folder at the top. Or 00:59:16.541 --> 00:59:17.726 - yeah, that's fine, that works. 00:59:23.670 --> 00:59:26.766 - Well his locals getting stuck on the build part which is before 00:59:26.766 --> 00:59:30.120 - it even talks to the database to ask it in Michael Migration. It 00:59:30.120 --> 00:59:32.958 - has to build the project 1st and that's what's failing. It's 00:59:32.958 --> 00:59:36.054 - stuck there. I mean it looks like you're not even like your 00:59:36.054 --> 00:59:39.150 - connection to the database is having a problem too. If you go 00:59:39.150 --> 00:59:40.698 - to active it loads of tables. 00:59:43.120 --> 00:59:46.607 - Yeah no, no one's done the migration yet against the I 00:59:46.607 --> 00:59:49.460 - guess you guys have to run the application before 00:59:49.460 --> 00:59:50.094 - you'll actually. 00:59:52.060 --> 00:59:55.318 - Nobody adding migration won't do anything. Update database will. 00:59:55.318 --> 00:59:59.662 - Yeah, that's what I just that's what I was basically saying. So 00:59:59.662 --> 01:00:02.886 - why don't. Please stop here this week. This gets everyones 01:00:02.886 --> 01:00:06.812 - wheels spinning and then we can pick it up again next week and 01:00:06.812 --> 01:00:10.436 - that will give us a chance to figure this out or something 01:00:10.436 --> 01:00:12.550 - fun to work on over the weekend.