Support co-designing with the XAML designer in Visual Studio

[Chuxel]

Currently VS Live Share focuses on co-editing, co-debugging, and related features like sharing a server that is useful during the debugging process.

Live Share does not, however, support "co-designing" in Visual Studio. Visual Studio has a XAML designer that makes it easy to create great UX. This feature request covers the concept of supporting multiple people designing at the same time.

This is a significant undertaking. A possible pre-cursor step could be to enable the XAML designer for guests without the collaborative design capabilities, but in this case multiple guests/hosts would step on each other if the edited at the same time. In concept, we could "lock" editing to a single person or just leave this situation in place.

Give a thumbs up reaction if you'd like to see us look into this concept and sound off below on how far you think we'd need to go.

[Sander0542]

This would be a great option to add! This will give all the users better customization of their Designer.

[Rskeehan]

Honestly, I see this tool being a great for educational purposes as well as collaboration. A perfect tool for 1-on-1 tutorials. The designer view being available for all parties involved would make for an incredible addition for these kind of purposes.

[kingkrayz]

This is a needed feature even if the guests only could see the designer window and only allowed one user during a session to edit.

[spatrick195]

Definitely need this for useful collaboration.

[Zarelious]

the first thing we did when we tried out the live share was to find out how to do this would love to see it implemented.

[ogiesen]

Personally, I do not really care about the designer that much, as I usually work with XAML in code only and only really use the designer for visual verification. Support for collaborative XAML code editing would be perfectly sufficient for me. It would definitely be a great improvement to our pair programming workflow already if I wouldn't lose track of a colleague I'm following whenever they switch to a XAML file...

[fubaduba]

We’re not able to prioritize this issue over the other higher-impact issues we receive every week, based on the votes and comments from others in the community and our understanding of the issue. However, rest assured that we love your input. If you feel it deserves to stay open, then clarify your use case and contact us to let us know how severe it’s for you.