| Branch | Debug x86 | Debug x64 | Release x86 | Release x64 |
|---|---|---|---|---|
| master | ||||
| master-vs-deps |
| Branch | Windows Debug | Windows Release | Linux |
|---|---|---|---|
| master | |||
| master-vs-deps |
| Branch | Debug | Release |
|---|---|---|
| master | ||
| master-vs-deps |
| Branch | Determinism | Build Correctness | Mono | Spanish |
|---|---|---|---|---|
| master | ||||
| master-vs-deps |
Roslyn provides open-source C# and Visual Basic compilers with rich code analysis APIs. It enables building code analysis tools with the same APIs that are used by Visual Studio.
We are now taking language feature discussion in other repositories:
- https://github.com/dotnet/csharplang for C# specific issues
- https://github.com/dotnet/vblang for VB-specific features
- https://github.com/dotnet/csharplang for features that affect both languages
Discussion about the transition of language design to the new repos is at dotnet#18002.
Want to start developing in C# and Visual Basic? Download Visual Studio 2017, which has the latest features built-in. There are also prebuilt Azure VM images available with Visual Studio 2017 already installed.
To install the latest release without Visual Studio, run one of the following nuget command lines:
nuget install Microsoft.Net.Compilers # Install C# and VB compilers
nuget install Microsoft.CodeAnalysis # Install Language APIs and Services
Daily NuGet builds of the project are also available in our MyGet feed:
See what's new with the C# and VB compilers.
- Clone the sources:
git clone https://github.com/dotnet/roslyn.git - Enhanced source view, powered by Roslyn
- Building, testing and debugging the sources
- Tutorial articles by Alex Turner in MSDN Magazine
- Roslyn Overview
- API Changes between CTP 6 and RC
- Samples and Walkthroughs
- Documentation
- Analyzer documentation
- Syntax Visualizer Tool
- Syntax Quoter Tool
- Roadmap
- Language Design Notes
- FAQ
- Also take a look at our Wiki for more information on how to contribute, what the labels on issue mean, etc.
Some of the best ways to contribute are to try things out, file bugs, and join in design conversations.
Looking for something to work on? The list of up for grabs issues is a great place to start.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
This project is part of the .NET Foundation along with other projects like the class libraries for .NET Core.