00:00:08.428 --> 00:00:09.338 Alright, we are recording.
00:00:11.698 --> 00:00:13.028 And then you want to share your screen.
00:00:15.598 --> 00:00:17.468 Yeah, can join quick second.
00:00:17.478 --> 00:00:17.838 Let's see.
00:00:17.848 --> 00:00:19.028 Let's do.
00:00:19.478 --> 00:00:20.768 I'm gonna make this for repro.
00:00:29.488 --> 00:00:29.758 Share.
00:00:35.028 --> 00:00:35.368 OK.
00:00:39.118 --> 00:00:42.176 So we're starting from the project, do you have to do
00:00:42.176 --> 00:00:45.629 anything in the project itself or do you have to do this and
00:00:45.629 --> 00:00:46.308 the publish?
00:00:47.598 --> 00:00:48.858 You can do this in the publish.
00:00:49.368 --> 00:00:49.578 OK.
00:00:49.588 --> 00:00:50.748 We'll go ahead and do that real quick.
00:00:56.528 --> 00:00:58.448 Go to stage one where it lives.
00:01:11.268 --> 00:01:13.128 Published where we're able to use their own servers.
00:01:16.638 --> 00:01:18.968 Alright, so currently it is here.
00:01:19.758 --> 00:01:22.413 I'll go ahead and shut it down since I imagine any changes we
00:01:22.413 --> 00:01:24.468 gonna make, we're going to shut it down anyway.
00:01:26.018 --> 00:01:26.238 Yep.
00:01:27.138 --> 00:01:28.288 Alright, so that's stopped.
00:01:28.298 --> 00:01:30.508 OK, so how do I how do I do this?
00:01:31.858 --> 00:01:34.128 OK, so which one do you want?
00:01:34.478 --> 00:01:36.499 So go into the stage cause I send that where you want to do
00:01:36.499 --> 00:01:37.138 the work in folder.
00:01:37.588 --> 00:01:37.708 Yes.
00:01:38.378 --> 00:01:38.888 Ah, OK.
00:01:38.898 --> 00:01:42.128 So right now you have it just in the folder.
00:01:42.598 --> 00:01:45.104 So do you wanna put this like in a separate publish and then a
00:01:45.104 --> 00:01:46.058 separate working folder?
00:01:47.968 --> 00:01:49.218 Here's what I'd like to do.
00:01:49.288 --> 00:01:53.227 I want to have it to where I can just push things to stage and
00:01:53.227 --> 00:01:56.477 not have to worry about overwriting my app settings
00:01:56.477 --> 00:02:00.415 because every time I have to go in I whenever I publish I have
00:02:00.415 --> 00:02:03.228 to delete the app settings and then push it.
00:02:03.318 --> 00:02:04.768 I'd rather it not even worry it.
00:02:03.868 --> 00:02:07.539 So would it be fine if it was like the folder stage and then
00:02:07.539 --> 00:02:11.088 inside of that was a folder called publish and Working or?
00:02:12.978 --> 00:02:15.497 Or we could just have the working here or whatever is
00:02:15.497 --> 00:02:18.389 going to be best where I don't accidentally overwrite the app
00:02:18.389 --> 00:02:18.808 settings.
00:02:20.158 --> 00:02:21.008 Either work.
00:02:21.018 --> 00:02:23.178 I'd probably go with just stage Dash working.
00:02:23.188 --> 00:02:27.422 Then in that case cause the folder being named working isn't
00:02:25.308 --> 00:02:25.488 OK.
00:02:27.422 --> 00:02:28.948 specific Lee required.
00:02:30.118 --> 00:02:31.638 Stage dash working like that.
00:02:32.598 --> 00:02:32.798 Yep.
00:02:33.418 --> 00:02:34.468 OK, do that.
00:02:34.698 --> 00:02:36.946 Alright, so I imagine the app settings are going to go in
00:02:36.018 --> 00:02:40.808 Uh, so go into your stage folder and copy out the web dot config.
00:02:36.946 --> 00:02:37.178 there.
00:02:42.868 --> 00:02:43.968 There should be one in here.
00:02:44.648 --> 00:02:44.868 OK.
00:02:47.038 --> 00:02:48.068 Do I need to leave it in there?
00:02:48.078 --> 00:02:50.068 Can I just cut it or copy it or what?
00:02:49.878 --> 00:02:53.933 You can cut it it your next publishes will still contain it,
00:02:53.933 --> 00:02:55.728 but it shouldn't be needed.
00:02:55.738 --> 00:02:57.768 Once we move it to the working directory here.
00:02:58.678 --> 00:02:59.738 OK, kind of like the app settings.
00:03:00.628 --> 00:03:00.768 Yes.
00:03:01.368 --> 00:03:02.868 OK, alright, so it's there.
00:03:03.678 --> 00:03:08.266 And then you're going to want to edit it, probably using notepad
00:03:06.198 --> 00:03:06.438 Right.
00:03:08.266 --> 00:03:08.548 yet.
00:03:08.858 --> 00:03:14.508 That way we don't have to load up Visual Studio and then in the
00:03:14.508 --> 00:03:20.069 argument section there you just change that to essentially dot
00:03:20.069 --> 00:03:22.628 dot slash and then the stage.
00:03:25.018 --> 00:03:27.798 Because that's just saying go up a full no, not stage, just
00:03:27.798 --> 00:03:28.168 working.
00:03:28.178 --> 00:03:28.668 Just stage.
00:03:29.208 --> 00:03:29.408 OK.
00:03:29.888 --> 00:03:35.753 That's saying you'll find the website application up a folder
00:03:35.753 --> 00:03:40.388 inside the stage folder and it's named that DLL.
00:03:41.118 --> 00:03:41.338 OK.
00:03:43.928 --> 00:03:48.454 And then you should now just be able to change IIS to point at
00:03:48.454 --> 00:03:49.818 stage desk working.
00:03:52.258 --> 00:03:53.038 You'll want to save that.
00:03:54.748 --> 00:03:58.200 Alright, who also want to change the log file standard logout
00:03:58.200 --> 00:03:58.478 file.
00:03:59.258 --> 00:04:03.848 No, cause that'll write it to the uh working directory.
00:04:03.958 --> 00:04:06.613 So then that way if you want to check the logs and stuff, it's
00:04:04.358 --> 00:04:04.568 OK.
00:04:06.613 --> 00:04:07.118 right there.
00:04:06.788 --> 00:04:07.598 Very good, very good.
00:04:08.698 --> 00:04:13.668 So then I change it and the actual site itself OK.
00:04:12.528 --> 00:04:12.658 Yes.
00:04:17.998 --> 00:04:20.978 It's going to be, he noted, buckets.
00:04:26.878 --> 00:04:27.858 Oops, that's what I want to do.
00:04:27.868 --> 00:04:28.118 I want to.
00:04:30.738 --> 00:04:31.259 I wanna go to.
00:04:31.078 --> 00:04:32.258 The amazing numbers they hide.
00:04:32.318 --> 00:04:33.808 It's the advanced settings one.
00:04:36.588 --> 00:04:37.638 Cheers Levisa really.
00:04:40.158 --> 00:04:41.868 A ton of things around the advanced things.
00:04:41.878 --> 00:04:44.025 If you do manage website, there's advanced well and I
00:04:44.025 --> 00:04:45.178 think that one works as well.
00:04:46.488 --> 00:04:47.258 Alright, so the.
00:04:46.488 --> 00:04:48.808 And then the physical path is what you'd be changing.
00:04:50.928 --> 00:04:55.918 Just change that to connect Dash working like that.
00:04:56.668 --> 00:04:56.868 Yep.
00:04:59.158 --> 00:05:02.475 They should be able to hit OK and start the app pool and it
00:05:02.475 --> 00:05:03.138 should work.
00:05:03.898 --> 00:05:04.068 OK.
00:05:07.508 --> 00:05:10.015 Songs you're not loading any other files other than app
00:05:10.015 --> 00:05:10.418 settings.
00:05:12.878 --> 00:05:16.018 Now there's no app settings in the working folder.
00:05:16.898 --> 00:05:19.963 Oh, you'll need to move the app settings into the working folder
00:05:19.963 --> 00:05:20.198 then.
00:05:20.908 --> 00:05:21.128 OK.
00:05:23.998 --> 00:05:25.758 And then probably restart the app pool.
00:05:24.238 --> 00:05:24.608 Why did?
00:05:25.568 --> 00:05:27.868 Why does this have Internet Explorer still?
00:05:31.998 --> 00:05:33.238 To stop that.
00:05:32.418 --> 00:05:33.278 Who knows?
00:05:33.338 --> 00:05:37.481 It's Microsoft server, so they have to keep supporting Internet
00:05:37.481 --> 00:05:39.228 Explorer to like 20-30 Mom.
00:05:41.768 --> 00:05:43.468 Alright, actually, you know what?
00:05:43.478 --> 00:05:46.233 I'm just gonna move it there as long as I know it's going to be
00:05:46.233 --> 00:05:46.448 good.
00:05:46.498 --> 00:05:47.378 So I care about.
00:05:47.958 --> 00:05:49.748 All right, so now that has an app settings.
00:05:49.758 --> 00:05:53.638 It has the error because the app settings weren't found OK.
00:05:54.938 --> 00:05:57.258 And if you restart the app pool it should work.
00:06:03.618 --> 00:06:04.318 Ask ah.
00:06:07.998 --> 00:06:12.878 So now even if I say.
00:06:15.628 --> 00:06:17.048 Delete the app settings entirely.
00:06:20.018 --> 00:06:22.538 And Webb not there anymore.
00:06:23.218 --> 00:06:26.068 Well, the sync time stamps also come over to the working
00:06:26.068 --> 00:06:26.568 directory.
00:06:27.258 --> 00:06:29.278 EI believe so.
00:06:31.848 --> 00:06:35.618 And then I'll just for poops and giggles, delete that too.
00:06:44.498 --> 00:06:45.078 And start.
00:06:50.508 --> 00:06:53.660 So if you're run async, it should write inside the working
00:06:53.660 --> 00:06:54.888 directory of the stuff.
00:07:32.988 --> 00:07:37.158 Yay, and there was much rejoicing.
00:07:41.268 --> 00:07:41.848 All right.
00:07:41.338 --> 00:07:44.772 To be honest, we could probably alter the publish script to
00:07:44.772 --> 00:07:48.321 where it it's able to make this, and then you would just only
00:07:48.321 --> 00:07:49.408 copy the publish 1.
00:07:51.658 --> 00:07:54.994 I think that would be awesome if we can get when JL gets here
00:07:54.994 --> 00:07:58.060 because I looked at the publisher cause I thought that's
00:07:58.060 --> 00:08:01.288 what the published script did that all the published script
00:08:01.288 --> 00:08:04.408 does is just create a folder and put everything in there.
00:08:06.138 --> 00:08:09.253 Then then the odd thing that I would want with the public
00:08:09.253 --> 00:08:12.368 script is a way to set it to do self contained publishes.
00:08:12.758 --> 00:08:16.044 I don't know what like I've updated to the latest .net on my
00:08:16.044 --> 00:08:16.528 computer.
00:08:16.858 --> 00:08:18.588 I've installed the latest .net.
00:08:18.598 --> 00:08:20.388 Unlike client machines and whatnot.
00:08:20.658 --> 00:08:24.813 And then I'll go to run connect and it will say it can't find
00:08:24.813 --> 00:08:25.148 .net.
00:08:25.798 --> 00:08:28.524 So I've just gotten so much in the habit of using self
00:08:28.524 --> 00:08:30.258 contained publishes at this point.
00:08:30.878 --> 00:08:31.278 Weird.
00:08:33.428 --> 00:08:37.428 Alright, now I'm gonna kill that.00:00:03.203 --> 00:00:04.973 Good morning, Vietnam.
00:00:08.473 --> 00:00:09.393 Clear now I guess.
00:00:12.103 --> 00:00:12.883 OK so.
00:00:15.813 --> 00:00:20.823 This check loops make sure I'm on the right commits 437.
00:00:20.903 --> 00:00:25.871 Umm OK, so I already have one commit on here that I have not
00:00:25.871 --> 00:00:27.663 actually brought over.
00:00:29.243 --> 00:00:32.532 So basically this is for the cases where you're developing on
00:00:32.532 --> 00:00:33.593 some remote machine.
00:00:34.003 --> 00:00:36.722 Obviously you can't just directly push back up in the
00:00:36.722 --> 00:00:39.843 Azure because you can't put your credentials on a client box.
00:00:41.663 --> 00:00:46.373 Uh, so two ways we can go about that first way is if you leave
00:00:46.373 --> 00:00:50.785 it uncommitted over there completely, you can you do a git
00:00:50.785 --> 00:00:55.345 diff dash P so this is git diff in patch format and redirect
00:00:55.345 --> 00:00:56.093 that into.
00:00:56.503 --> 00:00:59.543 You know, maybe like you wt that patch or some file name.
00:01:00.823 --> 00:01:04.187 So if you're looking inside you that patch, you'll see it's like
00:01:04.187 --> 00:01:07.396 a full patch of exactly what's supposed to change in order to
00:01:07.396 --> 00:01:10.243 get to the state that you have on committed right now.
00:01:12.013 --> 00:01:16.420 And then really I have to do is be bringing back over here and
00:01:16.420 --> 00:01:20.757 then you do get apply and then whatever they have patches had
00:01:20.757 --> 00:01:25.234 stupid simple now annoying thing there is that then you have to
00:01:25.234 --> 00:01:27.403 get the commits back over here.
00:01:27.413 --> 00:01:32.859 Otherwise, obviously this is no longer In Sync, So what you can
00:01:32.859 --> 00:01:36.603 do and so right now I have one commit here.
00:01:37.053 --> 00:01:44.513 If I've 3AF which is not over here in my local so I can do is.
00:01:48.243 --> 00:01:48.463 Oops.
00:01:51.173 --> 00:01:51.603 Shoot.
00:01:51.613 --> 00:01:52.463 Well, what was it called?
00:01:59.383 --> 00:02:00.563 Expand the command quick.
00:02:05.423 --> 00:02:06.123 Format power.
00:02:06.133 --> 00:02:06.543 That was it.
00:02:09.743 --> 00:02:13.148 So I can do git format patch, we select what we want to format
00:02:13.148 --> 00:02:16.390 against or rather like what the base is that we are getting
00:02:16.390 --> 00:02:17.093 commits from.
00:02:17.623 --> 00:02:20.287 So in this case that will be this one, because it's the last
00:02:20.287 --> 00:02:22.995 one that's shared between local and this thing, which in this
00:02:22.995 --> 00:02:25.223 case actually happens to also be origin developed.
00:02:25.233 --> 00:02:29.443 So we can just directly, uh caught.
00:02:30.913 --> 00:02:34.297 I just directly target that branch, but if it wasn't the
00:02:34.297 --> 00:02:37.859 same as what this thing already knows being tracked for the
00:02:37.859 --> 00:02:41.540 remote, we could also just give the commit hash directly, and
00:02:41.540 --> 00:02:45.399 then I prefer to do double Dutch 10 it out and just pipe it into
00:02:45.399 --> 00:02:45.933 clip.exe.
00:02:47.103 --> 00:02:52.233 If you were to not do this, then it will just create one file.
00:02:52.243 --> 00:02:55.461 I believe for every patch or sorry for every commit that has
00:02:55.461 --> 00:02:58.522 been made since then and just copy them all over and just
00:02:58.522 --> 00:02:59.313 apply them all.
00:03:00.483 --> 00:03:02.663 I just do the standard out method.
00:03:04.993 --> 00:03:07.448 Because that's much easier to transfer because now I can just
00:03:07.448 --> 00:03:09.903 go back over to your clipboard, request the remote clipboard.
00:03:09.913 --> 00:03:12.293 I have the patch and come over to my local.
00:03:14.153 --> 00:03:19.777 Now it's going to be get AM to apply it and now I can actually
00:03:19.777 --> 00:03:20.223 just.
00:03:20.233 --> 00:03:23.251 Since then my case, I have a program that can take from my
00:03:23.251 --> 00:03:25.963 clipboard and treat like a file and just type it in.
00:03:28.003 --> 00:03:33.100 Ohh tricky thing is the connector directories, so this
00:03:33.100 --> 00:03:36.343 can be a little tricky with those.
00:03:37.273 --> 00:03:42.493 However, what you can do OK if I can remember what it was.
00:03:46.893 --> 00:03:48.393 Is the Welshman ject?
00:03:49.763 --> 00:03:52.598 So what this will do is they'll set you in the special AM mode
00:03:52.598 --> 00:03:55.253 of Git, so you don't want to do anything else with the Git
00:03:55.253 --> 00:03:57.908 repository here until you've actually like finished all of
00:03:57.908 --> 00:03:58.133 this.
00:03:59.443 --> 00:04:03.740 Uh, but if we go look through the folder for any dot rejects
00:04:03.740 --> 00:04:07.826 or rage that that Reg files, basically these are the ones
00:04:07.826 --> 00:04:10.433 where patches did not apply cleanly.
00:04:11.483 --> 00:04:17.416 So now we can look at, uh, finance bentek our program docs
00:04:17.416 --> 00:04:20.533 as well as The Reg file for it.
00:04:23.493 --> 00:04:24.183 So we see.
00:04:24.253 --> 00:04:27.423 Here's like the patch it was trying to apply to it.
00:04:28.503 --> 00:04:31.391 So you can look here extensions configuration looks like we
00:04:31.391 --> 00:04:32.113 already had it.
00:04:32.123 --> 00:04:34.773 We can ignore that adjacent file.
00:04:34.783 --> 00:04:37.783 Actually I did this so we can just ignore that rest file.
00:04:39.353 --> 00:04:40.443 Just going to remove it.
00:04:45.143 --> 00:04:49.056 On the other ones now the the other issue is just because it
00:04:49.056 --> 00:04:52.713 was sight line in here is probably on a different commit
00:04:52.713 --> 00:04:55.023 than site line up in the other box.
00:04:55.393 --> 00:04:58.573 So we can probably just ignore that for the moment.
00:05:02.753 --> 00:05:04.043 And then get a MI. Think.
00:05:04.053 --> 00:05:06.083 Let's continue. Oops.
00:05:09.293 --> 00:05:10.913 Of course, we do want to.
00:05:13.463 --> 00:05:16.373 Well, I guess in this case nothing technically changed it.
00:05:17.573 --> 00:05:22.003 Oh, actually I missed one one second.
00:05:27.453 --> 00:05:28.473 See what changed?
00:05:28.483 --> 00:05:28.853 So we added.
00:05:30.133 --> 00:05:32.373 That's just make it look the same.
00:05:36.373 --> 00:05:42.193 And this stuff inside sync order woo to Infor.
00:05:46.483 --> 00:05:51.290 See, so we got rid of the if statement and obviously this is
00:05:51.290 --> 00:05:56.254 where it's a little Trixie to, like, work out what you need to
00:05:56.254 --> 00:06:01.218 change, but in the end at least it's an easy way to, you know,
00:06:01.218 --> 00:06:05.867 pull things back across and actually, uh, work on a remote
00:06:05.867 --> 00:06:10.674 machine when you absolutely have to and have no other choice
00:06:10.674 --> 00:06:12.723 because security policies.
00:06:16.173 --> 00:06:18.963 So I will spare you going through the rest of this.
00:06:22.513 --> 00:06:24.523 So that's basically it.
00:06:24.533 --> 00:06:28.643 And then obviously if you want to say, oh crap, I messed up.
00:06:29.373 --> 00:06:30.263 Give me out of here.
00:06:30.273 --> 00:06:32.113 Put things back to the way they were before I started.
00:06:32.513 --> 00:06:36.483 Just aboard it, I think it might still leave.
00:06:36.493 --> 00:06:38.353 Yeah, I'll still leave the rejected files, but.
00:06:40.383 --> 00:06:40.893 Yeah.
00:06:41.783 --> 00:06:43.663 So any questions there?
00:06:47.233 --> 00:06:48.613 Hopefully nobody ever has to use this.
00:06:50.203 --> 00:06:53.283 M like a debug mode or a administrator mode where
00:06:53.283 --> 00:06:57.103 anything you do can screw stuff up the the factory be able to
00:06:57.103 --> 00:07:00.615 rollback by just doing abort would tell me it's not like
00:07:00.615 --> 00:07:00.923 that.
00:07:02.853 --> 00:07:06.373 Umm E you should really be able to screw anything up.
00:07:07.263 --> 00:07:07.523 OK.
00:07:07.503 --> 00:07:12.374 Uh, and if you're so, if you're local is in exactly the same
00:07:12.374 --> 00:07:12.853 state.
00:07:13.063 --> 00:07:16.402 So actually what I probably should have done is like do a
00:07:16.402 --> 00:07:20.029 fresh clone to apply this into if it's in the exact same state
00:07:20.029 --> 00:07:23.426 that the other side expects the remote to have been in, it
00:07:23.426 --> 00:07:25.383 should just apply pretty cleanly.
00:07:26.203 --> 00:07:27.393 Uh, problem isn't here.
00:07:28.103 --> 00:07:32.139 Uh Intellisense does not always work on VS code in this thing
00:07:32.139 --> 00:07:35.979 for some reason, so I end up coming over here like sort of
00:07:35.979 --> 00:07:40.015 scratch panning out, actually using Mel because they actually
00:07:40.015 --> 00:07:42.423 let me have real access to Infor uh.
00:07:42.533 --> 00:07:43.973 And then I bring it back over there.
00:07:45.013 --> 00:07:45.273 Uh.
00:07:45.503 --> 00:07:47.183 Manually redo it at all again.
00:07:49.593 --> 00:07:54.516 Uh, so my working directory in here ends up a bit cluttered
00:07:54.516 --> 00:07:55.583 with changes.
00:07:57.333 --> 00:07:57.633 Right on.
00:07:57.683 --> 00:08:01.142 So yeah, if you can keep your local clean though, and then
00:08:01.142 --> 00:08:04.543 just apply that directly there, it should work just fine.
00:08:06.173 --> 00:08:08.323 Every time I wake up the 1st that I tried.
00:08:07.513 --> 00:08:08.443 Promise. I have.
00:08:09.593 --> 00:08:09.793 Yeah.
00:08:11.583 --> 00:08:14.083 That's very sad conscious sedation.
00:08:14.133 --> 00:08:15.073 Ohh, there's curl.
00:08:15.083 --> 00:08:19.256 Development goes like if you ever heard of emailing Linus a
00:08:19.256 --> 00:08:21.273 patch or something like that.
00:08:22.133 --> 00:08:23.153 This is what we're talking about.
00:08:23.953 --> 00:08:26.954 Your firm, your firm at the patch, and you send them and
00:08:26.954 --> 00:08:28.323 then he just applies them.
00:08:29.293 --> 00:08:31.653 And then check them out and then says no, your code sucks.
00:08:38.773 --> 00:08:40.083 Kind of surprised he doesn't use.
00:08:40.093 --> 00:08:40.563 He wouldn't.
00:08:40.573 --> 00:08:42.671 They wouldn't use like GitHub or something where you could
00:08:42.671 --> 00:08:43.703 actually see the differences.
00:08:43.713 --> 00:08:45.533 A lot easier than through a notepad.
00:08:44.723 --> 00:08:45.003 Hmm.
00:08:45.933 --> 00:08:47.413 Yeah, it's.
00:08:47.463 --> 00:08:50.535 You're you're trying to ask why the the inventor of Git doesn't
00:08:50.535 --> 00:08:51.063 use GitHub.