This is partly because we are stuck in old habits and partly because we just aren’t aware of what all VS Live Share can do. Multiple developers can collaborate on the same file at the same time without ever leaving their own editor.Īfter the release of Live Share, I realized that many of us have resigned ourselves to being isolated in our code and we’re not even aware that there are better ways to work with a service like VS Live Share. VS Live Share is Google Docs level collaboration for code. VS Live Share is a new service that lets you do exactly that, and you might be surprised at just how much sharing you can actually do.Ī few months ago, Microsoft released its free Visual Studio (VS) Live Share service. In order to really collaborate, a developer needs to be able to share their whole environment. That’s because sharing just code isn’t enough. Collaborating on code is still a pretty difficult thing to do. They can run any command on your computer that you can.Collaborating on office documents is a solved problem. Keep in mind that read/write access gives guests the same access to your terminal that you have. Stick with read-only terminals when you just want the guests to see the output of commands you run. To be safe, you should give read/write access to guests only when you know they actually need it. So, as a host, you can easily intervene if a guest is doing something you don't like. When the terminal is read/write, everyone can type in the terminal, including the host. Select the Share terminal item or button:Īt this point, you can choose whether to make the terminal read-only or read/write. This limitation prevents guests from starting one up and doing something you aren't expecting.Īs a host, you can share a terminal from the Live Share or the Live Share Explorer tab. And only hosts can start shared terminals. This default configuration allows you to run commands in local terminals with reduced risk and share only when you need to. You can also let them run tests or builds or even triage environment-specific problems that only happen on your computer.īy default, terminals aren't shared because they give guests at least read-only access to the output of commands you run (if not the ability to run commands themselves). You can make terminal output visible to guests. The shared terminal can be read-only or fully collaborative, so you and the guests can run commands and see the results. Live Share allows hosts to share a terminal with guests. Modern developers frequently use of a variety of command-line tools. To stop sharing a local server, the host can hover over the server item in the Shared Servers list and then select the Unshare server button: You can also right-click and select an option to copy the server link to the clipboard.įor security reasons, guests can't control which ports on the host's computer are shared. If you select a port, that server opens in your browser. As a guest, you can see a list of shared ports (by name, if specified) on the Live Share Explorer tab or the VS Live Share tab. If the port is already being used on the guest's computer, a different one is automatically selected. That's it! The server on the port you specified will now be mapped to each guest's localhost on the same port (unless that port is already being used). On the Live Share tab or the Live Share Explorer tab, select the Share server item or button:Įnter the number of the port the server is running on. It's easy for the collaboration session host to add one. This behavior is useful, but it can be risky if you share the wrong port.įor security reasons, only servers running on ports that you specify are available to other guests. For guests, shared ports will behave exactly as they would if the server/service were running on the guest's computer. Stick to application ports (rather than sharing a system port). As a host, be selective about the ports you share with guests.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |