[Discussion] Feedback Area Map

[lostintangent]

This issue captures a high-level picture of outstanding developer feedback, categorized by feature area/scenario (a "feedback area map"). This is not meant to be a commitment/roadmap, so much as a way for us to visualize feedback, track progress, and continue to gather input from the community on priorities. Our goal is to make developer collaboration enjoyable, across the diverse landscape of use-cases, and as a result, we'll be looking into the following themes and explorations (among other things). Input on this is extremely welcome!

❗= High-priority item, that impacts a fundamental part of the experience or would significantly improve the product
🏃= In-progress item, that will be delivered in an upcoming release
🏅= Currently available in our Insiders channel
💪= Area of exploration, that we need more feedback on value, and therefore, isn't planned

Feedback Areas (Visual Studio & VS Code)

1. Extension Acquisition
   • ❗Reduce the impact of extension updates (e.g. don’t download .NET Core each time) (N/A)
   • ❗Store the VSLS agent binary in a global location (N/A)
   • ❗Update our Linux dependency checker to catch common issues
2. Authentication
   • 💪Allow sharing without signing in
   • 💪Support for GitHub Enterprise (#341)
   • 💪Support GitHub SSO in VS (#11)
3. Sharing/Joining
   • ❗Improve performance of sharing/joining (N/A)
   • 🏅🏃Web access for guests (#1235)
   • Allow changing the active workspace without ending the Live Share session
   • Support sharing symlinks (#1598)
   • Prevent old sessions from being opened (#1003)
   • 💪Teams entry point (#882)
4. Connectivity
   • ❗ Continue to increase network resilience / disconnections (#67, #1443, #1619)
   • ❗ 🏃Proxy-related issues (#1353)
5. Co-Editing
   • ❗🏃 Co-editing de-syncs (e.g. after a file rename) (#206)
   • ❗ Make undo work as expected (a personal vs. shared undo stack) (Can undo changes made by others #1439)
   • ❗🏃Investigate edits taking a long time to propagate (N/A)
   • ❗Formatting issues (#218, #286, #568, #1162)
   • ❗Keyboard shortcuts (#186)
   • 💪Item templates in Visual Studio (e.g. MVC controller)
   • 💪Enabling guest's to use their own snippets (Visual Studio)
   • 💪Pinning an editor group / "Follow to the side" (#81)
   • Participant / cursor theming (#376, #1547)
6. Following/Focus
   • ❗ Improve discoverability of follow/focus (Improve Pair-Programming by auto-following whoever starts to edit #2669)
   • ❗Allow identifying when someone is following you (N/A)
   • 💪Follow users into diff view (e.g. to support code reviews)
   • 💪Follow users into terminals
   • 💪"Super follow mode" (e.g. follow search queries, file tree position, etc.) (#1954)
   • 💪Project wide presence (#185, #281)
7. Language Services
   • ❗Completion list closing when someone types in VS (#730)
   • 💪Support other languages in Visual Studio (e.g. Razor, F#, XAML) (#1501)
8. Terminal
   • ❗Terminal resizing / issues (#456)
   • Display who is typing in terminal (#596)
   • 💪Allow granular terminal permissions (#1844)
9. Shared Servers
   • ❗ Shared servers / SSL (#1507)
   • 💪Sharing DNS domains in addition to TCP ports (#264)
   • 💪Allow exposing a server via a public domain, so non-Live Share guests can view it (N/A)
10. Debugging
    • 🏅🏃❗Application window sharing (e.g. desktop apps, VS Code extensions) (#236)
    • 🏅❗Sharing the debug terminal for console projects (Visual Studio)
    • ❗Make guest debugging control dynamic (#1550)
    • 💪Synchronize Debug Console output
11. Security/Access Control
    • 🏃❗Add support for text chat in the web clientIntroduce additional policy settings/APIs to provide users with more control (e.g. enforce direct mode, prevent non-organization users from joining sessions)
    • ❗Re-evaluate the default .gitignore behavior (N/A)
    • 💪 Explore ways to censor secrets embedded within files
    • 💪Limit Live Share sessions to certain users (#2018)
12. Session Management
    • ❗Edit adornments / activity log (#680)
    • ❗Add support for "planned sessions" to VS
    • 💪Saving a workspace (#671)
    • 💪Persisting a session (#56)
    • 💪"Lecture mode" (#87, #2008)
13. Testing
    • 🏅🏃❗Test Explorer support in Visual Studio (#33)
14. Version Control
    • 🏃❗Team Explorer support in Visual Studio (#1746)
15. Chat
    • 🏃❗ Migrate Live Share Chat functionality into the core VS Code extension
    • 🏃❗Add support for text chat in the web client
    • ❗Add support for text chat in Visual Studio
16. Audio
    • 🏅🏃Add Visual Studio support (#741)
    • 🏃❗Add support for text chat in the web client
    • Persist microphone/speaker selection across sessions (N/A)
    • Display users that are joining
17. Comments
    • 💪Add support in Visual Studio (N/A)
    • 💪Enable persisting them to a file (N/A)
    • 💪Allow migrating Live Share comments to PR comments (N/A)
18. Extensibility
    • ❗Investigate interop issues with the Vim extensions
    • 💪Enable extensions to detect if a user has read-only access (#1716)
    • 💪Enable extensions to detect if a user is following another user (#1717)
19. Designers
    • 💪Shared XAML/WinForms designer (N/A)

[gusbemacbe]

Hi @lostintangent

Sorry for entering this issue, but I have read the documentation https://docs.microsoft.com/en-us/visualstudio/liveshare/reference/extensions which does not cite «Emmet».

«Emmet: Wrap abbreviation» does not work on guest's Live Share. Without it, I would be totally unproductive and forced to do everything manually, what will take a lot of hours. It is totally unfair for me. My CTO wants me to have full Emmet to work quickly.

[lostintangent]

@gusbemacbe Despite not being listed, the Emmet extension should work in a Live Share session. Have you run into issues with it?

[gusbemacbe]

Yes, @lostintangent, I could not wrap the HTML text, using the command «Emmet: Wrap abbreviation» from the popup open with Ctrl + Shift + P.

[botscholar-scott]

Hello @lostintangent

What does it mean if the checkbox is checked above? I'm curious about item 13 specifically.

[lostintangent]

@phx-srankin Good question! The check means that it's been shipped, without requiring you to opt-into the Live Share "insiders" channel. Since the VS/Test Explorer support is only available in insiders, I removed the check mark. Thanks for the reminder!

[lostintangent]

Closing this item, since it has served us well over the last year :) I'll be re-creating a new one to track the open feedback moving forward.