Skip to content

Debug renaming could cause BadImageException #161

@wmjordan

Description

@wmjordan

I was addressing a weird problem after upgrading to the recently released version 1.4. (The weird problem will be reported later if I could figure out which part may be the cause) I changed the rename setting to debug. The "protected" application could not run due to a BadImageException which complained that there were two type having the same name in the assembly.

I examined the assembly and found it probably had something to do with nested generic type.

static class X<T> {
   abstract class A { }
   internal sealed class B : A { }
   internal sealed class C : A { }
}

After the debug renaming, the A, B, C within X<T> will be renamed to X, which breaks the application.

EDIT: The weird problem disappeared after applying #163.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions