Shouldn't escape namespace

[CreateAndInject]

No description provided.

[0xd4d]

Can you explain a little more why this is needed and what it fixes?

[CreateAndInject]

Type.Name=TypeDef.ReflectionName
Type.FullName=TypeDef.ReflectionFullName
But Type.Namespace=TypeDef.Namespace, it means Type.Namespace doesn't escape any char.
So:

namespace te&st
{
    class Fo&rm1 : Form
    {
      //..........
    }
}

This type requests resource te&st.Fo\&rm1.resources rather than te\&st.Fo\&rm1.resources

The following test work fine, but it wont run after de4dot, this PR can fix it.
test.zip

[CreateAndInject]

.Net doesn't use Type.FullName to request resources, instead, it concats Namespace and Name
https://github.com/dotnet/runtime/blob/c9f917052fc091014ef0f311b6f79a812bbfbd38/src/coreclr/src/System.Private.CoreLib/src/System/Reflection/RuntimeAssembly.cs#L235-L249

[0xd4d]

There are two GetManifestResourceStream() methods, one with a Type+string and the other one with a string arg. How can you be sure the 2nd one with only a string arg is never called?

[CreateAndInject]

I think it isn't relative to this PR.
If old code work with GetManifestResourceStream(string), my PR work also.
This PR doesn't take any side effect, if you don't think so, can you give me a test which old code work fine but this PR doesn't work.

[0xd4d]

Your code changes something that's used by all deobfuscators, so unless you can show that that other overload is never called by them, this PR could break other code.

[CreateAndInject]

GetManifestResourceStream(string name) requires name with a .resources postfix, which de4dot doesn't support originally.
de4dot supports ResourceManager(string baseName, Assembly assembly), and this PR still supports it.
So, I don't think it's a breaking change, since it doesn't break any correct output.

[CreateAndInject]

Related issue