Module.ScopeName returns appname.dll for single-file apps

[agocke]

When published as a single file, this code prints single-file.dll.

class Program
{
    public static void Main()
    {
         Console.WriteLine(typeof(Program).Assembly.GetModules()[0].ScopeName);
    }
}

It's unclear whether this is the correct behavior or just an oversight. Name and FullyQualifiedName both return <Unknown>

[ghost]

Tagging subscribers to this area: @agocke, @vitek-karas, @VSadov
See info in area-owners.md if you want to be subscribed.

Issue Details

---

When published as a single file, this code prints single-file.dll.

class Program
{
    public static void Main()
    {
         Console.WriteLine(typeof(Program).Assembly.GetModules()[0].ScopeName);
    }
}

It's unclear whether this is the correct behavior or just an oversight. Name and FullyQualifiedName both return <Unknown>

Author:	agocke
Assignees:	-
Labels:	area-Single-File, untriaged
Milestone:	-

[jkotas]

I think it is the correct behavior. ScopeName is meant to return the scope name from metadata, with no sugar coating.

[agocke]

Is .dll appropriate? That was the strange part for me.

[agocke]

If we do not end up changing this behavior, I think the behavior change should maybe be on MetadataLoadContext (at the suppression in #56196) to produce a string different from <Unknown> when loading from memory

[jkotas]

I think the behavior change should maybe be on MetadataLoadContext

Agree. ScopeName should return ModuleDefinition.Name

Is .dll appropriate?

Roslyn uses the filename, including the suffix, for this by default. You can override the default using /modulename Roslyn switch. E.g. Compile .dll with /modulename:banana - ScopeName will return banana without .dll suffix.

[agocke]

I'm going to close this as by-design. Changing these values now seems like low value without a motivating scenario.