| Release | Unit Tests (Debug) | Unit Tests (Release) | Localization | Coverage (Debug) |
|---|---|---|---|---|
| 16.0 |  |
|||
| 16.5 |  |
|||
| 16.6 |  |
|||
| master |  |
This repository contains the new .NET Project System that has been rewritten on top of the Common Project System (CPS). In Visual Studio 2017 and Visual Studio 2019, this project system is used by default for Shared Projects (C# and Visual Basic), and .NET Core (C#, F# and Visual Basic) project types, however, long term it will be the basis of all C#, F# and Visual Basic project types. For a list of feature differences between the project systems, see Feature Comparison.
The legacy C# and Visual Basic project systems (csproj.dll and msvbprj.dll) first shipped with Visual Studio .NET in 2002. They have served us well but are:
- Native and COM-based
- Single threaded and bound to the UI thread
- Hard to extend outside of aggregation via the use of
<ProjectTypeGuids>and sub types (flavors) - Separate implementations for C# and Visual Basic projects
The new .NET Project System is:
- Managed and managed-interface based
- Multi-threaded, scalable, and responsive
- Easy to extend and compose via the Managed Extensibility Framework (MEF). Many parties, including 3rd parties, can contribute to a single project system.
- A single implementation for C#, F# and Visual Basic projects
A project system sits between a project file on disk (for example, .csproj and .vbproj) and various Visual Studio features including, but not limited to, Solution Explorer, designers, the debugger, language services, build and deployment. Almost all interaction that occurs with files contained in a project file happens through the project system.
There are many technologies that come together to make up the .NET Project System:
- MSBuild provides the build engine and file format.
- SDK provides the command-line interface for building, running and interacting with .NET projects, along with the necessary MSBuild tasks and targets.
- Common Project System provides the base building blocks for the project system including (but not limited to) project tree, build and debugger coordination and Visual Studio integration.
- Roslyn provides C# and Visual Basic language support including compilers, IntelliSense, refactorings, analyzers and code fixes.
- Visual F# tools provides F# language support.
We welcome you to try things out, file issues, make feature requests and join us in design conversations. If you are looking for something to work on, take a look at our help wanted issues for a great place to start. Also be sure to check out our contributing guide.
This project has adopted a code of conduct adapted from the Contributor Covenant to clarify expected behavior in our community. This code of conduct has been adopted by many other projects. For more information see Contributors Code of conduct.