Absolutely beautiful. What great knowledge and extraordinary patience to go step by step for things one is master at. Truly grateful to you for doing this great favor to the community.
Bill - fabulous tutorial. Went from thinking Git was going to be a pain in the arse to learn to "dang, I think I'll have a firm grip on Git within a few weeks." Thank you for your work.
You are very welcome! Yes, I thought learning Git would be a daunting task, but actaully it is quite natural and easy to use. I am glad this video helped you!
Thank you so much for giving such a wonderful tutorial lecture! I was listening, making notes, making screenshots for the key steps, and used 5 x more time in watching the video. It certainly well worth for my efforts to listen to your lecture like that. I have listened to a few other videos with similar content (one of them as a paid course). Your video is certainly the best. I don't get confused any more! I look forward to many more of your videos in the future!
Awesome tutorial! Our team was used to TFS as our source control and our IS department decided to move to Git. I still know a couple of our dev guys trying to get used to Git, and I'll make sure to share this video to them. Thank you very much, Bill!
@@bill-raymond I was also wondering if you already have a video on how to create code review requests, including whether if it's possible to review the branch without merging to main, or merging the branch to main is a requirement. BTW, I'm now subscribed to your channel. Thanks again!
I must say I hated git until I watched your video, thank you so much! Finally someone who explains things simply and clearly! *LIKED & SUBSCRIBED* Edit: Can you please explain how the pull function in git works? It doesnt seem to work for me
Hello Bill, I actually started using git and github because of your old tutorial video. Because of these new videos I can finally change my workflow. Waiting for next video about Github :) Thank you for your clean and minimalist explanations. Thumps up!
@@bill-raymond Thank you Bill :) Do you consider to demo the new git experience for small team of 2 person ? Syncing, pushing, pull request, merging, solving conflicts etc? It would be great :) Again thank you very much.
Yes that will be next to wrap up this series. However, you can check that out in my older video series that will work with visual studio even though the menus are slightly changed. ruclips.net/video/qlxnwgLdc5I/видео.html
@Minimal Coder The new video is out. Unfortunately, it took a lot of effort to do the basic GitHub activities, so next week's video will be the third in the series with team collaboration. Sorry I had to break it up, but the video was getting too large. Here's the video ruclips.net/video/7ossCy94YAo/видео.html
An excellent tutorial. Just found the new git system and wanted to learn to use it again. Easy/quick - took only 30 mins to learn the basics, now I can use git again in VS :). I also make tutorials, I am learning from you :).
Great news! I am glad it helped you get started again so quickly! Also, feel free to reach out any time regarding video creation. It is a topic I like to talk about!
@@bill-raymond Oh I get it. Better to have step by step detailed demonstration that can be accelerated than to have a shallow and ambiguous presentation.
Okay, i downloaded the git for windows and the extension and there is already no "Git" menu in my menu :D Edit: oh my god, i fixed it! Try to do the following: Extensions → Customize menu → Commands → select "Menu Bar" radio box → select "Menu Bar" from the dropdown list and then click the button "Reset All" below. So it seems that i completely deleted the "Git" menu before because i didn't need it. Well, now i need it and i hope it helps you!! Edit #2: What a great tutorial. i really appreciate that you shared this knowledge with us!
Ha! Well I certainly would not have figured that one out! Thank you for sharing your experience here so others can see it and thank you for the nice comment as well!
Hey I really appreciate it. I know the audio was a problem. It was due to loud noises in the background during my office move for the pandemic so the only fix was (a) re-record or (b) release with lower audio to remove the noise. I picked (b) because it took a few weeks to product. I am glad you found it useful and you should not expect that kind of quality in general from my videos
@@bill-raymond (c) create an updated video with more detailed usage of git from visual studio 2019. Specifically related to pull requests, branching, cherry picking, gitignore - your choice. 👍👍👍
@@subhrajyotimaji Always happy to take requests for new videos but unfortunately I’m not re-recording this video. However, have you looked at the rest of the playlist? I have the collaboration video that explains pull requests. ruclips.net/video/Wdc56jf3yxM/видео.html
This was really good thank you. I’ve come from TFS which I found really easy to use. I hated GIT when I started watching this video and now hate it a little bit less. A well earned like and subscriber.
Haha! Well, Git and GitHub may have taken the term "distributed" a little too far, but here we are :-). I'm happy you liked the video and found it useful though!
@@bill-raymond out of interest how long did it take you to get monetised? I’ve recently started a coding channel called “Saturday Night Coder”. Thanks 👍
@@spaceoddity54 No problem! Just pick a topic you are passionate about, create video titles you think people will search for (not titles you think are cool), and make sure your content is solid so people like, comment, and subscribe
Thank you for the kind words! Yes, the volume issue had to do with a move to a new location with a lot of echo so I reduced the volume too much. In the future, you will hear them much better. I appreciate your comment though!
You should have a .gitignore file in the root of your project (wherever you initiated Git). Create the file if it does not exist. Edit the .gitignore file and then add appsettings.json on a new line. If this is something you need to do regularly, consider setting it up globally from this link: docs.github.com/en/get-started/getting-started-with-git/ignoring-files#configuring-ignored-files-for-all-repositories-on-your-computer Note that the global setting will only be for the computer you are working on at the time, so I do not like using that option very often. If appsettings.json is important to remove from Git history, check out the following article to remove it from cached commits (I have not done this, but it looks right): stackoverflow.com/questions/1274057/how-can-i-make-git-forget-about-a-file-that-was-tracked-but-is-now-in-gitign
Thank you for the feedback. I’m still trying to get the audio quality right. I think my future videos will be better. Sorry about that. It all has to do with working in a new space that echoes and I’m trying to reduce that.
Can you add a new video that applies specifically to Visual Studio 2022 (Professional) ? Microsoft moved to a Git menu under VS 2022. It works a bit differently.
This is one fantastic summary of working the interface with git in Visual Studio! By the end I had no confusions or questions left unanswered, and I feel I can now work with it and fully grasp its usefulness! All that's left for me to find is an extension that could show a more visualized version of the git history in vs, much like "git graph" does in vscode. Just having a list of the branches ordered alphabetically with seemingly no clear direction of when a branch was created or merged seems lacking in my eyes(reading and parsing the branch history could very well come with plenty more experience, I'm sure). Is it something I'll have to cope with or do you have any tips to share in that regard? Thanks again!
I'm glad this was useful to you! Yes, whatever Microsoft ships will likely always be generic and then allow for extensions. I have played with VS 2022, but have not seen anything that much different from 2019.
Thank you for the feedback. I understand the issue. It took me weeks to do this video because of a bug in the recording software. I’ll see if there’s anything RUclips can do to help me with this, but revisiting this particular video would be pretty triggering :)
Super video - thank you very much! I've never had a proper handle on this topic, so have done all mods on the master branch due to problems encountered merging other branches in the past. Now feel confident to use Git properly! 30 minutes well-invested. Why is there confusion over the master / main thing? All my repos say "master", so am I going to hit trouble if I don't change to "main"? Is there a technical reason that's going to bite me if I don't change it?
Thanks for the nice review! At the time I created this video, GitHub had not formally completed the shift from master to main but now there aren’t any issues. Most people now use GitHub’s default of “main” or they use “trunk” since everyone uses tree words like “branches”
@@bill-raymond thank you, Bill. I really enjoyed the video - you're an excellent communicator! As long as Master / main / trunk are all equivalent and not going to blow up in my face, I guess it really doesn't matter - just a style thing. Probably a reminder for me to work on some newer projects using the latest terms!
Bill, I have a Solution that started out as one project which is under source control (Git) I have added more projects but cant see to figure out how to get them under source control even though they are in the same solution. Is this possible?
Hi Bryan, the way Visual Studio creates projects, with the solution file [usually] being at a top-level folder with projects going underneath it means that you can end up in a solution where one project is under source control when others are not, so I understand the situation you are in. One option is to add source control to each project, so they are truly unique projects on your local computer. Depending on how large your solution/project is, that might be a good idea. However, it sounds like you want to have one single git repo for the entire solution (and sub-projects). I have not put much thought into this particular concept, but here is what I would do personally (and not being the expert): 1. Create a brand new solution and put it under Git source control 2. Copy the project folders into the solution folder. Visual Studio (and Git) should see the new files, which you can then commit into the overall solution. Note: Do *not* copy over hidden files because that could bring over the .git file(s) over from the old solution to the new one 3. Re-configure the solution and project files so they are all linked up, have the build settings you want, etc. I bet if you go to StackOverflow and ask if/how you can move Git from one folder to another, add the solution file(s) and add sub-folders, but honestly, my approach feels clean and less messy :-)
What if I want only to create a GitHub repository for a single folder within the solution? I have a solution with hundreds of folders containing files in each of them, and I want each folder to have its own repository without the need to open it separately and relaunch Visual Studio each time. So I want everything to be listed in the same solution, yet each folder has its own repository. How can I achieve that?
This is an ongoing question and debate amongst developers. Some will tell you to separate your code out to multiple repos because that will force you to keep each element of your code easy to maintain and help you avoid turning your app into something “monolithic”. However, jumping from repo to repo, especially when your code is new or you are the independent and primary maintainer, that could feel a bit like you are overdoing it and could be harder to code. I do not have a complete answer for you on this, but I will point you to this excellent article about Monorepos, which I think is closer to what you are looking for: semaphoreci.com/blog/what-is-monorepo the one thing I suggest is if things start to feel too difficult and you begin hating git and GitHub because you don’t like how it works, then you should seriously consider (a) trying it the git way and you will probably love it at first but go through the pain of refactoring code or (b) finding a different source control system that works best for you. I went down the (a) path because I was constantly fighting with git because I liked my old workflow, but now I know my old workflow was flawed and caused too much context switching. I hope this helps!
Question here. You created a repository for the project. What about if you create another project in the same solution? Will it be under the control of Git too? Or you must create another repository for the new project?
Yes, no, and a caveat. Yes if the project is contained under the root of the solution folder. No if the project is outside the root folder of the solution. The caveat is you probably want every project to be in their own root folder with their own git repo. If you do not do that, then you are probably creating what the kids term a "monolith" and that is a bad thing. You should create each project so it can stand alone, but also reference code from the other projects where dependencies matter. As you can see, it can turn into a bigger conversation :-)
Is the Git for Windows from Individual Component is the same as the standalone Git from their official website? Does it also have Git Bash or all it has is the Git functionalities inside Visual Studio?
Visual Studio uses standard Git, so it’s not a variant of Git. You can 100% use the command line or Bash assume you have the Linux subsystem enabled in Windows. However, Visual Studio does not do everything you can do on the command line. If your basic usage is to commit, push, pull, send pull requests and review PRs then it’s super useful. If you have a more advanced workflow, then the command line would be best
When I try to merge a branch 'branch1' into main (while main is selected/checked out), the merge option is available, but reads " merge 'branch1' into 'branch1' ". Anyone know why this might be happening? *edit* I've found a workaround. (Restarting visual studio, or perhaps just closing and re-opening the solution through the 'File > ' menu). I suspect that this is a bug either in Visual Studio or in one of the extensions I'm using.
To the best of my knowledge, you cannot do this using the Visual Studio UI, so you will have to use the command line. Install Git and use Cherry Pick. here's a good example: stackoverflow.com/questions/881092/how-to-merge-a-specific-commit-in-git/881112
Great work! One question, in my solution I have multiple project, should I create one repo for each project please? Thanks again for your wonderful job done!
You have asked a question that is hotly debated, so I will first answer the question that I think you want the answer to. If all your projects are under the same folder structure as your solution and you have the solution open with all projects, then they will all go under source control. So that is the easy answer. The real challenge now is to ask yourself what you should really be doing. Most people will tell you that you are building a “monolith” application by doing it that way. They will also tell you that each project should have its own unique root folder and be in its own git repo with a corresponding GitHub repo. I believe that the second path (multiple repos) is the right thing to do. However, if it is just you and maybe a few collaborators and the solution is not that big I would question why bother? Also, Visual Studio does not make it easy for you to manage multiple repos nicely when using a solution, so you may find it necessary to re-think how you design and structure your project. Hope that helps!
Hmm.. I would need more information, but here is how I would start trying to figure it out. First, make sure the file(s) you are editing are under source control and there is a Git repo, then make sure you save the file(s). I know that might seem like a lame response, but forgetting to save a file is my #1 reason for getting frustrated as to why the commit buttons are not available :-)
Do you have any recommendations for configuring visual studio 2019 mac? I'm new to both GitHub and visual studio and having a hard time following along with the tutorial since the windows version is just different enough. Thank you!
What if I make a change in The feature branch in startup file and switch to main without committing will that change also will be visible in both branches ? I am confused because earlier if I used to make any changes in a branch and switch to other vs used to ask me to either commit that or to stash that But today I saw something strange I made a change in a feature branch and coz I have some work in develop branch I just checked out to develop branch without committing my feature branch changes and when I was on develop branch I saw all my changes which I made feature was as it is in develop branch's file too 🥺 Can you please help on this ?
Okay that is a very good question and it seems weird to make a change and switch to another branch and the changes seem to appear there. What happened, right? Let's use your example. You are in the feature branch and make a change. At this point, that change is Pending (that is what VS 2019 calls it). Now, you switch to the main branch and it looks like that change carried over. In fact, the change is just following around with you because you did not commit it yet (well, technically it is unstaged, but I do not cover that in this video). So, the rule is, go to the feature branch and commit your change there. After you make that commit, the code will not carry over to another branch when you switch around. If that is something you do frequently but do not want to commit, you will have to look up "staging" files. I will ponder creating a video for it, but staging means you are letting GitHub know you want that change staged (not committed yet) in the branch you are working on.
It is coming! I promise! Please subscribe and click the bell for notifications. If all the stars align, it will be out next week, so you will get the notification. I hope the Git version was helpful.
@@bill-raymond Helped alot. All my books show the old Team tab version w/"publishing". Can you plz add something about undoing & starting over from a messed up Publish/upload of a project? Thx.
Bill, I hope you don't mind my comment. please remember that I am not trying to offend you. I appreciate you creating this video but I rather you mention the point of each instruction before you provide the instruction otherwise, I am looking at your steps thinking "what is he trying to do?"
Hi Jay. Thank you and that is really good feedback and something I am absolutely changing moving forward. In some cases, the videos will be broken up into smaller bites. In other cases, like this long-form video, I will introduce each concept first. No offense taken at all and all constructive feedback is very welcome! Thanks again!
@@lopsgamesstudio4113 That is odd because I have that. No worries though! Just create any random project. The point is to get into VS so you can modify settings
Have you upgraded and turned on all the features as I show in the beginning of the video? Miss one step and it might not work :). Also exit and restart VS as well
oh my god, i fixed it! Try to do the following: Extensions → Customize menu → Commands → select "Menu Bar" radio box → select "Menu Bar" from the dropdown list and then click the button "Reset All" below. So it seems that i completely deleted the "Git" menu before because i didn't need it. Well, now i need it and i hope it helps you!!
Yes I’m sorry about that. The problem was I recorded this during the peak of the pandemic and was switching up sound, location, equipment, and there was lots of noise so keeping it low was the only option (for me). I hope the video was helpful still
Unfortunately, I had to stop watching this. The volume is too low. I tried multiple devices and all had volume turned up to the highest leave. Further, when compared to the other videos, this video has low volume. Sorry, but it is what it is.
I appreciate your sharing this with me. Unfortunately, I created this video while still relocating my home office (because Covid), and the quality of the audio was really terrrible. I did my best so apologies for your experience and know that my other videos (aside from one other recorded during that time) are all very high quality audio now
Sorry it is too low for you. I did just play it at 50% volume and it came through pretty well for me. Was there a specific part of the video, or just the whole thing?
@@bill-raymond Thank you for the reply buddy. I indeed increased volume and watched this vid, and learnt a lot from it. The only issue was when every time it came ads, the ads volume was terribly high comparing to your voice. Once again thank you for the vid.
@saku okay thank you for this feedback! I’ve dealing with a new “COVID office” :). Getting the audio right without a tremendous amount of echo is something I’m still working on. Thanks so much for explaining the situation and I’m glad you were still able to make use of the video!
I have watched several videos about this topic and i can easily say this video was the best among them. Thank you.
That always makes me happy to hear! Thanks so much!
I was all confused about this Git with VS but then, I landed here. Amazing !!
Wonderful! Thank you for that!
Absolutely beautiful. What great knowledge and extraordinary patience to go step by step for things one is master at. Truly grateful to you for doing this great favor to the community.
That is very nice of you to say, thank you!
By far the most incredible visual studio git tutorial on RUclips. Thank you so much for this education.
Well thank you very much! I’m glad the series has helped you!
Bill - fabulous tutorial. Went from thinking Git was going to be a pain in the arse to learn to "dang, I think I'll have a firm grip on Git within a few weeks." Thank you for your work.
You are very welcome! Yes, I thought learning Git would be a daunting task, but actaully it is quite natural and easy to use. I am glad this video helped you!
The best video I've found so far explaining how to use Git with Visual Studio suite. Thank you for the easy to follow video!
Wonderful news and thank you!
Thank you so much for giving such a wonderful tutorial lecture! I was listening, making notes, making screenshots for the key steps, and used 5 x more time in watching the video. It certainly well worth for my efforts to listen to your lecture like that. I have listened to a few other videos with similar content (one of them as a paid course). Your video is certainly the best. I don't get confused any more! I look forward to many more of your videos in the future!
Thank you! That is great it helped you so much! It takes a few weeks to do these long form videos so I really appreciate this comment!
Awesome tutorial! Our team was used to TFS as our source control and our IS department decided to move to Git. I still know a couple of our dev guys trying to get used to Git, and I'll make sure to share this video to them. Thank you very much, Bill!
Great news! I designed this video series specifically for people that don’t have much experience (because I don’t) so glad it was helpful!
@@bill-raymond I was also wondering if you already have a video on how to create code review requests, including whether if it's possible to review the branch without merging to main, or merging the branch to main is a requirement. BTW, I'm now subscribed to your channel. Thanks again!
@@OldSchool614 Yes. Here you go: Learn collaboration with the new Visual Studio 2019 GitHub experience
ruclips.net/video/Wdc56jf3yxM/видео.html
Exactly what I needed to learn, and the pace and delivery of information was perfect. Thank you!
Great! Thank you for the nice comment!
This is exactly the comment I'd post today, but instead I'll just thumbs up. Thank you very much for this video!
I must say I hated git until I watched your video, thank you so much! Finally someone who explains things simply and clearly! *LIKED & SUBSCRIBED*
Edit: Can you please explain how the pull function in git works? It doesnt seem to work for me
Great news! Thank you! I hated Git for some time because no one could explain it to me so I’m glad this helped you too!
You are a great teacher for we the beginners.Thank you Sir
Thank you very much! I especially like a nice comment like this on a Friday :)
I am using your teaching videos for an entry level person. Its super easy for them to understand.
Wonderful, thank you!
Very well explained and beginner friendly. I'm shocked to see less subs. Thank you!
Thank you very much! Yes, I would like more subs too :-)
thank you very much it,s really simple and easy to understand. May you ,your family and your upcoming generations live longer and happily.
What a nice comment, thank you! I am very glad these videos are useful to you!
Hello Bill, I actually started using git and github because of your old tutorial video. Because of these new videos I can finally change my workflow.
Waiting for next video about Github :) Thank you for your clean and minimalist explanations. Thumps up!
Thank you very much! The GitHub version should be out next week. I’m diligently working on it, I promise!
@@bill-raymond Thank you Bill :) Do you consider to demo the new git experience for small team of 2 person ? Syncing, pushing, pull request, merging, solving conflicts etc? It would be great :) Again thank you very much.
Yes that will be next to wrap up this series. However, you can check that out in my older video series that will work with visual studio even though the menus are slightly changed. ruclips.net/video/qlxnwgLdc5I/видео.html
@Minimal Coder The new video is out. Unfortunately, it took a lot of effort to do the basic GitHub activities, so next week's video will be the third in the series with team collaboration. Sorry I had to break it up, but the video was getting too large. Here's the video ruclips.net/video/7ossCy94YAo/видео.html
@@bill-raymond Thank you very much Bill, I will like and comment immediately! :))
Very up-to-date and very clear explanation. Thank you for sharing the knowledge
Thank you for the nice comment!
Brilliant, thank you very much. Exactly what I've been looking for.
Good to hear, thank you!
Great work Bill. That is one of best video tutorial i have found to understand and set up Git. Keep it up! 😊
Thank you very much!
An excellent tutorial. Just found the new git system and wanted to learn to use it again. Easy/quick - took only 30 mins to learn the basics, now I can use git again in VS :). I also make tutorials, I am learning from you :).
Great news! I am glad it helped you get started again so quickly! Also, feel free to reach out any time regarding video creation. It is a topic I like to talk about!
Thank goodness for Playback speed X2. I like this new look and workflow. Thanks for the overview.
I'm glad you liked it! FYI, I create most of my videos so people can follow along, so they are a little drawn out, but it is on purpose :-)
@@bill-raymond Oh I get it. Better to have step by step detailed demonstration that can be accelerated than to have a shallow and ambiguous presentation.
Okay, i downloaded the git for windows and the extension and there is already no "Git" menu in my menu :D
Edit: oh my god, i fixed it! Try to do the following: Extensions → Customize menu → Commands → select "Menu Bar" radio box → select "Menu Bar" from the dropdown list and then click the button "Reset All" below. So it seems that i completely deleted the "Git" menu before because i didn't need it. Well, now i need it and i hope it helps you!!
Edit #2: What a great tutorial. i really appreciate that you shared this knowledge with us!
Ha! Well I certainly would not have figured that one out! Thank you for sharing your experience here so others can see it and thank you for the nice comment as well!
I wish the audio be a bit better. Apart from that, it's brilliant and crystal clear.
Hey I really appreciate it. I know the audio was a problem. It was due to loud noises in the background during my office move for the pandemic so the only fix was (a) re-record or (b) release with lower audio to remove the noise. I picked (b) because it took a few weeks to product. I am glad you found it useful and you should not expect that kind of quality in general from my videos
@@bill-raymond (c) create an updated video with more detailed usage of git from visual studio 2019. Specifically related to pull requests, branching, cherry picking, gitignore - your choice. 👍👍👍
@@subhrajyotimaji Always happy to take requests for new videos but unfortunately I’m not re-recording this video. However, have you looked at the rest of the playlist? I have the collaboration video that explains pull requests. ruclips.net/video/Wdc56jf3yxM/видео.html
Brilliant, up-to-date and very clear explanation.
Thank you and I appreciate the comment!
It helped me to understand how to use git in visual studio. Thank you.
You are very welcome!
This was really good thank you. I’ve come from TFS which I found really easy to use. I hated GIT when I started watching this video and now hate it a little bit less. A well earned like and subscriber.
Haha! Well, Git and GitHub may have taken the term "distributed" a little too far, but here we are :-). I'm happy you liked the video and found it useful though!
@@bill-raymond out of interest how long did it take you to get monetised? I’ve recently started a coding channel called “Saturday Night Coder”. Thanks 👍
After I started publishing regularly, two months
@@bill-raymond wow that’s pretty incredible. Thanks
@@spaceoddity54 No problem! Just pick a topic you are passionate about, create video titles you think people will search for (not titles you think are cool), and make sure your content is solid so people like, comment, and subscribe
Fasntastic video, you deserve more views, next time please increase the volume, great job!
Thank you! I agree I deserve more views :) yeah the volume has been fixed for new videos. I appreciate the comment
Thanks Bill. Exactly what I was looking for.
You are very welcome!
just perfect, thank you for the explanation
Thank you very much and you are very welcome!
Great overview, it helped me a lot. Clear, concise and answered most all my questions. I just subscribed. See you again. Thank You
Great news! Thank you!
Thanks for this. Exactly what I was looking for.
You are very welcome!
Clear and perfect Video. Thanks a lot
You are very welcome!
Thank you, excellent step by step Git 101 course. thank your for sharing Mr.!
You are very welcome!
Very good explanation and high quality content. The volume of the video was very low. Other than that, it was perfect. Subscribed ;)
Thank you for the kind words! Yes, the volume issue had to do with a move to a new location with a lot of echo so I reduced the volume too much. In the future, you will hear them much better. I appreciate your comment though!
I hope you are a teacher! Very well explained...thx
Thank you very much!
This was really helpful. Thank you!
Thank you and I am really glad it was helpful. Thank you for the nice comment!
Very clear explanation and cover all my target points Thank you
Great! And thank you!
great video presentation. this has really helped me Thank you so much
Thank you and I am glad the video helped you!!
Very informative and superbly presented, thanks for this!
Great news! I am glad you found it useful!
Excellent work, Bill. Thanks!
You are very welcome, and thank you!
Thank You Bill.... Love ❤
You are very welcome!
excellent presentation!
Well thank you very much! I appreciate it!
Thank you so much for this wonderful session
You are very welcome!
Very useful video..Thank you so much.
You are very welcome!
Thanks Bill, your video is excellent and really helped.
Great news and you are very welcome!
Excellent work, Bill. Thanks!
Only fault was that the sound was a bit low.
Thank you very much! Yes I put a pause on recording until my new mic comes in next week due to the issues with the current one
Thank you very much for this video. He help me too.
Thank you and I’m glad you liked it!
Simple and clear
Thank you!
crystal clear. thanks
Great! Thank you!
Thank you very much! Very informative video!!
You are very welcome! I am glad you found the video informative!
Well explained Thank you Sir
Thank you!
The video is more than good
Well, thank you! I really appreciate that!
beautiful Explanation sir.
Thank you, I appreciate that!
Thanks for this Bill.
You are welcome!
Thanks for this tutorial . It helped me a lot :)
You are very welcome!
Really nice video .
Thank you!
Like. Subscibe. Wait new videos. This video is perfect for newcomers.
Great news and thank you!
Thank you so much this is an excellent tutorial
Thank you!!
Very useful video, marred by far too many adverts (7)!
Thank you! I actually have the videos down to a minimum. Sorry about that.
This video is awesome. Can you cover up how to maintain the releases in git.
I created the following video. Take a look and let me know if this is what you were looking for? ruclips.net/video/fsKSDh-jWDw/видео.html
Useful thanks!
Thank you very much and I’m glad you found it useful!
Very good video.
Thank you! I am glad you are finding them helpful.
1：15 looks like in the 2022 version, there is no uncategorized option. when I search the git only "Git for window" shows up.
Thank you for pointing this out. I wish Microsoft had a bit more consistency with these things
How do you untrack and ignore the appsettings.json file? This is probably one of the most important things because it contains sensitive info.
You should have a .gitignore file in the root of your project (wherever you initiated Git). Create the file if it does not exist. Edit the .gitignore file and then add appsettings.json on a new line. If this is something you need to do regularly, consider setting it up globally from this link: docs.github.com/en/get-started/getting-started-with-git/ignoring-files#configuring-ignored-files-for-all-repositories-on-your-computer
Note that the global setting will only be for the computer you are working on at the time, so I do not like using that option very often.
If appsettings.json is important to remove from Git history, check out the following article to remove it from cached commits (I have not done this, but it looks right):
stackoverflow.com/questions/1274057/how-can-i-make-git-forget-about-a-file-that-was-tracked-but-is-now-in-gitign
It looks like it's not a preview feature in Visual Studio 2022 Preview anymore.
Good news! They said it was out of preview when I made the video but still put it in the preview section :(
Video Volume is quite low..not able to hear clearly :(
Thank you for the feedback. I’m still trying to get the audio quality right. I think my future videos will be better. Sorry about that. It all has to do with working in a new space that echoes and I’m trying to reduce that.
Can you add a new video that applies specifically to Visual Studio 2022 (Professional) ? Microsoft moved to a Git menu under VS 2022. It works a bit differently.
Thank you for the request, but I’m no longer using Visual Studio. If I get back in there again, I would be happy to though!
You are brilliant. Please make content on Microservice API TDD.
now I subscribed your channel.
Thank you very much! There may be something about micro services, but that would be later in the year.
Thank you so much
You are very welcome!
Good video.
Thank you!
This is one fantastic summary of working the interface with git in Visual Studio! By the end I had no confusions or questions left unanswered, and I feel I can now work with it and fully grasp its usefulness!
All that's left for me to find is an extension that could show a more visualized version of the git history in vs, much like "git graph" does in vscode. Just having a list of the branches ordered alphabetically with seemingly no clear direction of when a branch was created or merged seems lacking in my eyes(reading and parsing the branch history could very well come with plenty more experience, I'm sure). Is it something I'll have to cope with or do you have any tips to share in that regard?
Thanks again!
I'm glad this was useful to you! Yes, whatever Microsoft ships will likely always be generic and then allow for extensions. I have played with VS 2022, but have not seen anything that much different from 2019.
Awesome 👍
Thank you!
This is a great video but I have to turn the volume all the way up to hear anything. If possible, can you please normalize it?
Thank you for the feedback. I understand the issue. It took me weeks to do this video because of a bug in the recording software. I’ll see if there’s anything RUclips can do to help me with this, but revisiting this particular video would be pretty triggering :)
Super video - thank you very much! I've never had a proper handle on this topic, so have done all mods on the master branch due to problems encountered merging other branches in the past. Now feel confident to use Git properly! 30 minutes well-invested.
Why is there confusion over the master / main thing? All my repos say "master", so am I going to hit trouble if I don't change to "main"? Is there a technical reason that's going to bite me if I don't change it?
Thanks for the nice review! At the time I created this video, GitHub had not formally completed the shift from master to main but now there aren’t any issues. Most people now use GitHub’s default of “main” or they use “trunk” since everyone uses tree words like “branches”
@@bill-raymond thank you, Bill. I really enjoyed the video - you're an excellent communicator!
As long as Master / main / trunk are all equivalent and not going to blow up in my face, I guess it really doesn't matter - just a style thing. Probably a reminder for me to work on some newer projects using the latest terms!
excellent
Thank you!
Danke!
You are very welcome and thank you very much!
gracias amigo
Con gusto
Bill, I have a Solution that started out as one project which is under source control (Git) I have added more projects but cant see to figure out how to get them under source control even though they are in the same solution. Is this possible?
Hi Bryan, the way Visual Studio creates projects, with the solution file [usually] being at a top-level folder with projects going underneath it means that you can end up in a solution where one project is under source control when others are not, so I understand the situation you are in. One option is to add source control to each project, so they are truly unique projects on your local computer. Depending on how large your solution/project is, that might be a good idea.
However, it sounds like you want to have one single git repo for the entire solution (and sub-projects). I have not put much thought into this particular concept, but here is what I would do personally (and not being the expert):
1. Create a brand new solution and put it under Git source control
2. Copy the project folders into the solution folder. Visual Studio (and Git) should see the new files, which you can then commit into the overall solution. Note: Do *not* copy over hidden files because that could bring over the .git file(s) over from the old solution to the new one
3. Re-configure the solution and project files so they are all linked up, have the build settings you want, etc.
I bet if you go to StackOverflow and ask if/how you can move Git from one folder to another, add the solution file(s) and add sub-folders, but honestly, my approach feels clean and less messy :-)
What if I want only to create a GitHub repository for a single folder within the solution? I have a solution with hundreds of folders containing files in each of them, and I want each folder to have its own repository without the need to open it separately and relaunch Visual Studio each time. So I want everything to be listed in the same solution, yet each folder has its own repository. How can I achieve that?
This is an ongoing question and debate amongst developers. Some will tell you to separate your code out to multiple repos because that will force you to keep each element of your code easy to maintain and help you avoid turning your app into something “monolithic”. However, jumping from repo to repo, especially when your code is new or you are the independent and primary maintainer, that could feel a bit like you are overdoing it and could be harder to code. I do not have a complete answer for you on this, but I will point you to this excellent article about Monorepos, which I think is closer to what you are looking for: semaphoreci.com/blog/what-is-monorepo the one thing I suggest is if things start to feel too difficult and you begin hating git and GitHub because you don’t like how it works, then you should seriously consider (a) trying it the git way and you will probably love it at first but go through the pain of refactoring code or (b) finding a different source control system that works best for you. I went down the (a) path because I was constantly fighting with git because I liked my old workflow, but now I know my old workflow was flawed and caused too much context switching. I hope this helps!
@@bill-raymond Appreciate it ❤️
Question here. You created a repository for the project. What about if you create another project in the same solution? Will it be under the control of Git too? Or you must create another repository for the new project?
Yes, no, and a caveat. Yes if the project is contained under the root of the solution folder. No if the project is outside the root folder of the solution. The caveat is you probably want every project to be in their own root folder with their own git repo. If you do not do that, then you are probably creating what the kids term a "monolith" and that is a bad thing. You should create each project so it can stand alone, but also reference code from the other projects where dependencies matter. As you can see, it can turn into a bigger conversation :-)
@@bill-raymond Thank you Bill, subscribed !
No problem and thank you!
Is the Git for Windows from Individual Component is the same as the standalone Git from their official website? Does it also have Git Bash or all it has is the Git functionalities inside Visual Studio?
Visual Studio uses standard Git, so it’s not a variant of Git. You can 100% use the command line or Bash assume you have the Linux subsystem enabled in Windows. However, Visual Studio does not do everything you can do on the command line. If your basic usage is to commit, push, pull, send pull requests and review PRs then it’s super useful. If you have a more advanced workflow, then the command line would be best
When I try to merge a branch 'branch1' into main (while main is selected/checked out), the merge option is available, but reads " merge 'branch1' into 'branch1' ". Anyone know why this might be happening?
*edit*
I've found a workaround. (Restarting visual studio, or perhaps just closing and re-opening the solution through the 'File > ' menu). I suspect that this is a bug either in Visual Studio or in one of the extensions I'm using.
Thank you for sharing that tip! I had not encountered the issue before, but nothing beats a good old fashioned reset :-)
how to merge only specific commits to main branch?
To the best of my knowledge, you cannot do this using the Visual Studio UI, so you will have to use the command line. Install Git and use Cherry Pick. here's a good example: stackoverflow.com/questions/881092/how-to-merge-a-specific-commit-in-git/881112
Great work! One question, in my solution I have multiple project, should I create one repo for each project please? Thanks again for your wonderful job done!
You have asked a question that is hotly debated, so I will first answer the question that I think you want the answer to. If all your projects are under the same folder structure as your solution and you have the solution open with all projects, then they will all go under source control. So that is the easy answer.
The real challenge now is to ask yourself what you should really be doing. Most people will tell you that you are building a “monolith” application by doing it that way. They will also tell you that each project should have its own unique root folder and be in its own git repo with a corresponding GitHub repo.
I believe that the second path (multiple repos) is the right thing to do. However, if it is just you and maybe a few collaborators and the solution is not that big I would question why bother? Also, Visual Studio does not make it easy for you to manage multiple repos nicely when using a solution, so you may find it necessary to re-think how you design and structure your project.
Hope that helps!
@@bill-raymond great thanks Bill, you are brilliant yet so humble. That helps a lot.
You are very welcome and good luck with your project!
i've use visual studio 2022 but button "Commit all" is disable. Why? Thank you
Hmm.. I would need more information, but here is how I would start trying to figure it out. First, make sure the file(s) you are editing are under source control and there is a Git repo, then make sure you save the file(s). I know that might seem like a lame response, but forgetting to save a file is my #1 reason for getting frustrated as to why the commit buttons are not available :-)
thanks bill! How to collaborate with team using local only ? Can you teach me how ?
Thank you! I don’t think local only will really be worth trying. You could use GitHub out GitLab private repos though
I have no "Github" in my "Other windows...". How come?
Please make sure you added the feature from the Tools menu and restart Visual Studio. Does that help?
Do you have any recommendations for configuring visual studio 2019 mac? I'm new to both GitHub and visual studio and having a hard time following along with the tutorial since the windows version is just different enough. Thank you!
I would recommend installing Visual Studio Code, then installing Git. You should be good to go! Most GitHub functionality is built in
What if I make a change in The feature branch in startup file and switch to main without committing will that change also will be visible in both branches ?
I am confused because earlier if I used to make any changes in a branch and switch to other vs used to ask me to either commit that or to stash that
But today I saw something strange
I made a change in a feature branch and coz I have some work in develop branch I just checked out to develop branch without committing my feature branch changes and when I was on develop branch I saw all my changes which I made feature was as it is in develop branch's file too 🥺
Can you please help on this ?
Okay that is a very good question and it seems weird to make a change and switch to another branch and the changes seem to appear there. What happened, right? Let's use your example. You are in the feature branch and make a change. At this point, that change is Pending (that is what VS 2019 calls it). Now, you switch to the main branch and it looks like that change carried over. In fact, the change is just following around with you because you did not commit it yet (well, technically it is unstaged, but I do not cover that in this video). So, the rule is, go to the feature branch and commit your change there. After you make that commit, the code will not carry over to another branch when you switch around. If that is something you do frequently but do not want to commit, you will have to look up "staging" files. I will ponder creating a video for it, but staging means you are letting GitHub know you want that change staged (not committed yet) in the branch you are working on.
Please do the GitHub repo version! Thanks =)
It is coming! I promise! Please subscribe and click the bell for notifications. If all the stars align, it will be out next week, so you will get the notification. I hope the Git version was helpful.
@@bill-raymond Helped alot. All my books show the old Team tab version w/"publishing".
Can you plz add something about undoing & starting over from a messed up Publish/upload of a project? Thx.
On GitHub? Yes I can do that. Great idea!
Bill, I hope you don't mind my comment. please remember that I am not trying to offend you. I appreciate you creating this video but I rather you mention the point of each instruction before you provide the instruction otherwise, I am looking at your steps thinking "what is he trying to do?"
Hi Jay. Thank you and that is really good feedback and something I am absolutely changing moving forward. In some cases, the videos will be broken up into smaller bites. In other cases, like this long-form video, I will introduce each concept first. No offense taken at all and all constructive feedback is very welcome! Thanks again!
the continue without code option isn't exists 😑😑
Could you provide the time in the video you are referring to?
@@bill-raymond 1:25
@@lopsgamesstudio4113 That is odd because I have that. No worries though! Just create any random project. The point is to get into VS so you can modify settings
@@bill-raymond thank you i did this and succeeded 😀😀
@@lopsgamesstudio4113 great!
I checked everything in preview features, I installed all git stuff, still I cant see git menu next to debug.
What version are you on?
Meaning, what version of visual studio?
@@bill-raymond 16.9.1, I just got it, problem solved. Thanks for the fast replay, and awesome video
You are very welcome and glad you are up and running!
git doesn't show up on my menu
Have you upgraded and turned on all the features as I show in the beginning of the video? Miss one step and it might not work :). Also exit and restart VS as well
oh my god, i fixed it! Try to do the following: Extensions → Customize menu → Commands → select "Menu Bar" radio box → select "Menu Bar" from the dropdown list and then click the button "Reset All" below.
So it seems that i completely deleted the "Git" menu before because i didn't need it. Well, now i need it and i hope it helps you!!
Volume is very low.
Yes I’m sorry about that. The problem was I recorded this during the peak of the pandemic and was switching up sound, location, equipment, and there was lots of noise so keeping it low was the only option (for me). I hope the video was helpful still
Unfortunately, I had to stop watching this. The volume is too low. I tried multiple devices and all had volume turned up to the highest leave. Further, when compared to the other videos, this video has low volume. Sorry, but it is what it is.
I appreciate your sharing this with me. Unfortunately, I created this video while still relocating my home office (because Covid), and the quality of the audio was really terrrible. I did my best so apologies for your experience and know that my other videos (aside from one other recorded during that time) are all very high quality audio now
Sound is too low.
Sorry it is too low for you. I did just play it at 50% volume and it came through pretty well for me. Was there a specific part of the video, or just the whole thing?
@@bill-raymond Thank you for the reply buddy. I indeed increased volume and watched this vid, and learnt a lot from it. The only issue was when every time it came ads, the ads volume was terribly high comparing to your voice. Once again thank you for the vid.
@saku okay thank you for this feedback! I’ve dealing with a new “COVID office” :). Getting the audio right without a tremendous amount of echo is something I’m still working on. Thanks so much for explaining the situation and I’m glad you were still able to make use of the video!
so bad
Hi there. Could you share what you did not like about the video?
Thank you so much
You are very welcome!