Azure DevOps and visual studio | Taurius Litvinavicius | Skillshare
Play Speed
  • 0.5x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 2x
3 Lessons (30m)
    • 1. Intro to Azure DevOps

    • 2. Access repository

    • 3. Publish to Azure DevOps (commit and sync)

  • --
  • Beginner level
  • Intermediate level
  • Advanced level
  • All levels
  • Beg/Int level
  • Int/Adv level

Community Generated

The level is determined by a majority opinion of students who have reviewed this class. The teacher's recommendation is shown until at least 5 student responses are collected.





About This Class

This class will introduce you to Azure DevOps and the use of it in the visual studio. Azure DevOps works the same way as GitHub, but it has a lot more features. 

Meet Your Teacher

Teacher Profile Image

Taurius Litvinavicius

Businessman, author and tech expert


I am a businessman with a wide range of software development skills, including .net core, MSSQL, c++ and other technologies. I have worked on the most straightforward and the most complicated projects, but no matter what the task is, the best way - is the straightforward way. Therefore, in my lectures, I will only cover the things that you will actually need.  My goal is to help bring technology and business together, because there is nothing better than an all-rounder in these areas.


See full profile

Class Ratings

Expectations Met?
  • Exceeded!
  • Yes
  • Somewhat
  • Not really
Reviews Archive

In October 2018, we updated our review system to improve the way we collect feedback. Below are the reviews written before that update.

Your creative journey starts here.

  • Unlimited access to every class
  • Supportive online creative community
  • Learn offline with Skillshare’s app

Why Join Skillshare?

Take award-winning Skillshare Original Classes

Each class has short lessons, hands-on projects

Your membership supports Skillshare teachers

Learn From Anywhere

Take classes on the go with the Skillshare app. Stream or download to watch on the plane, the subway, or wherever you learn best.



1. Intro to Azure DevOps: blow in this lecture, you'll get a quick introduction to the Azur devils Now. What is this? Asher Delap's basically in ASHA devils. You can create an organization. You can also create a project in the organization, and then the project will contain one on multiple repositories so wise is better than get well. First of all, the project does not contain just just be reports trees. It contains a lot more. You can actually create features you can create always backlogs and all that management stuff in a very nice way. It's a need and died way. It's not like get home. It's not a massive total fashion. It's very more than very bright, very contemporary, that you have all these features. Plus, you get these bills you get builds deployments, all that automation. If you, of course, want to use that and you also get the wicked. Now let's take a look at all that and let's first of all, creed a project, and also I just want to mention you should use the same account for the ASHA develops as you use for the visual studio. It will work a lot smoother that way because you do need to be connected to that particular organization with the same account. But you're on the visual studio. Let's create that project that's great with Project, and you click on that and you enter a name for the project. So let's say test project. That's Roger just like that, and you could also and Toby description. And then you have either private or public. In this case, I would do private. It doesn't really matter. It's all actually free. Well, the organization up to five people, everything is free. The that's probably one of the best parts of this, and we will look at some other great parts later. But for now, let's create that project, and if you go to advanced, you will see them interesting things. First of all, the version control you see was get and then you can see team foundation version control. Now we won't be getting into the team foundation version control. It's a totally different thing. It's a bit more advanced thing, and you actually have to learn how to use the BF B C. No chest. The visual studio that we will get started with get and you might ask yourself why is this ? Get version control. If this isn't get help, well, the answer is probably quite simple. Microsoft actually earns get hub. So in turn, since get herb reported story supposed, wide popular get hub or get reports. Injuries aren't used him and the actual repository is pretty much the same as the get home . You will see all that, but it is a lot easier to use it through the azure devils. And then you have work item process the we currently have actual oil. We could have basic we could have C m m I. We could have from the again. This is a totally different thing with the management thing. We would just go with actual really makes no difference for the reports that report Now that's great Click create. It's really create. And your new project is being created right now, though we have our test project and then you can invite people to the project joined the project and you have the private You can't change that. You can change your name and then you have the summary and then you have dashboards Dash, What a really nice feature. Really nice feature you can add to eat which it and say, If you want to know what work items are assigned to you simply adverse one assigned to me. If you want to have your build history, add this one and there are many of them are many of them the example? Co title displays a number of reasons. Changes in the code repository will have some sort of decent description. It's very easy to use, and once you get a hang of it, you won't be able to leave this Asher Della thing that we won't be adding any widgets. We'll just move on to the Wikki. Take a quick look at the wiki you can actually create Wicky, or you could publish codas wicked, but I don't like land. I prefer having a wicked the sort of separate entity. There's no need to make. It has a code now, Alice. Let's take a look at the wiki have that Project Wiki, and we have one page currently new page. We don't actually have it yet, so if you say just page and you click safe, you will have all that. Plus, you get a previous If you'll write some things, it does this test. Get the free. We like that. If you do bold, you get a pre off aboard. It works white. Well, actually, it works perfectly. I would say so. Then you have these boards and boards have work I terms or a different stuff and we leave also. This is a great feature. This is a great feature now. I did not save my wicked page and it actually noticed that. And it is stating now if I want to leave or not, it doesn't have all those nasty default rounds. The pop ups. It's beautifully made, soft custom, Pope of window. And as you can see, you can actually drag it. So it's a really beautiful platform, and I would definitely recommend to try it. And then we can leave. Actually, we can go. We went to the work items. You can create a new work items that you have a feature you click on feature and you can create a new feature. Now, you may think this is only useful for managers for people who are actually gonna have a team to work with. And you might think if I have only to your free people, I don't need that. But you should try it once in a while. It might be quite useful, especially for some more detailed systems. It might come in handy. So now we won't get into all these bills and pipelines and deployment groups and all that, Although it's quite useful, it can be quite useful. But it is quite difficult to work with. We won't get into that. It doesn't really matter. It doesn't concern with visual studio. What does Concern Visual Studio is? The reported Cherie part the reported three Ponte. As you can see by the photo, you get this one repository, you get this one repository. But what we will do, we will actually rate a project in visual studio that will be in the next lecture and we'll upload it. We'll create a reported tree format and we will actually upload it. Do this to this desk project. That's gonna be very interesting. And once that is done, we will get back to the azure, and we will take a look at these files and what we look like since we don't have anything yet, we can take a look at anything. And first of all, we need to actually create some code and publish it. Teoh this repository. And with that we will conclude this lecture 2. Access repository: Hello and with lecture will take a quick look at how to access a repository. Rome. A visual studio. So again we will be accessing our test report tree in the Asher Devils, and to access it, you simply go to clone or check out code. And here you will find Azure develops in the browse repository. You don't you need to look at thes, reportedly locations and local puffs. Just go to browse a repository. You click on the Asher Devils. If you had a good hubby, you would go to get up. Now let's go to you as your devils and let's see each launch. Now it can take a while. Sometimes. Burlison, we have I have my organization and I have all these projects, these projects and let's see, let's look for test project right here and we have a couple of projects. Now. We have won't slapped us and we have death project. So we had our consul amped A, says the rial project uploaded. Now, if you click on that, you'll notice the button connect. So since I have created with Project with Reports tree on this particular computer on with particular folder with this particular installation off a visual cereal. I can now simply connect. I don't need anything else. However, if you would reinstall the visual studio if you would change some things Ah, if you would move a few things around, you might need to clone it. You mind need to clone it that we would clone it. It would create that new local reports a tree in your selected half in your selected directory, and you would then later next time be able to connect. And also, if you do have bad, but she can't find the connect right away. You would simply again select this expansion and you van click on Connect and then you find the four border. So now let's simply connect. Let's see how that works is very simple again. It will launch in a second, and you will find your Rogic dried away, though here we have our project. And as you can see, it is opened as this reporter tree file rather off, not it file. Behold, directory before order or would you prefer. And so right now, the project, the solution rather is not initialized in the visual studio. What you need to do you need to simply double click on that solution. So you you access in this in this explorer, you basically access that repository folder and then you click your solution. You open it on this, your studio, just as you would do a non repository project from your folder. And now, if you can see, we have our two different projects. And that is basically how you open a project from Asher Devils in visual studio and event. We will conclude with lecture. 3. Publish to Azure DevOps (commit and sync): Hello and with lecture, we will try to publish the code to the reports Tree. Now, I already have a simple project Creative. I didn't do anything to it with a just with the four toe template for a dot net core consul application that you can see that the Ford Code has with little room line and it says Hello world though we have all the basics and we do have some code And also we do have a project and a solution. Now, remember, repositories we work on the solution we work on with solution. We don't work on a single project. We work on a solution and you will see how that works later. And to begin with once you created a project, when she wrote some code, you need to add it to source control. And as you can already see in the bottom left or rather right corner. You see this ad to source control. There you click on that and you only have one option. What is get we get way added to the git repository. As you can see, it was some consul things happening, but you don't need to write anything to pick on. So everything is done for you and you save lots and lots of time and effort and all that. So now we created our consul. AP won our little local reporter tree and we have off like a basic first publish. This is the first initial publish. You won't see that again and you can publish Forget Repo to the Asher develops. You can publish it to get home the same way the same way you would do that and you can publish it somewhere else. But we will be looking at the good old Asher develops in this case and what you can also see in the bottom. You can see this little arrow and then this little, probably a penitence. We will look at those later. But basically, if you get lost from this window, future or off, you're simply click on that arrow and you would get back to it. But again, this is just be initial one. I suggest the initial one and I can actually expand it. Make it bigger, get full screen you now Why not, though I'm going to click on publish get Repo in the published rash that develops and I have my account and all that, and I have my organization. That is the one I want to choose. If I wanted a different one, my master of organization, I would choose that. But I need my main one. So now you can create a simple reported tree. You can write my name, but what Matt will do it would actually create a new project with that reporter tree that it wouldn't go into your existing projects that would create a new project. I don't like that. It's not really efficient. If you use when a lot you get a mess off projects. You would get 50 projects in your Azur organization, and it will be a mess. So if you want to add a repository to your Parolin shipped, you simply go to advanced. You go to be advance if, like plant, and then you can choose the project, as you can see have project that I will expand that and I have algorithms using C sharp basics. And then I have all these different little projects and let's see, let's see which one I need. I need my test project, my text, this project and if I go to test project it has with people. The Fourth Report Century name which is says Project. But we want to create a different one. Why don't we create a different one? Let's say is gone. So app Best consul AP test that we create that little reponse a tree and then let's publish it. It's publish it just like that. It will take a few seconds, but it will be perfect Now again, You don't need any consul windows. You don't need any of that nonsense. And now everything is published, as you can see going so app Just waas pushed pushed is with technical term. Now let's turn that off for now. Let's see if I can turn it off. I can Yes. And now we have this whole thing and we have this program off course. But what we will do now is we will create another project in the same solution out. For some reason, I can't see my solution, explorer. And if you can't find one of these windows on the right, you go to the view. You go to the View tab on the top, many times have and then Ugo and try to choose from one of these. And if you can't find what you're looking for in one of these, you go to other windows and you look the one you want in half. Well, when he won in half and you might be able, Robbie should be able, you find it. We need the solution, Explorer we need a solution for and I did expand it. I will leave it for now, like that. It doesn't really matter what I need now. What I need now is to create another project. So I will right click on the solution and I will click on Add and I will go to new project just like that on. Then I will do. Let's say, Let's see and let's say let's do a on so or rather, a library. Let's do a little dot net core library. Why don't we? So this is a good search thing. You can have project type. You can have gone so desktop and all that have you would be. Let's see, we have library. We do have library and it shows all the libraries. Now we should be able to find that actually I see hair. But if you can't find you want to add another filter, go with the language. It's gonna be see shop, though I want to see shop and I want Don't match goal. I click on that. I go to next on before ER before the relocation is actually picked by the solution. It's the same way it's the same place where solution is. You could off course choosy, different place, but it really doesn't matter. In this case there. Let's click create, let's create and we will have it in the second album. Minimize that window now and I will try to attach it now again, If you want to attach it, you start dragging it and you see all these different things. And if you go on one of these, you see well, be window would end up then one. Matt, we don't want that. That's your big bats, your small and we want the usual place. Probably that's the usual place for it. And now that you have this whole solution with whole reported everything going, you can see these little red read Aikens, and then you can see with these blasts things and checked in Ah, locks and all that. So all that has to do with the reported tree. Now we did make a change. We did make a change. And the computer? The system, it has noticed it. So let's go now and commit with changes to be reported free. So first of all, you will commit the changes. The local reports the tree. Now we're way. I would like to explain. This is simply your first go hair on the pen and you commit everything. You kind of write down with changes into that local reports that tree and then you simply upload or rather, update be remote reports a tree. So think of it as two different reports of trees. One on your computer, one, the remote one. And then you send the data, you update that one. And if you have some conflict off the data, your soul, it's very simple. And here you need to have a commit message. Now I did detach with things, and now it's a bit of a mess. I'll try to puts us right hand, though we have a changes. So let's see. Ah, let's see. We have added a library. Now you could just make a mess of off some letters. You could just say minor changes something like that. But I would recommend adding jazz a very basic description on watch you are committing. So we have that and we will commit all. We won't get into any offers. Other teaches him. We will commit all I thought you need to really do and then, as you can see, have created locally and then you can stink. You can sing to share your changes with the server, though you can. I have a click hair or you can go to the bottom and click on the error arrow. And as you can see, it has 11 on pushed goal meant So that's one a NSYNC palm it if that language is a bit more simple that we have that and again on changes. If you make some changes to the code, you get pending changes for that. Ben, if you if you commit locally, if you create that commit locally, you will get this UNP pushed comment. Now I would recommend doing both at the same time arrive in in that same order you simply commit, and then you push it right away because the whole point off this push thing. It's actually keep it somewhere safe, not on your computer. Somewhere in one of those reports trees. Now let's click on Let's say, click on the sink, click on the sink with time. And as you can see, I have outgoing comments. I have outgoing calm. It's just like that, and I will click Bush and it will push hopefully successfully. And it did actually push very successfully. No. If you want Teoh, create a different branch for the bush, let's say you have masa. You want a new branch? If you want to do that, it's simply click on the new branch and you go through that process and you create it. It's very easy to do. We won't get into that. You can give it a shot. So now to get something they someone else see you work with for some other fella and you obviated the reports tree and someone updated it as well and say you want to get the data so if you would want to do that, you would simply click on a pull. You would click on Pull, and it won't actually be able to pull anything because we did not change anything. And as you can see it says Repository is already up to date. No changes to pull. If you had changes, you simply would pull them and it would be the same exact being as pushing them the again. It's very, very easy to do now let's just for a quick second. Get back, Get back to our now. Ah, As you develop site, we get back ham and we are still on the same test project. Now you could go. You could go to the files, have a repose of files and then you by the four to get to some random reported tree if you have several. So if you want to change that to go head to the top, you click on that. And as you can see, you have become so app, and if you have many reported recent, you can actually feel to them. So let's click on the consul app and we will get to the files we get to the files and we can actually very easily arouse them. See what we wrote. What we've done and what we committed This is the main program and all that you get all this code with no distractions on one useful thing here, you can actually fork it you can click on for, and basically this will copy the whole reports that tree and create a new repository again . It's the same thing as in get, huh? But this is very, very easy to do, and you can actually walk it to a different project. You can forget to a different project, which is actually quite amazing. And then you have only the default branch master, and you can have all branches as well there. Matt is again very, very useful now. We won't actually be forking it with no point in doing that. It's very easy to do just great. The name it Just get the like, your project and you choose between all in one branch. And let's cancel that the let's See you have also the Comets. If you go to the Comets, you will see that I have in fact committed a few things I have committed. We had the General Comet, then we had that library thing. They you can search should, as you can see simple history and all that, and let's see you can actually dio explore the source on Let's say, Let's say you have some specific file where some other person might have committed, not you, nor your friend with someone else, and you would see that way committed that the It's all very useful if you have more people working. Review. If you're working alone, is probably not gonna be that useful unless, of course, you make these good descriptions good messages, and you actually know what's happening to your code. And then you can see the bushes can see the bushes, and then you can see the branches. You can see the branches. You can compare the branches and dual that, and you can create tags. And then you can also have the pull requests that we don't have any pull requests. We won't see any yet. Now, as you can see for many choices, haver many things to do, and it's all very, very easy to use. And with that, we will conclude with a lecture