Background

We do not use the ResXFileCodeGenerator, because it doesn't generate what we need. Instead we manage our resources using ResourceManager ouerselves.

Porting our code from .NET Framework to .NET Core 3.0, we see changes in the handling of *.resx files that break our code. The embedded *.resources resource streams have unexpected names.

I think it is related to #4488

Steps to reproduce

Build attached solution
ResX.zip

Expected behavior

Dll contains:

• ResX.Foo.resources
• ResX.Foo2.resources
• ResX.Foo3.resources

Actual behavior

Dll contains:

• ResX.FooExtensions.resources
• ResX.Foo2.resources
• ResX.Messages.resources

Environment data

We use VisualStudio 16.3.3 with .NET Core 3.0 on Windows 10 German.
It worked with VisualStudio 16.2.x and .NET Core 3.0 preview9