dotnet/roslyn

How to handle warnings CS1701 and CS1702

Open

#23,488 opened on Nov 30, 2017

View on GitHubContributor guide
 (2 comments) (1 reaction) (0 assignees)C# (4,257 forks)batch import
Area-CompilersQuestionhelp wanted

Repository metrics

Stars
 (20,414 stars)
PR merge metrics
 (Avg merge 6d 17h) (256 merged PRs in 30d)

Description

Is there built in support in the .Net compiler platform to generate binding redirects similar to setting the AutoGenerateBindingRedirects to true in a visual studio project?

Alternativly, are there any guidelines on how one should go about to generate binding redirects when the compilation result contains warnings CS1701 and CS1702? Or maybe there is a way to tell the compiler that some redirect exists in order to supress the warning?

What I would like to achieve is:

  • If a binding redirect exists in the projects app.config --> no warning.
  • If there is a need for a binding redirect, it should be added to the app.config --> no warning.

Contributor guide

Research direction
Investigate the Roslyn compiler's handling of binding redirect warnings. Look for existing mechanisms to suppress or auto generate binding redirects in MSBuild or the compiler. Check the app.config handling and consider if a new feature or documentation is needed.
Tech stack
csharp
Domain
build system
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.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#MSBuild
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25