├── .editorconfig ├── .github ├── ISSUE_TEMPLATE │ ├── bug_report.md │ ├── config.yml │ └── desync_report.md └── workflows │ ├── CloseInactiveIssues.yml │ └── label-issues.yml ├── .gitignore ├── .vscode ├── extensions.json ├── settings.json └── tasks.json ├── CONTRIBUTING.md ├── LICENSE ├── LICENSE-CODE ├── README.md ├── SECURITY.md └── ThirdPartyNotices /.editorconfig: -------------------------------------------------------------------------------- 1 | [*] 2 | indent_style = space 3 | indent_size = 4 -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: Create a report to help us improve 4 | 5 | --- 6 | **Describe what happened:** 7 | 8 | **What was your system configuration?** 9 | *Product and Version* [VS/VSCode]: 10 | *OS Version*[macOS/Windows]: 11 | *Live Share Extension Version*: 12 | *Target Platform or Language* [e.g. Node.js]: 13 | 14 | **Steps to Reproduce / Scenario:** 15 | 1. Go to '...' 16 | 2. Click on '....' 17 | 3. Scroll down to '....' 18 | 4. See error 19 | 20 | 21 | **Please attach logs to this issue:** 22 | *You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue* 23 | 24 | **Screenshots** 25 | If applicable, add screenshots to help explain your problem. 26 | 27 | 34 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/config.yml: -------------------------------------------------------------------------------- 1 | blank_issues_enabled: false 2 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/desync_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Desync 3 | about: Please provide information about the desync you encountered to help us resolve the problem 4 | --- 5 | 6 | **Before filing a new issue, check that it's not already captured by one in [this list](https://github.com/MicrosoftDocs/live-share/issues/4260)** 7 | 8 | **Product and Version** [VS/VSCode]: 9 | **OS Version** [macOS/Windows/Linux]: 10 | **Live Share Extension Version**: 11 | **Target Platform or Language** [e.g. Node.js]: 12 | 13 | **What were you doing when you encountered the desync?** 14 | 15 | **How often have you encountered desyncs?** 16 | 17 | **Do the host and the guest have the same contents?** 18 | 19 | *If yes, there's no need to answer the following questions* 20 | 21 | If you are using VS Code, the following will provide helpful information. 22 | 23 | On both the host and the guest: 24 | - Enable the `liveshare.diagnosticMode` setting 25 | - Open the file that's out of sync 26 | - Run the `liveshare.getCoeditingInformation` command (`ctrl+shift+p` to open the command palette, then search for "Get co-editing information") and paste the results below 27 | 28 | **Host co-editing information:** 29 | 30 | **Guest co-editing information:** 31 | 32 | To check that messages are being sent and received, open the Output view (`ctrl+shift+u`) and select "Visual Studio Live Share Coediting" from the dropdown. Type a character. On the sending end, you should see output like: 33 | ``` 34 | [2020-12-10 23:51:25.351 ] Post message: {"messageType":"textChange","changes":[{"length":0,"newText":"a","start":400}],"changeServerVersion":12,"clientId":24,"fileName":"/src/foo.txt","time":1607644285349,"sendId":16} 35 | ``` 36 | On the receiving end, you should see output like: 37 | ``` 38 | [2020-12-10 23:51:27.713 ] Receive message: {"context":{"GuestSessionId":"31","IsOwner":"False"},"sourceId":"Coauthoring","eventId":45,"jsonContent":"{"messageType":"textChange","changes":[{"length":0,"newText":"a","start":400}],"changeServerVersion":12,"clientId":24,"fileName":"/src/foo.txt","time":1607644427514,"sendId":25}","time":1607644427713} 39 | ``` 40 | **Are messages being sent and received?** 41 | -------------------------------------------------------------------------------- /.github/workflows/CloseInactiveIssues.yml: -------------------------------------------------------------------------------- 1 | 2 | name: 'Close stale issues' 3 | on: 4 | schedule: 5 | - cron: '0 10 * * 1-5' 6 | 7 | jobs: 8 | stale: 9 | runs-on: ubuntu-latest 10 | steps: 11 | - uses: actions/stale@v4 12 | with: 13 | exempt-issue-labels: "keep" 14 | any-of-labels: "needs-more-info" 15 | start-date: "2023-01-01T00:00:00Z" 16 | stale-issue-message: 'This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically shortly.' 17 | days-before-issue-stale: 14 18 | days-before-issue-close: 2 19 | operations-per-run: 1000 20 | close-issue-label: "wontfix" 21 | close-issue-reason: "not_planned" 22 | debug-only: false 23 | -------------------------------------------------------------------------------- /.github/workflows/label-issues.yml: -------------------------------------------------------------------------------- 1 | # See https://github.com/marketplace/actions/close-stale-issues 2 | # As used here, "stale" is a misnomer. This uses the predefined action close-stale-issues to 3 | # label issues that have not been categorized with one of the triage label types 4 | # shown in line 22. Runs on the 1st day of every month. 5 | 6 | name: label-untriaged-issues 7 | 8 | on: 9 | schedule: 10 | - cron: "1 1 1 * *" 11 | 12 | jobs: 13 | stale: 14 | runs-on: ubuntu-latest 15 | steps: 16 | - uses: actions/stale@v3 17 | with: 18 | repo-token: ${{ secrets.GITHUB_TOKEN }} 19 | stale-issue-message: 'Automatically marked uncategorized issue as product feedback' 20 | stale-issue-label: 'product-feedback' 21 | exempt-issue-labels: 'doc-bug,feature-request,doc-enhancement,doc-idea,doc-experience,product-issue,product-question' 22 | remove-stale-when-updated: false 23 | days-before-close: -1 24 | days-before-issue-stale: 1 25 | days-before-pr-stale: -1 26 | 27 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | log/ 2 | obj/ 3 | _site/ 4 | .optemp/ 5 | _themes*/ 6 | _repo.*/ 7 | 8 | .openpublishing.buildcore.ps1 9 | 10 | .vs 11 | 12 | docfx.console 13 | 14 | vslivesharedocs 15 | 16 | .vsls.json 17 | 18 | .DS_Store -------------------------------------------------------------------------------- /.vscode/extensions.json: -------------------------------------------------------------------------------- 1 | { 2 | "recommendations": [ 3 | "docsmsft.docs-authoring-pack" 4 | ] 5 | } -------------------------------------------------------------------------------- /.vscode/settings.json: -------------------------------------------------------------------------------- 1 | { 2 | "cSpell.words": [ 3 | "Arduino", 4 | "CFML", 5 | "Capitan", 6 | "IntelliJ", 7 | "Kwallet", 8 | "MATLAB", 9 | "TLDR", 10 | "Thons", 11 | "Xubuntu", 12 | "aspdotnet", 13 | "bracketeer", 14 | "caml", 15 | "chuxel", 16 | "clantz", 17 | "coedit", 18 | "customizations", 19 | "debugging", 20 | "deterministically", 21 | "distros", 22 | "erlang", 23 | "filesystems", 24 | "gettext", 25 | "gitignore", 26 | "guestapproval", 27 | "hlsl", 28 | "intelli", 29 | "intellisenese", 30 | "joncart", 31 | "jorgicio", 32 | "keyring", 33 | "kubuntu", 34 | "libcurl", 35 | "libgsasl", 36 | "libicu", 37 | "libkrb", 38 | "liblttng", 39 | "libopenssl", 40 | "libsecret", 41 | "libssl", 42 | "libunwind", 43 | "liburcu", 44 | "libuuid", 45 | "liveshare", 46 | "lostintangent", 47 | "lttng", 48 | "mailto", 49 | "manjaro", 50 | "markdownlint", 51 | "nginx", 52 | "opencode", 53 | "openssl", 54 | "phpcs", 55 | "prereq", 56 | "procs", 57 | "quickstart", 58 | "quickstarts", 59 | "quokka", 60 | "remoted", 61 | "repls", 62 | "repo", 63 | "reqs", 64 | "res", 65 | "servicebus", 66 | "sharepoint", 67 | "solus", 68 | "sync'ing", 69 | "tful", 70 | "timeit", 71 | "tldr", 72 | "upvote", 73 | "userprofile", 74 | "vbhtml", 75 | "vetur", 76 | "visualstudio", 77 | "vsengsaas", 78 | "vsliveshare", 79 | "walkthrough", 80 | "xamarin", 81 | "xprop", 82 | "xsel" 83 | ], 84 | "markdownlint.config": { 85 | "default": true, 86 | "MD007": { "indent": 4 }, 87 | "MD033": false, 88 | "MD013": false, 89 | "MD034": false, 90 | "MD026": false 91 | }, 92 | "favorites.sortDirection": "ASC", 93 | "favorites.groupsFirst": true, 94 | "workbench.colorCustomizations": {} 95 | 96 | } -------------------------------------------------------------------------------- /.vscode/tasks.json: -------------------------------------------------------------------------------- 1 | { 2 | // See https://go.microsoft.com/fwlink/?LinkId=733558 3 | // for the documentation about the tasks.json format 4 | "version": "2.0.0", 5 | "tasks": [ 6 | { 7 | "label": "docfx serve", 8 | "type": "shell", 9 | "command": "${workspaceFolder}/.build/serve.sh", 10 | "options": { 11 | "cwd": "${workspaceFolder}/.build" 12 | }, 13 | "windows": { 14 | "command": "${workspaceFolder}/.build/serve.cmd" 15 | }, 16 | "group": { 17 | "kind": "build", 18 | "isDefault": true 19 | } 20 | } 21 | ] 22 | } -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | 6 | 7 | # Contributing 8 | 9 | ## TLDR 10 | 11 | In short: 12 | 13 | - **Known issues:** See [bugs](https://aka.ms/vsls-bugs) or [feature requests](https://aka.ms/vsls-feature-requests) and up-vote using a 👍 reaction. 14 | - **VS Code bugs:** [Log a new issue](https://aka.ms/vsls-new-issue). Use the "Live Share: Export logs" command and [drag-and-drop the zip](https://help.github.com/articles/file-attachments-on-issues-and-pull-requests/) onto the bug. 15 | - **VS bugs:** [Help > Send Feedback > Report a Problem...](https://learn.microsoft.com/visualstudio/ide/how-to-report-a-problem-with-visual-studio-2017) Repro the problem before sending and logs will be auto-attached. 16 | - **Feature requests:** [Log a new request](https://aka.ms/vsls-new-issue) or use a 👍 reaction to [up-vote an existing one](https://aka.ms/vsls-feature-requests). 17 | 18 | More details below. 19 | 20 | ## Up-Vote an existing problem report or feature request 21 | 22 | If you are wondering if someone has already encountered a problem or requested a feature, you can check out [open issues](https://github.com/Microsoft/live-share/issues). You can also use [this query](https://aka.ms/vsls-feature-requests) to specifically search for feature requests. 23 | 24 | If you find your issue/feature already exists, feel free to make relevant comments and add your [reaction](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments). Use a reaction in place of a "+1" comment. 25 | 26 | 👍 - upvote 27 | 28 | 👎 - downvote 29 | 30 | ## File a problem report 31 | 32 | ### Step 1 - [Optional] Check output logs 33 | 34 | If you're seeing an error pop up that is not very descriptive, the output logs can help you understand if this is a known issue. Simply go to the "Output" window and select the "Visual Studio Live Share" log stream. Verbose logging is on by default. 35 | 36 | ### Step 2A - File a Visual Studio problem 37 | 38 | Visual Studio has a built in feedback mechanism via the "Report a Problem..." tool that provides the engineering team detailed information about your installation that you should use to log bugs or problems you encounter when using VS. 39 | 40 | Logs will be automatically attached. 41 | 42 | > **Tip:** You may be able to save yourself some time by simply up-voting an existing problem report. You may search for existing issue in the Visual Studio Feedback tool but be aware your problem may be related to multiple clients and therefore is logged in the GitHub [issue repository](https://github.com/Microsoft/live-share/issues). 43 | 44 | Note that after your problem report is filed, it may be converted to a [GitHub issue](https://github.com/Microsoft/live-share/issues) for future tracking if it applies multiple clients or turns out to be a feature request. In this event, a link to the corresponding GitHub issue number will be referenced in comments on your raised problem report. 45 | 46 | Check out the tips in "[Writing Good Problem Reports and Feature Requests](#tip-writing-good-problem-reports-and-feature-requests)" for additional suggestions. 47 | 48 | ### Step 2B - File a VS Code or general service problems 49 | 50 | 1. **Export logs:** Press F1 (or Ctrl+Shift+P / Cmd+Shift+P), type "export logs" and run the "Live Share: Export Logs" command. 51 | 52 | 2. **Raise a new issue:** [Click here to draft a new issue](https://aka.ms/vsls-new-issue) and please add following information into the description: 53 | 54 | 55 | - **Tool:** VS, VS Code for Mac, VS Code for Windows 56 | - **OS and Version:** Windows 7/8/8.1/10, macOS Sierra/High Sierra 57 | - **Extension version:** Mention the version you installed with your VS/VSCode. 58 | - **Target Platform/Language:** Mention the language / project type you were using (e.g. ASP.NET Core, Node.js) 59 | - Be sure to specify whether you are using .NET Core or Full .NET for .NET related scenarios 60 | - **Repro steps:** Prefix the repro steps with [Host] or [Guest] to make it easy to repro the bug 61 | 62 | 3. **Attach logs:** Drag-and-drop the zipped logs from step 1 into the issue text and wait for it to upload. 63 | 64 | 4. **Click "Submit new issue"** 65 | 66 | Check out the tips in "[Writing Good Problem Reports and Feature Requests](#tip-writing-good-problem-reports-and-feature-requests)" for additional suggestions. 67 | 68 | ## Filing Feature Requests 69 | 70 | Many feature requests start out life as reported problems and should therefore follow the processes described above. However, if you believe you have a feature request that is not a bug, you can follow these steps. 71 | 72 | > Tip: You may be able to save yourself some time by using this [query](https://aka.ms/vsls-feature-requests) to see if your request already exists. If you find it, 👍 (upvote) it. 73 | 74 | Simply [click here to draft a new issue](https://aka.ms/vsls-new-issue) and add as much of the following information into the description as is appropriate: 75 | 76 | - **Tool:** VS, VS Code for Mac, VS Code for Windows 77 | - **OS and Version:** Windows 7/8/8.1/10, macOS Sierra/High Sierra 78 | - **Extension version:** Mention the version you installed with your VS/VSCode. 79 | - **Project Type:** Mention the language / project type you were using (e.g. ASP.NET Core, Node.js) 80 | - Be sure to specify whether you are using .NET Core or Full .NET for .NET related scenarios 81 | 82 | Be as specific as you can be with the problem or scenario you are trying to solve with the requested feature and let us know any painful workarounds you are having to do. 83 | 84 | As with problem reports, don't feel bad if we ask for more information while we try to understand your scenario. 85 | 86 | ### Tip: Writing Good Problem Reports and Feature Requests 87 | 88 | Here are a few tips that will help us understand your problem or feedback quickly. 89 | 90 | > **Tip:** You may be able to save yourself some time by searching the [issue repository](https://github.com/Microsoft/live-share/issues) to see if the problem/request already exists so you can simply up-vote it. 91 | 92 | First, try to file a single issue per problem or feature request. 93 | 94 | * Do not enumerate multiple bugs or feature requests in the same issue. 95 | * Do not add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar, but have different causes. 96 | 97 | The more information you can provide, the more likely someone will be successful reproducing the issue and finding a fix. 98 | 99 | * Reproducible steps (1... 2... 3...) and what you expected versus what you actually saw. 100 | * Images, animations, or a link to a video. 101 | * A code snippet that demonstrates the issue or a link to a code repository we can easily pull down onto our machine to recreate the issue. 102 | 103 | Don't feel bad if we can't reproduce the issue and ask for more information! 104 | 105 | ## Discussion Etiquette 106 | 107 | In order to keep the conversation clear and transparent, please limit discussion to English and keep things on topic with the issue. Be considerate to others and try to be courteous and professional at all times. This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). 108 | 109 | For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. 110 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Attribution 4.0 International 2 | 3 | ======================================================================= 4 | 5 | Creative Commons Corporation ("Creative Commons") is not a law firm and 6 | does not provide legal services or legal advice. Distribution of 7 | Creative Commons public licenses does not create a lawyer-client or 8 | other relationship. Creative Commons makes its licenses and related 9 | information available on an "as-is" basis. Creative Commons gives no 10 | warranties regarding its licenses, any material licensed under their 11 | terms and conditions, or any related information. Creative Commons 12 | disclaims all liability for damages resulting from their use to the 13 | fullest extent possible. 14 | 15 | Using Creative Commons Public Licenses 16 | 17 | Creative Commons public licenses provide a standard set of terms and 18 | conditions that creators and other rights holders may use to share 19 | original works of authorship and other material subject to copyright 20 | and certain other rights specified in the public license below. The 21 | following considerations are for informational purposes only, are not 22 | exhaustive, and do not form part of our licenses. 23 | 24 | Considerations for licensors: Our public licenses are 25 | intended for use by those authorized to give the public 26 | permission to use the material in ways otherwise restricted by 27 | copyright and certain other rights. Our licenses are 28 | irrevocable. Licensors should read and understand the terms 29 | and conditions of the license they choose before applying it. 30 | Licensors should also secure all rights necessary before 31 | applying our licenses so that the public can reuse the 32 | material as expected. Licensors should clearly mark any 33 | material not subject to the license. This includes other CC- 34 | licensed material, or material used under an exception or 35 | limitation to copyright. More considerations for licensors: 36 | wiki.creativecommons.org/Considerations_for_licensors 37 | 38 | Considerations for the public: By using one of our public 39 | licenses, a licensor grants the public permission to use the 40 | licensed material under specified terms and conditions. If 41 | the licensor's permission is not necessary for any reason--for 42 | example, because of any applicable exception or limitation to 43 | copyright--then that use is not regulated by the license. Our 44 | licenses grant only permissions under copyright and certain 45 | other rights that a licensor has authority to grant. Use of 46 | the licensed material may still be restricted for other 47 | reasons, including because others have the copyright or other 48 | rights in the material. A licensor may make special requests, 49 | such as asking that all changes be marked or described. 50 | Although not required by our licenses, you are encouraged to 51 | respect those requests where reasonable. More_considerations 52 | for the public: 53 | wiki.creativecommons.org/Considerations_for_licensees 54 | 55 | ======================================================================= 56 | 57 | Creative Commons Attribution 4.0 International Public License 58 | 59 | By exercising the Licensed Rights (defined below), You accept and agree 60 | to be bound by the terms and conditions of this Creative Commons 61 | Attribution 4.0 International Public License ("Public License"). To the 62 | extent this Public License may be interpreted as a contract, You are 63 | granted the Licensed Rights in consideration of Your acceptance of 64 | these terms and conditions, and the Licensor grants You such rights in 65 | consideration of benefits the Licensor receives from making the 66 | Licensed Material available under these terms and conditions. 67 | 68 | 69 | Section 1 -- Definitions. 70 | 71 | a. Adapted Material means material subject to Copyright and Similar 72 | Rights that is derived from or based upon the Licensed Material 73 | and in which the Licensed Material is translated, altered, 74 | arranged, transformed, or otherwise modified in a manner requiring 75 | permission under the Copyright and Similar Rights held by the 76 | Licensor. For purposes of this Public License, where the Licensed 77 | Material is a musical work, performance, or sound recording, 78 | Adapted Material is always produced where the Licensed Material is 79 | synched in timed relation with a moving image. 80 | 81 | b. Adapter's License means the license You apply to Your Copyright 82 | and Similar Rights in Your contributions to Adapted Material in 83 | accordance with the terms and conditions of this Public License. 84 | 85 | c. Copyright and Similar Rights means copyright and/or similar rights 86 | closely related to copyright including, without limitation, 87 | performance, broadcast, sound recording, and Sui Generis Database 88 | Rights, without regard to how the rights are labeled or 89 | categorized. For purposes of this Public License, the rights 90 | specified in Section 2(b)(1)-(2) are not Copyright and Similar 91 | Rights. 92 | 93 | d. Effective Technological Measures means those measures that, in the 94 | absence of proper authority, may not be circumvented under laws 95 | fulfilling obligations under Article 11 of the WIPO Copyright 96 | Treaty adopted on December 20, 1996, and/or similar international 97 | agreements. 98 | 99 | e. Exceptions and Limitations means fair use, fair dealing, and/or 100 | any other exception or limitation to Copyright and Similar Rights 101 | that applies to Your use of the Licensed Material. 102 | 103 | f. Licensed Material means the artistic or literary work, database, 104 | or other material to which the Licensor applied this Public 105 | License. 106 | 107 | g. Licensed Rights means the rights granted to You subject to the 108 | terms and conditions of this Public License, which are limited to 109 | all Copyright and Similar Rights that apply to Your use of the 110 | Licensed Material and that the Licensor has authority to license. 111 | 112 | h. Licensor means the individual(s) or entity(ies) granting rights 113 | under this Public License. 114 | 115 | i. Share means to provide material to the public by any means or 116 | process that requires permission under the Licensed Rights, such 117 | as reproduction, public display, public performance, distribution, 118 | dissemination, communication, or importation, and to make material 119 | available to the public including in ways that members of the 120 | public may access the material from a place and at a time 121 | individually chosen by them. 122 | 123 | j. Sui Generis Database Rights means rights other than copyright 124 | resulting from Directive 96/9/EC of the European Parliament and of 125 | the Council of 11 March 1996 on the legal protection of databases, 126 | as amended and/or succeeded, as well as other essentially 127 | equivalent rights anywhere in the world. 128 | 129 | k. You means the individual or entity exercising the Licensed Rights 130 | under this Public License. Your has a corresponding meaning. 131 | 132 | 133 | Section 2 -- Scope. 134 | 135 | a. License grant. 136 | 137 | 1. Subject to the terms and conditions of this Public License, 138 | the Licensor hereby grants You a worldwide, royalty-free, 139 | non-sublicensable, non-exclusive, irrevocable license to 140 | exercise the Licensed Rights in the Licensed Material to: 141 | 142 | a. reproduce and Share the Licensed Material, in whole or 143 | in part; and 144 | 145 | b. produce, reproduce, and Share Adapted Material. 146 | 147 | 2. Exceptions and Limitations. For the avoidance of doubt, where 148 | Exceptions and Limitations apply to Your use, this Public 149 | License does not apply, and You do not need to comply with 150 | its terms and conditions. 151 | 152 | 3. Term. The term of this Public License is specified in Section 153 | 6(a). 154 | 155 | 4. Media and formats; technical modifications allowed. The 156 | Licensor authorizes You to exercise the Licensed Rights in 157 | all media and formats whether now known or hereafter created, 158 | and to make technical modifications necessary to do so. The 159 | Licensor waives and/or agrees not to assert any right or 160 | authority to forbid You from making technical modifications 161 | necessary to exercise the Licensed Rights, including 162 | technical modifications necessary to circumvent Effective 163 | Technological Measures. For purposes of this Public License, 164 | simply making modifications authorized by this Section 2(a) 165 | (4) never produces Adapted Material. 166 | 167 | 5. Downstream recipients. 168 | 169 | a. Offer from the Licensor -- Licensed Material. Every 170 | recipient of the Licensed Material automatically 171 | receives an offer from the Licensor to exercise the 172 | Licensed Rights under the terms and conditions of this 173 | Public License. 174 | 175 | b. No downstream restrictions. You may not offer or impose 176 | any additional or different terms or conditions on, or 177 | apply any Effective Technological Measures to, the 178 | Licensed Material if doing so restricts exercise of the 179 | Licensed Rights by any recipient of the Licensed 180 | Material. 181 | 182 | 6. No endorsement. Nothing in this Public License constitutes or 183 | may be construed as permission to assert or imply that You 184 | are, or that Your use of the Licensed Material is, connected 185 | with, or sponsored, endorsed, or granted official status by, 186 | the Licensor or others designated to receive attribution as 187 | provided in Section 3(a)(1)(A)(i). 188 | 189 | b. Other rights. 190 | 191 | 1. Moral rights, such as the right of integrity, are not 192 | licensed under this Public License, nor are publicity, 193 | privacy, and/or other similar personality rights; however, to 194 | the extent possible, the Licensor waives and/or agrees not to 195 | assert any such rights held by the Licensor to the limited 196 | extent necessary to allow You to exercise the Licensed 197 | Rights, but not otherwise. 198 | 199 | 2. Patent and trademark rights are not licensed under this 200 | Public License. 201 | 202 | 3. To the extent possible, the Licensor waives any right to 203 | collect royalties from You for the exercise of the Licensed 204 | Rights, whether directly or through a collecting society 205 | under any voluntary or waivable statutory or compulsory 206 | licensing scheme. In all other cases the Licensor expressly 207 | reserves any right to collect such royalties. 208 | 209 | 210 | Section 3 -- License Conditions. 211 | 212 | Your exercise of the Licensed Rights is expressly made subject to the 213 | following conditions. 214 | 215 | a. Attribution. 216 | 217 | 1. If You Share the Licensed Material (including in modified 218 | form), You must: 219 | 220 | a. retain the following if it is supplied by the Licensor 221 | with the Licensed Material: 222 | 223 | i. identification of the creator(s) of the Licensed 224 | Material and any others designated to receive 225 | attribution, in any reasonable manner requested by 226 | the Licensor (including by pseudonym if 227 | designated); 228 | 229 | ii. a copyright notice; 230 | 231 | iii. a notice that refers to this Public License; 232 | 233 | iv. a notice that refers to the disclaimer of 234 | warranties; 235 | 236 | v. a URI or hyperlink to the Licensed Material to the 237 | extent reasonably practicable; 238 | 239 | b. indicate if You modified the Licensed Material and 240 | retain an indication of any previous modifications; and 241 | 242 | c. indicate the Licensed Material is licensed under this 243 | Public License, and include the text of, or the URI or 244 | hyperlink to, this Public License. 245 | 246 | 2. You may satisfy the conditions in Section 3(a)(1) in any 247 | reasonable manner based on the medium, means, and context in 248 | which You Share the Licensed Material. For example, it may be 249 | reasonable to satisfy the conditions by providing a URI or 250 | hyperlink to a resource that includes the required 251 | information. 252 | 253 | 3. If requested by the Licensor, You must remove any of the 254 | information required by Section 3(a)(1)(A) to the extent 255 | reasonably practicable. 256 | 257 | 4. If You Share Adapted Material You produce, the Adapter's 258 | License You apply must not prevent recipients of the Adapted 259 | Material from complying with this Public License. 260 | 261 | 262 | Section 4 -- Sui Generis Database Rights. 263 | 264 | Where the Licensed Rights include Sui Generis Database Rights that 265 | apply to Your use of the Licensed Material: 266 | 267 | a. for the avoidance of doubt, Section 2(a)(1) grants You the right 268 | to extract, reuse, reproduce, and Share all or a substantial 269 | portion of the contents of the database; 270 | 271 | b. if You include all or a substantial portion of the database 272 | contents in a database in which You have Sui Generis Database 273 | Rights, then the database in which You have Sui Generis Database 274 | Rights (but not its individual contents) is Adapted Material; and 275 | 276 | c. You must comply with the conditions in Section 3(a) if You Share 277 | all or a substantial portion of the contents of the database. 278 | 279 | For the avoidance of doubt, this Section 4 supplements and does not 280 | replace Your obligations under this Public License where the Licensed 281 | Rights include other Copyright and Similar Rights. 282 | 283 | 284 | Section 5 -- Disclaimer of Warranties and Limitation of Liability. 285 | 286 | a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE 287 | EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS 288 | AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF 289 | ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, 290 | IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, 291 | WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR 292 | PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, 293 | ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT 294 | KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT 295 | ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. 296 | 297 | b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE 298 | TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, 299 | NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, 300 | INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, 301 | COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR 302 | USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN 303 | ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR 304 | DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR 305 | IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. 306 | 307 | c. The disclaimer of warranties and limitation of liability provided 308 | above shall be interpreted in a manner that, to the extent 309 | possible, most closely approximates an absolute disclaimer and 310 | waiver of all liability. 311 | 312 | 313 | Section 6 -- Term and Termination. 314 | 315 | a. This Public License applies for the term of the Copyright and 316 | Similar Rights licensed here. However, if You fail to comply with 317 | this Public License, then Your rights under this Public License 318 | terminate automatically. 319 | 320 | b. Where Your right to use the Licensed Material has terminated under 321 | Section 6(a), it reinstates: 322 | 323 | 1. automatically as of the date the violation is cured, provided 324 | it is cured within 30 days of Your discovery of the 325 | violation; or 326 | 327 | 2. upon express reinstatement by the Licensor. 328 | 329 | For the avoidance of doubt, this Section 6(b) does not affect any 330 | right the Licensor may have to seek remedies for Your violations 331 | of this Public License. 332 | 333 | c. For the avoidance of doubt, the Licensor may also offer the 334 | Licensed Material under separate terms or conditions or stop 335 | distributing the Licensed Material at any time; however, doing so 336 | will not terminate this Public License. 337 | 338 | d. Sections 1, 5, 6, 7, and 8 survive termination of this Public 339 | License. 340 | 341 | 342 | Section 7 -- Other Terms and Conditions. 343 | 344 | a. The Licensor shall not be bound by any additional or different 345 | terms or conditions communicated by You unless expressly agreed. 346 | 347 | b. Any arrangements, understandings, or agreements regarding the 348 | Licensed Material not stated herein are separate from and 349 | independent of the terms and conditions of this Public License. 350 | 351 | 352 | Section 8 -- Interpretation. 353 | 354 | a. For the avoidance of doubt, this Public License does not, and 355 | shall not be interpreted to, reduce, limit, restrict, or impose 356 | conditions on any use of the Licensed Material that could lawfully 357 | be made without permission under this Public License. 358 | 359 | b. To the extent possible, if any provision of this Public License is 360 | deemed unenforceable, it shall be automatically reformed to the 361 | minimum extent necessary to make it enforceable. If the provision 362 | cannot be reformed, it shall be severed from this Public License 363 | without affecting the enforceability of the remaining terms and 364 | conditions. 365 | 366 | c. No term or condition of this Public License will be waived and no 367 | failure to comply consented to unless expressly agreed to by the 368 | Licensor. 369 | 370 | d. Nothing in this Public License constitutes or may be interpreted 371 | as a limitation upon, or waiver of, any privileges and immunities 372 | that apply to the Licensor or You, including from the legal 373 | processes of any jurisdiction or authority. 374 | 375 | 376 | ======================================================================= 377 | 378 | Creative Commons is not a party to its public 379 | licenses. Notwithstanding, Creative Commons may elect to apply one of 380 | its public licenses to material it publishes and in those instances 381 | will be considered the “Licensor.” The text of the Creative Commons 382 | public licenses is dedicated to the public domain under the CC0 Public 383 | Domain Dedication. Except for the limited purpose of indicating that 384 | material is shared under a Creative Commons public license or as 385 | otherwise permitted by the Creative Commons policies published at 386 | creativecommons.org/policies, Creative Commons does not authorize the 387 | use of the trademark "Creative Commons" or any other trademark or logo 388 | of Creative Commons without its prior written consent including, 389 | without limitation, in connection with any unauthorized modifications 390 | to any of its public licenses or any other arrangements, 391 | understandings, or agreements concerning the use of licensed material. For 392 | the avoidance of doubt, this paragraph does not form part of the 393 | public licenses. 394 | 395 | Creative Commons may be contacted at creativecommons.org. 396 | -------------------------------------------------------------------------------- /LICENSE-CODE: -------------------------------------------------------------------------------- 1 | The MIT License (MIT) 2 | Copyright (c) Microsoft Corporation 3 | 4 | Permission is hereby granted, free of charge, to any person obtaining a copy of this software and 5 | associated documentation files (the "Software"), to deal in the Software without restriction, 6 | including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, 7 | and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, 8 | subject to the following conditions: 9 | 10 | The above copyright notice and this permission notice shall be included in all copies or substantial 11 | portions of the Software. 12 | 13 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT 14 | NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. 15 | IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, 16 | WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE 17 | SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | 6 | 7 | # Visual Studio Live Share Feedback 8 | 9 | 10 | 15 |
11 | Visual Studio Live Share
12 | Enabling developers to achieve greater confidence at speed by streamlining collaboration in real-time during development.
13 | Learn more! 14 |
16 | 17 | ## Quickstarts 18 | 19 | - [Share your first project](https://aka.ms/vsls-docs/share) 20 | - [Join your first collaboration session](https://aka.ms/vsls-docs/join) 21 | 22 | ## How-tos 23 | 24 | - [Collaborate using Visual Studio Code](https://aka.ms/vsls-docs/vscode) 25 | - [Collaborate using Visual Studio](https://aka.ms/vsls-docs/vs) 26 | 27 | ## Reference 28 | 29 | - [Connectivity requirements](https://aka.ms/vsls-docs/connection-mode) 30 | - [Security features](https://aka.ms/vsls-security) 31 | - [Linux install details](https://aka.ms/vsls-linux) 32 | - [Language and platform support](https://aka.ms/vsls-docs/platform-support) 33 | - [Extension support](https://aka.ms/vsls-docs/extensions) 34 | - [Common Use Cases](https://aka.ms/vsls-usecases) 35 | - [Troubleshooting](https://aka.ms/vsls-troubleshooting) 36 | 37 | ## Resources 38 | 39 | - [Provide feedback](https://aka.ms/vsls-support) 40 | - [FAQ](https://aka.ms/vsls-faq) 41 | - [VS Live Share Extension API](https://www.npmjs.com/package/vsls) 42 | - [VS Live Share Extension Samples](https://github.com/vsls-contrib) 43 | 44 | ## Contributing & Feedback 45 | 46 | Have a question or feedback? There are many ways to contribute. 47 | 48 | - [Up-vote a feature or request a new one](https://aka.ms/vsls-feature-requests) 49 | - Search [existing bugs](https://aka.ms/vsls-bugs) or [report a problem](CONTRIBUTING.md#file-a-problem-report) 50 | 51 | This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). 52 | For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or 53 | contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. 54 | 55 | ## License 56 | 57 | By downloading and using Visual Studio Live Share, you agree to the product [license terms](https://aka.ms/vsls-license) and [privacy statement](https://www.microsoft.com/en-us/privacystatement/EnterpriseDev/default.aspx). 58 | 59 | License for documentation: 60 | 61 | Copyright © Microsoft Corporation 62 | All rights reserved. 63 | Creative Commons Attribution 4.0 License (International): https://creativecommons.org/licenses/by/4.0/legalcode 64 | 65 | License for documentation code samples: 66 | 67 | The MIT License (MIT) 68 | Copyright (c) Microsoft Corporation 69 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## Security 4 | 5 | Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/). 6 | 7 | If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/opensource/security/definition), please report it to us as described below. 8 | 9 | ## Reporting Security Issues 10 | 11 | **Please do not report security vulnerabilities through public GitHub issues.** 12 | 13 | Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/opensource/security/create-report). 14 | 15 | If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/opensource/security/pgpkey). 16 | 17 | You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://aka.ms/opensource/security/msrc). 18 | 19 | Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue: 20 | 21 | * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.) 22 | * Full paths of source file(s) related to the manifestation of the issue 23 | * The location of the affected source code (tag/branch/commit or direct URL) 24 | * Any special configuration required to reproduce the issue 25 | * Step-by-step instructions to reproduce the issue 26 | * Proof-of-concept or exploit code (if possible) 27 | * Impact of the issue, including how an attacker might exploit the issue 28 | 29 | This information will help us triage your report more quickly. 30 | 31 | If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/opensource/security/bounty) page for more details about our active programs. 32 | 33 | ## Preferred Languages 34 | 35 | We prefer all communications to be in English. 36 | 37 | ## Policy 38 | 39 | Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/opensource/security/cvd). 40 | 41 | 42 | -------------------------------------------------------------------------------- /ThirdPartyNotices: -------------------------------------------------------------------------------- 1 | ##Legal Notices 2 | Microsoft and any contributors grant you a license to the Microsoft documentation and other content 3 | in this repository under the [Creative Commons Attribution 4.0 International Public License](https://creativecommons.org/licenses/by/4.0/legalcode), 4 | see the [LICENSE](LICENSE) file, and grant you a license to any code in the repository under the [MIT License](https://opensource.org/licenses/MIT), see the 5 | [LICENSE-CODE](LICENSE-CODE) file. 6 | 7 | Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation 8 | may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. 9 | The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. 10 | Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653. 11 | 12 | Privacy information can be found at https://privacy.microsoft.com/en-us/ 13 | 14 | Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents, 15 | or trademarks, whether by implication, estoppel or otherwise. --------------------------------------------------------------------------------