Skip to main content
Microsoft.Net.Compilers.Toolset package icon

Microsoft.Net.Compilers.Toolset

.NET Compilers Toolset Package. Referencing this package will cause the project to be built using the C# and Visual Basic compilers contained in the package, as opposed to the version installed with MSBuild. This package is primarily intended as a method for rapidly shipping hotfixes to customers. Using it as a long term solution for providing newer compilers on older MSBuild installations is explicitly not supported. That can and will break on a regular basis. The supported mechanism for providing new compilers in a build enviroment is updating to the newer .NET SDK or Visual Studio Build Tools SKU. This package requires either MSBuild 16.3 and .NET Desktop 4.7.2+ or .NET Core 2.1+ More details at https://aka.ms/roslyn-packages This package was built from the source at https://github.com/dotnet/roslyn/commit/182c1e333b8514ac17dc463aac26b5552977a040.

Total Downloads
22.0M
22,017,582
Published
Dec 4, 2020
Latest stable version

Install

.NET CLI
dotnet add package Microsoft.Net.Compilers.Toolset --version 3.9.0-1.final
Package Manager Console
Install-Package Microsoft.Net.Compilers.Toolset -Version 3.9.0-1.final
PackageReference
<PackageReference Include="Microsoft.Net.Compilers.Toolset" Version="3.9.0-1.final" />

Frameworks

.NETFramework4.7.2 .NETCoreApp3.1

Dependencies

No declared dependencies.

Adoption guide

A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.

This version is marked prerelease. Validate its API and upgrade path before production use.

Compatibility metadata lists 2 target frameworks; confirm the exact target used by your application.

How to read this guidance

Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.

Useful next steps

Move from package metadata to a concrete selection or review workflow.