Visual Studio Team Services Tutorial:
This is a Microsoft Service that covers all the needs of the software development life cycle. Here in this post, we will see how the application development life cycle proceeds and what are the general requirements of a team or an individual developer.
There is a lot that goes into an application or game development. While developing apps and games, the development team has to manage with the source code, the team, testing, deployment and more. In this post, we are going to show how Visual Studio Team Services is going to solve a lot of those problems.
- Visual Studio Team Services Tutorial.
- Visual Studio Team Services for independent developers.
- A closer look at Visual Studio Team Services.
- Agile with Visual Studio Team Services.
- Work Items with Visual Studio Team Services.
- CLI for Visual Studio Team Services.
- Code Visualizer for Visual Studio Team Services.
- CI/CD for Visual Studio Team Services.
VSTS works for all kinds of developments. It works for a single person or it works for a team. There are projects like, Windows, Minecraft, Halo and more that are being built using Visual Studio Team Services.
Visual Studio Team Services is a cloud-hosted application development service. So, all the Dev-Ops capabilities that people associate with when it comes to a product like Visual Studio Team Services, is available in this product. We can say that planning a product involves choosing the kind of methodology first. If we go with the trend and choose the agile methodology, we have to next think about bugs and task along with the advanced classification like epics and features. This helps us to structure the labor so that they will take on the right task, bug, epic or feature.
Visual Studio Team Services for independent developers:
Visual Studio Team Services is also very useful for independent developers. The developer has to track the work done, the bugs reported by the users and the feature requested by the users and Visual Studio Team Services is very useful in managing all that comes in for the developer. Earlier the developer had to plan and manage everything on their own but with Visual Studio Team Services everything is done by the cloud and the developer has to focus only on how to solve a particular problem or implement a new feature.
Visual Studio Team Services also provides source control. Every team or an independent developer has to store the source somewhere safe and Visual Studio Team Services offers the right source control for that purpose. Many developers just use GitHub for their source control. And due to that visual studio team services tutorial is offering unlimited private GitHub repositories.
There is only one restriction on an unlimited private repository and that is the 5 user limit. If there are more than 5 people in the team, Visual Studio Team Services charge only for the additional members and only on a monthly basis. The GitHub repository is still free for everyone on the team.
Next to Git repositories Visual Studio Team Services offers the build services. Only Visual Studio Team Services offers all Windows, Mac, and Linux to build the source code in and test it. This lets the development team take advantage of the build service that is integrated into the Visual Studio Team Services and not use their own. This is available right next to Git. Therefore we can have the planning, source and the tests alongside each other. Build services also offer package management, it has package management for Nuget packages, Node packages and more. This helps the developers ensure that the build is started with all the necessary NuGet Packages added to the project.
The test platform supports the main Visual Studio projects along with open source and more.
Testing team can run the manual test, load test and run tests against the back end.
Visual Studio Team Services also supports deployment. The developers can choose CI/CD or just go with manual deployment and it is up to them.
Now that we have come across the different stages of the application development lifecycle, we can say that when an individual or development team is taking advantage of visual studio team services tutorial they do not have to use all the available features and they can choose what they want and remaining they can do on their own. This applies to the part of the deployment also.
Availability with different Cloud providers:
Visual Studio Team Services does not only apply to Microsoft Azure which Microsoft’s own cloud but it is available for AWS also. It is also available on AWS through an extension. This helps make a very open market place for developers to choose and work with.
Support for different development technologies:
Visual Studio Team Services does not require everyone to be on the Microsoft Visual Studio. It does work the best with Microsoft Visual Studio. If the development team is using a development technology other than Visual Studio they can still take advantage of Microsoft Team Services due to the fact that Visual Studio Team Services supports Git Hub. Visual Studio Team Services can get the source from Git. That is the basis for developers to use other technologies and still use Visual Studio Team Services.
This is the effort to not to lock any developers to only Visual Studio and let them benefit from team services at the same time.
Visual Studio Team Services has many capabilities and the development team can think of them as offerings and choose what they want to use. If the team needs only the source control, they can use the unlimited Git repository. If the users want to do the planning on Jira, and log issues in Git, that is also possible. Alongside that, if the developers have already purchased private repositories from Git they can go with that and still take advantage of the build services and CICD.
That means that the users can be building an iOS app in swift, it is source controlled in Git and yet the development team can take advantage of the build services offered in visual studio team services tutorial. This can be done by connecting the team services to Git Hub, get the source code and build using the build services. The users can make custom task using PowerShell and build complex tasks and more.
But when the team is using only Visual Studio Team Services there are more advantages as they can relate the commits, work items, and the build test. This integrates the whole software development life cycle into one platform.
A closer look at Visual Studio Team Services:
When a new user logs into the Visual Studio Team Services he can see the project status at a glance. Here the Mark Down file is being rendered by the Visual Studio Team Services from Git. The web UI is very powerful and the users can see the status of the project right from the Web UI.
There are also features for organizing team projects. This lets the users organize themselves into a team project that is building an App A and another team that is building an App B and so on and so forth.
Visual Studio Team Services has a powerful dashboard. The users can have as many dashboards as they want. The dashboard has very powerful customization. This can be customized such that the users can get a good idea of what are the assigned tasks, bugs, epics and more right from the Dashboard. The dashboard is not a piece of static information, it is connected to what is currently happening in the project and so clicking on an item will directly take the users to the detailed information on the item.
Agile with Visual Studio Team Services:
There is very good support for agile concepts. There is a display of burn down rate, scrum duration, and more complex concepts. This also helps the individual developers in the team to properly prioritize the tasks. The dashboard is very customizable. We can edit, we have widgets on the right that we can choose from. We easily get the mainstream ones such as the Markdown, pull request. We can also get more widgets from the extension gallery.
This very very customizable, a development team can build widgets for themselves and publish it such that only their team can use it.
Work Items with Visual Studio Team Services:
The developers can use only the backlogs if they want or they can be fancy and separate certain tasks as Epics and Features. It also has a built-in Kanban board that a team can make use of. This helps the users distribute the work equally with everyone in the team. It also has extensions that help get the data out into Microsoft Excel sheet. This helps the developers solve lots of problems.
CLI for Visual Studio Team Services:
For users who do not prefer Web UI, there is CLI for Windows, Linux, and Mac. Agile is also built into the command line interface. Therefore the tasks, bugs are assigned using command line interface also.
Code Visualizers for Visual Studio Team Services:
It is possible to have third-party CICD with the Git repository. That means that the users can make changes commit using the Web UI, the third party CICD will pick up the code, run the CICD and give the output in their corresponding dashboard. This integration is done seamlessly into Visual Studio Team Services.
CI/CD with Visual Studio Team Services:
CICD is also built into the Visual Studio Team Services that can trigger a build for every commit. It can do a Nuget restore before every build trigger and make sure that every build is made on a new environment. This ensures that maximum successful deployment probability for the application. After every successful build, the Visual Studio Team Services makes artifacts that users can also see and download. These artifacts can be stored away for as long as the developers want and they can always come back and take a look at it.
It is important to note that there are many different tools that the users can download from the market place and integrate with the build. They can download and integrate items such as Bower, CMD and more. It also has Docker and Kubernetes support.
Everything we need from source code, planning, testing to deployment is available with visual studio team services tutorial and everyone can get started for free. This is a very powerful tool from Microsoft that anyone from an opensource developer to a closed source game developer can take advantage of for even free. If you need a more detailed explanation on any specific topic related to the tool, please let us know in the comments below.