Allow specifying a static session URL

[DevBenLefevre]

This question may have been already asked but, can we have "persistent sessions" ?

Like "https://insiders.liveshare.vsengsaas.visualstudio.com/join?DevBenLefevre" for example ? It would be easier to collaborate. It will simplify repeated use of Live Share.

Thank's :)

[svorobiev]

Case in point. I use live share on Ubuntu 14 host where it is all but impossible to configure copy-paste over rdp. My life would become so much better if I would not have to go through contortions to get the session link out from host to windows guest.

[lostintangent]

Hey folks! We’re beginning to explore this item, and we’d love to get some feedback. In particular, how would you expect to use this? For example, are you currently using a chat tool (like Slack, Teams) to co-ordinate a collaboration session, and the static URL would simply prevent needing to copy/paste another link? Would #190 or #882 be a preferable solution to this issue?

Any details you could share about your use cases would also be greatly appreciated (e.g. daily pair programming, developer streaming, code reviews) 👍

---

If the static URL solution is most appealing, would you expect to always use a static URL when sharing? Or would you want to toggle between static and dynamic on a per-session basis?

In general, I’m wondering if folks are looking for a persistent URL that is re-useable for some period of time (e.g. a month, until you change it, 20 sessions), as opposed to a truly static (and predictable?) URL. That way, you can improve the ergonomics of repeated use (regular pairs can re-use the old link), while retaining the flexibility of changing it if/when needed (e.g. you gave it to someone you no longer trust).

[svorobiev]

I need to prevent needing copy-paste because I cannot copy-paste :-). Either form of reusability that you propose will do. #190 would be the preferred solution since I have no Slack not Teams on the Live Share host (and #882 isn't a solution at all for the same reason).

As for predictable URLs, I would expect that such capability is a premium feature. Think Webex URLs. I would like to have it though :-)

[lostintangent]

@svorobiev Thanks! Is your main use case for Live Share to remotely develop from another machine, as opposed to collaboration? Or are you developing in a VM running locally on your dev machine and then collaborating from there? Apologies for the dumb question, I couldn’t entirely tell from your previous comment 😁

[neico]

Warning: random thought train!

One way I could imagine static urls to work is by being able to set some sort of namespace, either so you could for example set a company as a namespace and set different workspaces as sub-links: <namespace>/[<username>/]<workspace>[/<username>] (I used username twice here because I'm unsure if it should be sorted per-user or per-workspace, but in both cases optional)

This could probably be managed with a website endpoint where you could also set managers of the namespace and who is able to use those workspace links (and maybe also set managers per-workspace), that way you'd do 2 features with one go, or simply set the link as "ask before joining and then add account to list"

The integration itself can then simply fetch the available links using the identified account and ask the user to assign each link to a workspace it should share (seeing an overview on the namespace site which workspace is currently online and shareable might be also an interesting gimmick)

Probably overkill but seems flexible enough to add other features in the long run (at least in my head it is)

In the end we shouldn't need to spam chats with invite links one way or another, for quick and unmanaged projects which is usually a one-time thing it's ok enough, but for anything that involves sharing something on a regular basis (think of a live code review, or working on a bigger feature over weeks / months with a small team, where the one who started the feature holds all the code) it's getting tedious, especially on chats that save history like discord / slack

PS: #190 is a great step in-between what we have currently and having static links (and probably easier to realize in general)

[CoolDadTx]

In a classroom environment it is painful when class starts to get everyone connected. Our campus has a shared website where each class has a session and I can post an announcement. When I get to class I start VS, load my solution, start the session, copy the link, update the announcement and then have students go to the announcement and click the link. Sharing this link is painful.

Having a persisted link would make it easy for me to set up a single URL for the entire semester. I'm not too worried about others (outside the class) accessing it but I could see that being a concern as well. If a persistent link isn't possible then a very short link that can be easily typed would be better than the currently unique but too long URL.

[inirudebwoy]

Hi,

Really like the feature of being able to share my session. I use it to share what I'm working on at work. The pain of keeping people updated was big enough so I created extension that keeps a static link that will not change (unless I guess vscode is reinstalled) and when URL is opened it redirects to live share session.

Instead of starting session with Live Share extension you start your live session by pressing Ctrl+Shift+p and running command Oversharing: Share session.

Hopefully you will find it helpful

https://marketplace.visualstudio.com/items?itemName=klich-dev.oversharing

[lostintangent]

This feature has been shipped and can be used by running the Live Share: Create Persistent Link command 👍

[chiragpurohit71085]

I am not able to view Live Share: Create Persistent Link. Am I missing something here?

[finnmerlett]

Why was this feature removed??

[SichangHe]

Is there a similar functionality now? Having to send collaborators new links every day is annoying.