![\"VSTSMarketplace\"](\"https:\/\/blogs.ncl.ac.uk\/isg\/files\/2016\/07\/VSTSMarketplace.png\")
<\/a><\/p>\nOne extension which I think everyone should add is Code Search<\/strong>, which has been written by Microsoft themselves. This gives you a handy search tool which you can use to find bits of code in your repo which match a variety of criteria. You’ve got a number of powerful search options to make sure you find what you’re looking for, no matter how big your codebase is.<\/p>\n The other extension that we use all the time is the Microsoft-written integration extension for the Slack<\/strong> messaging app. We’ll probably have another post in the future about Slack – it’s a great tool for teams doing DevOps style work because of all the integration options that it has. By using the VSTS\/Slack integration, we all get notifications (in the Slack desktop or mobile apps) of code commits and automated test results, so we don’t need to open the VSTS website to see how builds have gone.<\/p>\n We’ll sometimes commit some code and then stick a comment in the Slack channel for the team if we’re perhaps expecting the build to fail for some reason, and we might have a little group celebration of success in the channel when something we were struggling with eventually works.<\/p>\n Useful, huh?<\/p>\n You can have a browse of the VSTS marketplace at\u00a0https:\/\/marketplace.visualstudio.com\/VSTS<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" As useful as Visual Studio Team Services is by itself, and with its API (we sync our LANDesk tickets with the VSTS Kanban board via the REST API – I’ll write a post about that sometime), it can be made … Continue reading <\/a><\/p>\n<\/a><\/p>\n