The C#, F# and Visual Basic project system for Visual Studio
Branch: master
Clone or download
drewnoakes Merge pull request #4581 from drewnoakes/up-to-date-check-logging
Fix incorrect UpToDateCheck log message
Latest commit b912355 Feb 19, 2019

C#, F# and Visual Basic project system

Release Branch Unit Tests (Debug) Unit Tests (Release) Localization Coverage (Debug)
15.9.x dev15.9.x Build Status Build Status Build Status codecov
16.0 Preview 4 dev16.0.x Build Status Build Status Build Status codecov
16.1 master Build Status Build Status Build Status codecov

Join the chat at

This repository contains the new C#, F# and Visual Basic project system that has been rewritten on top of the Common Project System (CPS). In Visual Studio 2017, 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 existing C# and Visual Basic project systems (csproj.dll and msvbprj.dll), which first shipped back in Visual nearly 15 years ago, 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)
  • Tied to Visual Studio

The new C#, F# and Visual Basic project system is:

  • Managed and managed-interface based
  • Multi-threaded, scalable, and responsive
  • Easy to extend via the use of the Managed Extensibility Framework (MEF) and composable. Many parties, including 3rd parties, can contribute to a single project system
  • Hostable outside of Visual Studio

What is a project system?

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 MSBuild tasks and targets needed to build .NET projects.
  • 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.
  • CLI is the .NET command-line interface for building, running and interacting with .NET projects.


How do I engage and contribute?

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.