dotnet/roslyn

integrate csi with dotnet cli and test it works or coreclr

Open

#6,882 opened on Nov 19, 2015

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)C# (4,257 forks)batch import
Area-InteractiveInteractive-ScriptingLogichelp wanted

Repository metrics

Stars
 (20,414 stars)
PR merge metrics
 (PR metrics pending)

Description

This issue does not include a description.

Contributor guide

Research direction
Understand what CSI (Component Source Index) is and its purpose. Explore the dotnet/roslyn repository to find relevant code for CLI integration. Look at existing test patterns for coreclr and design a test plan.
Tech stack
csharp
Domain
compilersbackendtooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
C#.NET CLIcompiler internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30