Not only do you explain things very well, you are also a fluent speaker who doesn’t rely on disfluencies (i.e. - “um”, “uh”, “like” and “ya know”). Very pleasant to listen to. Keep up the good work!
Thank you very much! Part of my warmup before creating a video is to take a few deep breaths and speak out loud: "no ums, no ahs, make no assumptions about the person watching the video". It is sort of like a little meditation
I went through both videos and took tons of notes/screenshots. I have learned a ton, I appreciate the work you put in to this and the clear explanations.
These two videos were extremely useful to me in learning the Git and GitHub functionality in Visual Studio. I am really looking forward to the upcoming video mentioned here covering GitHub Collaboration Workflow.
Thank you Bill for these two videos, very valuable. Really needed to learn how to work with Git / GH from VS and these two covered all the important bits without a doubt. That being said still deciding to keep with Git Bash CLI, but this is a must to know as a .NET Dev.
It really comes down to what you are trying to do. If you follow a basic pattern of branch->commit->merge, then the Visual Studio 2019 interface should be just fine. If your workflow gets more complex than that, then the command line might be a better fit. I like the idea of doing everything from the UI to reduce context switching
Wow! That is high praise! Thank you so much! Also, please feel free to share that with your friends, family, and anyone you randomly speak with. Make sure they like and subscribe :-)
@@bill-raymond Haha Brilliant, I can't wait! Are you going to be covering the collaborating and updating origin from upstream? it's been driving me crazy trying to get it to work! xD
I think so but maybe you can describe the scenario you are trying to address just so I’m sure. There’s a little time to slip in something extra so let me know the use case
@@bill-raymond Whenever I add / amend code (in a scenario where I have a forked repo from someone else's repo), I commit it, then push it, then create a pull request - all good up to here, the original author merges the code into their main, then the problem occurs, no matter what I do, how I do it, any future contributions I make, when I do the same thing again, it always tries to push both the new commit and the previous commit. I can get the upstream to update (fetch and it gets the updated code with my newly merged contribution) and I can merge with my local repo, but when I make another commit and push it, it also pushes my original commit along with the new commit =/
Thank u very much, the best video and well explained, i am looking forward to see next video which will covers more bash(remote,fetching,pulling,pushing) ,how to write in bash as same time work with visual studio(modify and change codes) AWESOME video
@@bill-raymond My partner and I were working on a Xamarin Forms app. We both stayed in the same branch and it worked okay, but if we both made changes in the same file, it was a mess. Love to see the correct way for a team to collaborate.
I am not getting “merge branch” and checkout options in the “manage branches” window. Please let me know if I am missing smthng. Thanks. Instead I am getting option like “cherry pick”. Can you explain what it is.
I think the problem is you need to switch to the branch you want to merge too. For example, let's say you create a new branch and call it "new-feature". You modify a file (or files) and commit those changes. Now, you want to merge those changes back to the main (or master) branch. You go to the Git menu and select Manages Branches (which is where I think you are right now -- or at least were at when you asked the question) First, you go to the branch you want to merge into. In this case, double-click the main (or master) branch. Alternatively, you can right-click and choose checkout. The main (or master) branch will now be bold. With the main branch still in bold, right-click the branch you want to merge into it. In this case, I would right-click on the branch called "new-feature". Select the menu option that says something like "Merge 'new-feature' into 'main'". I think you did not see that because you either right-clicked on the wrong branch or did not first select the branch you wanted to merge into. Please let me know if that helps or if there is still an issue.
I got a question, when I made a repository, and clone it to VS. So like it shows me something which is "Select a startup item" but I don't see something like that. Thanks
Me too! Thank you! I had a serious problem with the recording then some work got in my way, but plan to really sit down and hopefully for real complete it next week :-)
In visual studio, when I click on the main branch on the bottom right, a window pops up that just shows a list of the branches and a search bar that says "type here to filter the list". There are no settings for adding, switching branches...
I wonder if this has to do with your having a lot of branches, so MS changes the interface a little bit? I have not experienced this, so am not too sure how to respond. Do you have a public repo I can fork and take a look at? If so, please share the link.
@maStaOverPowered, first let me preface this response with what you will hear a lot: Don't do it, because you are creating a monolith and every project should have its own repo, or use orphaned repos for each project. The work I do is pretty small, so I cannot explain that in more detail. All that aside, to answer your question, it does look like you can! I just created a solution and put two projects into it and then added the code to Git. It put all the files into source control and successfully published to GitHub. I do not know what might happen if each project is not under the same solution folder though (I doubt that works). Hope this helps!
There are many ways. The way you will likely use it is to compare one specific against another specific file. To do that, go to the Solution Explorer, right-click the file, select Git, then select View History. From there, you can select one file, then another using the CTRL key on your keyboard. Right-click on the two selections and select the Compare option. This will take some playing with. Please let me know if that answers your question
@@bill-raymond Thanks for the quick and detailed answer! I already use this technic, but I don't now how to do it with completely different branches which have the same file.
Unfortunately, I do not think VS 2019 offers a solid way to do this. I just checked a few diff tools, but they all seem to like working with files that are in the file explorer window, which means that is not helpful. You might need to do this in command line. Check out this link (which I have not tried, but looks like what you want): intellipaat.com/community/3494/how-to-compare-files-from-two-different-branches-git-diff-file-between-branches
![[Part 1] ทารกน้อยถูกทิ้ง👶 หญิงชราเก็บขวดขายเลี้ยงดูเขาจนโต #โลกการละคร](http://i.ytimg.com/vi/nPTDvFCExks/mqdefault.jpg)
Not only do you explain things very well, you are also a fluent speaker who doesn’t rely on disfluencies (i.e. - “um”, “uh”, “like” and “ya know”). Very pleasant to listen to. Keep up the good work!
Thank you very much! Part of my warmup before creating a video is to take a few deep breaths and speak out loud: "no ums, no ahs, make no assumptions about the person watching the video". It is sort of like a little meditation
très bonne explication, un grand merci à vous Bill 😊❤
You are very welcome and thank you!
wow, this is pure gold! thanks a lot ! and thanks again for the subtitles!
Thank you and you are very welcome!
Thank You lot, very simple explanation. kids also easily understand your teaching
Wonderful, thank you! May I ask what students are using the content and if there are any gaps?
Thank you, Bill! Great explanation, very calm voice. It is a very comfortable atmosphere to listen and learn something new.
Thank you, I really appreciate that!
Once again - just brilliant!
Keep up the interesting work.
Thanks!
Great! Thank you!
Honestly this is great video with clear explanation, thanks a lot Bill
You are very welcome! Glad you liked the video!
I went through both videos and took tons of notes/screenshots. I have learned a ton, I appreciate the work you put in to this and the clear explanations.
Thank you very much! I am glad you learned from the videos!
Greetings from brazil you are awsome, your teaching is amazing
Greetings from San Francisco, and thank you very much for the nice comment!
@@bill-raymond 👏👏👏
Excellent quality video that described exactly what I was looking for. Subscribed. Thank you Bill !
Wonderful! Thank you so much!
Thank you Bill, one of the best video available on internet today. I appreciate your hard work and presentation. Will wait for more videos.
Thank you! I am glad you found the video useful!
Excellent video, the basics of setting up and using GitHub in VS, good simple examples, superb! Very clear style of presentation! Thanks man!
Thank you very much! I’m glad you found the video useful!
These two videos were extremely useful to me in learning the Git and GitHub functionality in Visual Studio. I am really looking forward to the upcoming video mentioned here covering GitHub Collaboration Workflow.
Great, thank you! I am hoping to wrap it up this week
you are the best, man!
Thank you! I really appreciate the comment and hope you are doing well learning how to use Git in VS!
Thank you Bill for these two videos, very valuable. Really needed to learn how to work with Git / GH from VS and these two covered all the important bits without a doubt.
That being said still deciding to keep with Git Bash CLI, but this is a must to know as a .NET Dev.
It really comes down to what you are trying to do. If you follow a basic pattern of branch->commit->merge, then the Visual Studio 2019 interface should be just fine. If your workflow gets more complex than that, then the command line might be a better fit. I like the idea of doing everything from the UI to reduce context switching
Thanks Bill, this is just what I've been looking for to get me really working well with Git in Visual Studio.
Great news! Glad helped you!
This is the best new GitHub user experience basics tutorial in the entire internet! Thank you very much Bill :))
Wow! That is high praise! Thank you so much! Also, please feel free to share that with your friends, family, and anyone you randomly speak with. Make sure they like and subscribe :-)
@@bill-raymond No doubt the tutorial is very good but how can you enforce anyone to like and subscribe?
@@aamirpare I only ask that you like and subscribe. I cannot enforce anything. It is just a request
Thanks for the explanation. Great to get one started with VS and GitHub.
Thank you and I am glad it was helpful to you!
omagd! the best tutorial in youtube
Well thank you! My first omagd too!
Good work Bill.. nice video
Thank you very much!
Another fantastic video, nearly fell off my chair when I saw that Hipster Bill Raymond dude!! He has a killer moustache! xD
Thanks! He’s making a return next week!
@@bill-raymond Haha Brilliant, I can't wait! Are you going to be covering the collaborating and updating origin from upstream? it's been driving me crazy trying to get it to work! xD
I think so but maybe you can describe the scenario you are trying to address just so I’m sure. There’s a little time to slip in something extra so let me know the use case
@@bill-raymond Whenever I add / amend code (in a scenario where I have a forked repo from someone else's repo), I commit it, then push it, then create a pull request - all good up to here, the original author merges the code into their main, then the problem occurs, no matter what I do, how I do it, any future contributions I make, when I do the same thing again, it always tries to push both the new commit and the previous commit.
I can get the upstream to update (fetch and it gets the updated code with my newly merged contribution) and I can merge with my local repo, but when I make another commit and push it, it also pushes my original commit along with the new commit =/
Thank u very much, the best video and well explained, i am looking forward to see next video which will covers more bash(remote,fetching,pulling,pushing) ,how to write in bash as same time work with visual studio(modify and change codes)
AWESOME video
Thanks!
Really a very nice video tutorial that I found on internet.
Thanks for the great comment and glad it helped you!
Very helpful. Thank you
You are very welcome, and I am happy it was helpful to you!
Great explanation! Thank you very much!
You are very welcome and thank you for the nice comment!
Plain and simple. Thanks
I'll assume plain and simple means it was helpful and will take that :-). Thanks!
@@bill-raymond exactly :)
@@itasco24 cool thanks!
Great explanation !!!
Thank you very much!
Amazing, thanks for the detailed explanation
Thank you!
Great video. Thanks.
You are very welcome!
thank you so much i learned a lot
You are very welcome and I am glad you learned from the video!
nice video man you are the best, next time please talk higher because I barley hear you. THanks! I will see if what you say actually work.....
Thanks for the feedback. I’ll increase the volume in the future
very good tutorial
Thank you very much!
Very good.
Thank you!
Great videos, but I really need the collaboration video. When will it be uploaded?
Thank you! And I'm working on it. I promise soon! So sorry. So many things got in the way, and I had run into some bugs I reported to Microsoft.
@@bill-raymond My partner and I were working on a Xamarin Forms app. We both stayed in the same branch and it worked okay, but if we both made changes in the same file, it was a mess. Love to see the correct way for a team to collaborate.
Many Thanks, Bill
You are very welcome!
Thanks!
Thank you, James!
I am not getting “merge branch” and checkout options in the “manage branches” window. Please let me know if I am missing smthng. Thanks. Instead I am getting option like “cherry pick”. Can you explain what it is.
I think the problem is you need to switch to the branch you want to merge too.
For example, let's say you create a new branch and call it "new-feature". You modify a file (or files) and commit those changes.
Now, you want to merge those changes back to the main (or master) branch. You go to the Git menu and select Manages Branches (which is where I think you are right now -- or at least were at when you asked the question)
First, you go to the branch you want to merge into. In this case, double-click the main (or master) branch. Alternatively, you can right-click and choose checkout. The main (or master) branch will now be bold.
With the main branch still in bold, right-click the branch you want to merge into it. In this case, I would right-click on the branch called "new-feature". Select the menu option that says something like "Merge 'new-feature' into 'main'".
I think you did not see that because you either right-clicked on the wrong branch or did not first select the branch you wanted to merge into.
Please let me know if that helps or if there is still an issue.
@@bill-raymond this is really helpful. I tried the steps and it worked.
Appreciate you taking time to write the explanation.
Can you please share link to your video / make a video with explanation on “cherry pick”?
I got a question, when I made a repository, and clone it to VS. So like it shows me something which is "Select a startup item" but I don't see something like that. Thanks
Yeah VS sort of assumes you already have supported code in the project. Personally I prefer to create the project in VS and then push to GitHub.
looking forward for new video on fork
Me too! Thank you! I had a serious problem with the recording then some work got in my way, but plan to really sit down and hopefully for real complete it next week :-)
In visual studio, when I click on the main branch on the bottom right, a window pops up that just shows a list of the branches and a search bar that says "type here to filter the list". There are no settings for adding, switching branches...
I wonder if this has to do with your having a lot of branches, so MS changes the interface a little bit? I have not experienced this, so am not too sure how to respond. Do you have a public repo I can fork and take a look at? If so, please share the link.
@@bill-raymond Never mind, the interface does allow adding and switching branches. I did just update VS to 16.10, so maybe they changed the look
Hello is it possible to push two project to one repository ?
@maStaOverPowered, first let me preface this response with what you will hear a lot: Don't do it, because you are creating a monolith and every project should have its own repo, or use orphaned repos for each project. The work I do is pretty small, so I cannot explain that in more detail. All that aside, to answer your question, it does look like you can! I just created a solution and put two projects into it and then added the code to Git. It put all the files into source control and successfully published to GitHub. I do not know what might happen if each project is not under the same solution folder though (I doubt that works). Hope this helps!
Cool, but how to compare code with other branch /commit?
There are many ways. The way you will likely use it is to compare one specific against another specific file. To do that, go to the Solution Explorer, right-click the file, select Git, then select View History. From there, you can select one file, then another using the CTRL key on your keyboard. Right-click on the two selections and select the Compare option. This will take some playing with. Please let me know if that answers your question
@@bill-raymond Thanks for the quick and detailed answer! I already use this technic, but I don't now how to do it with completely different branches which have the same file.
Unfortunately, I do not think VS 2019 offers a solid way to do this. I just checked a few diff tools, but they all seem to like working with files that are in the file explorer window, which means that is not helpful. You might need to do this in command line. Check out this link (which I have not tried, but looks like what you want): intellipaat.com/community/3494/how-to-compare-files-from-two-different-branches-git-diff-file-between-branches