dotnet/roslyn

Investigate and fix/document the behavior when compiler is supplied with a netmodule reference in wrong casing.

Open

#1,672 opened on Mar 30, 2015

View on GitHub
 (2 comments) (0 reactions) (0 assignees)C# (20,414 stars) (4,257 forks)batch import
Area-CompilersConcept-PortabilityDocumentationLanguage-C#Language-VBhelp wanted

Description

We had reports that some versions of CSC could embed two module references in the metadata - one as supplied and another matching the actual file name.

There should be just one module reference in the metadata.

Contributor guide

Tech stack
csharp
Domain
tooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
C# programmingcompiler fundamentalsfamiliarity with .NET metadata
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
Investigate the behavior of the C# compiler when a netmodule reference is supplied with wrong casing. Look at the metadata emission code in the Roslyn compiler, possibly in the Microsoft.CodeAnalysis.CSharp namespace. Write a unit test that supplies a netmodule reference with different casing and verify that only one module reference appears in the emitted metadata. Check if there are existing tests for module references. The issue may require understanding how the compiler resolves and embeds module references.