-
Notifications
You must be signed in to change notification settings - Fork 51
Contributing Code
Patrick Nelson edited this page Sep 10, 2015
·
1 revision
Before submitting a new sample or making extensive changes, please discuss it with the team. Submissions must meet a high bar for quality and design.
- Follow the coding style. We use the .NET code style for C# files. The team enforces this by running the .NET code formatter tool on the code base. Contributors should ensure they follow these guidelines when making submissions.
- Entirely new samples or new features should be discussed with the team first or they will likely be declined.
- The goal of samples is to be simple and serve as a teaching tool. Contributions should not add new features or increase complexity unless there is a compelling reason to do so.
- All tests must continue to pass after a contribution including tests that are not yet open source.
- Only contributions against the master branch will be accepted. Authors submitting pull requests that target experimental feature branches or release branches will likely be asked target their pull request at the master branch.
- Pull requests that do not automatically merge with the tip of the master branch will be declined. The author will be asked to rebase to the tip and update the pull request
- Contributors must sign the Microsoft CLA
Concord Documentation:
- Overview
- Visual Studio 2022 support
- Concord Architecture
- Getting troubleshooting logs
- Tips for debugging extensions
- Component Discovery and Configuration
- Component Levels
- Navigating the Concord API
- Obtaining the Concord API headers, libraries, etc
- Concord Threading Model
- Data Container API
- Creating and Closing Objects
- Expression Evaluators (EEs)
- .NET language EEs
- Native language EEs
- Installing Extensions
- Cross Platform and VS Code scenarios:
- Implementing components in native code:
- Worker Process Remoting
Samples: