Microsoft.CodeAnalysis.Scripting

v5.0.0

Microsoft .NET Compiler Platform ("Roslyn") CSharp and VB scripting package. More details at https://aka.ms/roslyn-packages This package was built from the source at https://github.com/dotnet/roslyn/commit/6c4a46a31302167b425d5e0a31ea83c9a9aa1d09.

Microsoft RoslynTeam

Roslyn CodeAnalysis Compiler CSharp VB VisualBasic Parser Scanner Lexer Emit CodeGeneration Metadata IL Compilation Scripting Syntax Semantics

NuGet Stats Changelog

Total Downloads

29.0M

29,029,959

Published

Nov 18, 2025

Latest stable version

Install

.NET CLI

dotnet add package Microsoft.CodeAnalysis.Scripting --version 5.0.0

Package Manager Console

Install-Package Microsoft.CodeAnalysis.Scripting -Version 5.0.0

PackageReference

<PackageReference Include="Microsoft.CodeAnalysis.Scripting" Version="5.0.0" />

Frameworks

.NETStandard2.0

Dependencies

Microsoft.CodeAnalysis.CSharp.Scripting

.NETStandard2.0

[5.0.0, 5.0.0]

Microsoft.CSharp

.NETStandard2.0

[4.7.0, )

Microsoft.CodeAnalysis.Analyzers

.NETStandard2.0

[3.11.0, )

System.Buffers

.NETStandard2.0

[4.6.0, )

System.Collections.Immutable

.NETStandard2.0

[9.0.0, )

System.Memory

.NETStandard2.0

[4.6.0, )

System.Numerics.Vectors

.NETStandard2.0

[4.6.0, )

System.Reflection.Metadata

.NETStandard2.0

[9.0.0, )

System.Runtime.CompilerServices.Unsafe

.NETStandard2.0

[6.1.0, )

System.Text.Encoding.CodePages

.NETStandard2.0

[8.0.0, )

System.Threading.Tasks.Extensions

.NETStandard2.0

[4.6.0, )

Adoption guide

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

Compatibility metadata lists 1 target framework; 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.

Audit NuGet dependencies in a .NET project Review NuGet licenses before shipping