├── .github └── workflows │ └── autocloser.yml ├── CONTRIBUTING.md ├── ISSUE_TEMPLATE.md ├── README.md ├── SECURITY.md └── UPDATE_HISTORY.md /.github/workflows/autocloser.yml: -------------------------------------------------------------------------------- 1 | name: Autocloser 2 | on: [issues] 3 | jobs: 4 | autoclose: 5 | runs-on: ubuntu-latest 6 | steps: 7 | - name: Autoclose issues 8 | uses: roots/issue-closer@v1.1 9 | with: 10 | repo-token: ${{ secrets.GITHUB_TOKEN }} 11 | issue-close-message: "@${issue.user.login} bugs and new suggestions should be reported on the [Developer Community forum](https://developercommunity.visualstudio.com). It is centralized, better equipped for group voting, and has more visibility." 12 | issue-pattern: "a^" -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | ## Bugs and Suggestions 2 | 3 | **New issues should not be opened on this repo.** 4 | 5 | Bugs and new suggestions should be reported on the [Developer Community forum](https://developercommunity.visualstudio.com). It is centralized, better equipped for group voting, and has more visibility. -------------------------------------------------------------------------------- /ISSUE_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | ## Bugs and Suggestions 2 | 3 | **New issues should not be opened on this repo.** 4 | 5 | Bugs and new suggestions should be reported on the [Developer Community forum](https://developercommunity.visualstudio.com). It is centralized, better equipped for group voting, and has more visibility. -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Visual C++ for Linux Development 2 | 3 | This is a legacy repo that archives old discussion and questions related to the Visual C++ for Linux Development extension. Existing issues will be driven to completion. 4 | 5 | ## Bugs and Suggestions 6 | 7 | **New issues should not be opened on this repo.** 8 | 9 | Bugs and new suggestions should be reported on the [Developer Community forum](https://developercommunity.visualstudio.com). It is centralized, better equipped for group voting, and has more visibility. 10 | 11 | ## Closing 12 | New issues will be closed. Bugs and suggestions should be reported on the [Developer Community forum](https://developercommunity.visualstudio.com). 13 | 14 | Existing issues may be closed by the original poster at any time. An issue can be closed if: 15 | - A request is a duplicate of another. The duplicate will be linked; 16 | - Any discussion that has run its course. 17 | 18 | ## Important Links 19 | - Developer Community forum for bugs, suggestions reporting and support: https://developercommunity.visualstudio.com 20 | - Documentation: https://blogs.msdn.microsoft.com/vcblog/2016/03/30/visual-c-for-linux-development/ 21 | - Releases and Release Notes: https://visualstudiogallery.msdn.microsoft.com/725025cf-7067-45c2-8d01-1e0fd359ae6e 22 | - Visual Studio 2017 Preview Release: https://www.visualstudio.com/vs/preview/ 23 | - VC++ Blog: https://blogs.msdn.microsoft.com/vcblog 24 | 25 | ## Demos 26 | - [Visual C++ for Linux Development - Handling multiple connections](https://vimeo.com/251731898) 27 | - [Visual C++ for Linux Development - Setting up additional include directories](https://vimeo.com/251710903 ) 28 | 29 | This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). 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. 30 | 31 | -------------------------------------------------------------------------------- /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 | -------------------------------------------------------------------------------- /UPDATE_HISTORY.md: -------------------------------------------------------------------------------- 1 | 2 | --------------------------------------------------------------------------------